MDK Branded Client Build PDFFileProvider package conflict

[ed_miller]

Experts,

I am building branded clients for SAM. I have separate and unique package names for different apps. I am building for Android at the moment. Up through building a client using the MDK Plug-in's for version 2110 or earlier, everything was fine. I could create a branded client with for package "A" and another for package "B" and install on the device simultaneously without issue. However, I am now using MDK Plug-in's for version 2210. The build of the packages is fine. When I install the ".apk" for package "A", it installs just fine. However when I install the ".apk" for package "B", it gives me the underlying error or:

• Error: INSTALL_FAILED_CONFLICTING_PROVIDER: Can't install because provider name com.sap.sam.framework.pdf.provider (in package "B") is already used by "A"

As I dug in, it seems this information is buried in an AndroidManifest.xml file that the build process creates.

<provider

android:name="com.sap.sam.framework.pdf.PDFFileProvider"

android:authorities="com.sap.sam.framework.pdf.provider"

android:exported="false"

android:grantUriPermissions="true"

<meta-data

android:name="android.support.FILE_PROVIDER_PATHS"

android:resource="@xml/file_paths"

</provider>

If I uninstall package "A" and install package "B", "B" will install just fine. But then if I try to install package "A", I get the same error.Can a fix be provided by SAP so the "android:authorities" for this provider are set uniquely in order for multiple applications to be installed on the device simultaneously?Thank you in advance, Ed

[muhammad_rafay]

There is a SAP note already exist for this

https://launchpad.support.sap.com/#/notes/3276311

[ed_miller]

Thanks for the quick response. I obviously missed this one as I was reviewing the SAP Notes list.

It would be good, though, for SAP to put this fix in the MDK Plug-In directly since there is a solution. That SAP Note was released on November 29, 2022 and there have been at least 5 (five) versions of the MDK Plug-In's for Android released since.

I will say, though, that it does solve the problem, but having that fix in the latest plug-ins would be very helpful.

Thanks,

Ed

[muhammad_rafay]

We haven't released any version after 2210 so it will be part of the 2305 release.
The five versions you are seeing are all based on 2210 and none of them were for PDF related