I have this issue with the manifest.
Looks like it could be a hoax: Using @string for android: permissions in ContentProvider
I have a provider with separate permissions for different versions of the application (so I can store different permissions in the string folders of the res res difference folders in different versions).
My manifest is as follows:
<provider android:authorities="@string/app_provider_auth" android:name="com.mecompany.myapp.provider.CachedFileProvider"/>
NOW, this works great, but I see the Bad Manifest problem when it is installed on an OS 2.1 device. This problem is that when I change it to a text string, it works fine on 2.1.
I understand that in 2.1 (7) or earlier, the manifest does not allow references to strings from resource files. So, can I create a separate manifest for version 7-, can I have an if statement in the manifest? or do I need to raise minSDK (last resort)?
UPDATE:
OK on further searches it seems that I can set / switch the auth line of the provider using my Maven assembly. I already have several profiles and I redefine the resource folders. Therefore, I like this idea, but I cannot omit it. something like
<replaceAuthority>${customerauthority}<replaceAuthority>
However, I do not know what the tag is that I should use, or, if I suggested above, this is the way I need to go.
android string resources manifest
Aiden Fry Oct 25 2018-12-12T00: 00Z
source share