For anyone having the same issue, you can remove the android:MaxSdkVersion attribute from the merged manifest as follows.

<uses-permission
    android:name="android.permission.WRITE_EXTERNAL_STORAGE"
    tools:remove="android:maxSdkVersion" />

Duplicate of #301

Hi @smuldr,

This is described in our documentation and release notes:

To be ready for Android O, HockeySDK-Android now limits the WRITE_EXTERNAL_STORAGE permission with the maxSdkVersion filter. In some use cases, e.g. where an app contains a dependency that requires this permission, maxSdkVersion makes it impossible for those dependencies to grant or request the permission. The solution for those cases is to declare the tools:node="replace" manifest merging strategy later in the dependency tree:
<uses-permission android:name="android.permission.WRITE_EXTERNAL_STORAGE" tools:node="replace"/>

Best,
Ivan

Hi,

I have tried all solution but no success.

Hi @Iqra786,

have you tried <uses-permission android:name="android.permission.WRITE_EXTERNAL_STORAGE" tools:node="replace"/> as well as
<uses-permission android:name="android.permission.WRITE_EXTERNAL_STORAGE" tools:node="remove" />?

Hi, @TroubleMakerBen

Yes, I have tried both.

Is there any chance you can send us the project (or a sample that has this behavior)? We cannot repro this and I'm running out of ideas. To do that, please contact us via Support and mention this conversation.

Thx a ton!

@Iqra786 @TroubleMakerBen
I can confirm that replacing the maxSdkVersion works as expected for us with the following ways: tools:node="replace" and tools:remove="android:maxSdkVersion".
However, tools:node="remove" only removes the permission itself and not the maxSdkVersion restriction, so don't use this!

We also have Spoon and LeakCanary besides HockeySDK in our project, did you make sure to check your merged manifest (tab "Merged Manifest" in Android Studio).
If you have multiple manifest files in your project for more than one module, you should also check if the right one is used.

The following screenshots show the difference in our final merged manifest (first one without the additional code, resulting in the maxSdkVersion to be incorrectly present, and the second one with the maxSdkVersion replaced/removed correctly).

Hope this helps you in finding your problem cause...

Btw: don't ask me why the READ_EXTERNAL_STORAGE permission occurs twice in the final merge result 😄

Adding tools:node="replace" helps for me, but now I have the warning

Task :app:processDebugManifest /Android/app/AndroidManifest.xml:6:2-131 Warning: uses-permission#android.permission.WRITE_EXTERNAL_STORAGE was tagged at AndroidManifest.xml:6 to replace another declaration but no other declaration present

Any ideas how to avoid or at least suppress it?

@rusmonster The warning tells you that you don't have any tags to be replaced. Looks like your project doesn't contain HockeyApp dependencies, can you make sure your app contains HockeyApp libraries in it?

@jaelim-ms Yes, I'm sure my app contains hockeyApp. Moreover, without tools:node="replace" hockeyApp drops WRITE_EXTERNAL_STORAGE in my app on API > 18 and adding the tools:node="replace" returns it back. So the warning looks like manifest merger issue. I'm just asking about how to suppress it?

@rusmonster I've tried to find a way to suppress the warning but couldn't find any. Sorry about that. I keep searching it and let you know if I find but the warning isn't from lint so I don't think you can suppress it.

We have another open issue regarding the permission issue. Please continue conversation in #373.