Flutter-permission-handler: Apple rejection. NSAppleMusicUsageDescription

Created on 27 May 2020  路  4Comments  路  Source: Baseflow/flutter-permission-handler

馃悰 Bug Report

Apple rejects due to not defining NSAppleMusicUsageDescription even when not needing this permission.

Expected behavior

Should be able to disable this via preprocessor definition.

Reproduction steps

Configuration

Version: 5.0.0+hotfix.6

Platform:

  • [x] :iphone: iOS
  • [ ] :robot: Android

Most helpful comment

@gusabdala you can mention dummy permission like this in info.plist

<key>NSAppleMusicUsageDescription</key>
<string>This permission is not needed by the app, but it is required by an underlying API. If you see this dialog, contact us.</string>

All 4 comments

@mvanbeusekom Is this something you could resolve?

What I did, and what others have suggested is to add it to the info file and state that your "app does not use this permission, if requested please reject." It shouldn't ever call though.

If you want to disable it completely, this seems to work I haven't tried it.
https://github.com/Baseflow/flutter-permission-handler/issues/26#issuecomment-605026503

@gusabdala you can mention dummy permission like this in info.plist

<key>NSAppleMusicUsageDescription</key>
<string>This permission is not needed by the app, but it is required by an underlying API. If you see this dialog, contact us.</string>

I've seen this before and the reason (from my understanding) is because if an underlying SDK or framework requires a certain permission for a specific feature (regardless of whether you implement that feature), you need to include that permission in your plist. The reasoning being, if somehow that code is triggered and the permission isn't accounted for in the plist, it will cause a crash and from my experience Apple review won't allow for such a possibility.

I would echo the comments from @smasinde and @shahnawazahmed88

Was this page helpful?
0 / 5 - 0 ratings