Flutter-permission-handler: Unable to publish to Appstore rejection because of NSCalendarUsageDescription but i have made the Podfile changes as per the Ios setup in the pub dev.

Created on 31 Aug 2020  路  8Comments  路  Source: Baseflow/flutter-permission-handler

Screenshot 2020-08-31 at 8 57 43 AM

Permission handler version:
permission_handler: ^5.0.1+1
flutter version:
```Doctor summary (to see all details, run flutter doctor -v):
[鉁揮 Flutter (Channel stable, 1.20.2, on Mac OS X 10.15.6 19G2021, locale en-GB)

[鉁揮 Android toolchain - develop for Android devices (Android SDK version 29.0.2)
[鉁揮 Xcode - develop for iOS and macOS (Xcode 11.6)
[鉁揮 Android Studio (version 3.5)
[鉁揮 IntelliJ IDEA Community Edition (version 2019.3.1)
[鉁揮 VS Code (version 1.46.1)
[鉁揮 Connected device (1 available)

Podfile:
```post_install do |installer|
installer.pods_project.targets.each do |target|
target.build_configurations.each do |config|
config.build_settings['ENABLE_BITCODE'] = 'NO'
config.build_settings['GCC_PREPROCESSOR_DEFINITIONS'] ||= [
'$(inherited)',
## dart: PermissionGroup.calendar
"PERMISSION_EVENTS=0",

              ## dart: PermissionGroup.reminders
              "PERMISSION_REMINDERS=0",

              ## dart: PermissionGroup.contacts
              "PERMISSION_CONTACTS=0",

              ## dart: PermissionGroup.microphone
              "PERMISSION_MICROPHONE=0",

              ## dart: PermissionGroup.speech
              "PERMISSION_SPEECH_RECOGNIZER=0",

              ## dart: [PermissionGroup.location, PermissionGroup.locationAlways, PermissionGroup.locationWhenInUse]
              "PERMISSION_LOCATION=0",

              ## dart: PermissionGroup.notification
              # "PERMISSION_NOTIFICATIONS=0",

              ## dart: PermissionGroup.mediaLibrary
              "PERMISSION_MEDIA_LIBRARY=0",

              ## dart: PermissionGroup.sensors
              "PERMISSION_SENSORS=0",
    ]
  end
flutter_additional_ios_build_settings(target)

end
end
```

Most helpful comment

@praveen-francium excuse me, could you please share your solutions? Your helps would be appreciated.

All 8 comments

Hi @praveen-francium ,

You should comment out the permissions you are using, so in this case "PERMISSION_EVENTS=0", should be # "PERMISSION_EVENTS=0",

@danielroek Thanks for the reply,But i don't want access to calendar, i need access only to notification so i commented that one.But now why i need to change to #"PERMISSION_EVENTS=0"

Did you add all the permissions to your Info.plist file? Apple rejects applications that do not specify the user-facing purpose String when using flutter_permission_handler.
The README states the following

IMPORTANT: You will have to include all permission options when you want to submit your App. This is because the permission_handler plugin touches all different SDKs and because the static code analyser (run by Apple upon App submission) detects this and will assert if it cannot find a matching permission option in the Info.plist. More information about this can be found here.

The original issue can be found here.

@danielroek Yes ,i need only permission for notifications and i have added that in the Info.Plist but i don't need access to calendars but the issue i am facing while publishing to appStore is related to Calendar issue.So please help me how to overcome this issue. Also i have followed up exactly how the Podfile need to be as per the documentation,i have commented only the notification line,but i am facing this issue.

This issue seems to be linked to this issue. Could you please try if updating your Podfile following the example works? Please let us know if this fixes your issue, that way we're able to update our documentation.

@danielroek Thanks for the reply,but i have added the podfile to your reference i think i did the same as what been mentioned in the link you provided actually.Please take a look at my Podfile and suggest me what if i am doing anything wrong.Because i just replicated as per the documentation.So please take a look at my Podfile and suggest me the changes.Thanks

Readding the line mentioned in Ios set up solves the issue.

@praveen-francium excuse me, could you please share your solutions? Your helps would be appreciated.

Was this page helpful?
0 / 5 - 0 ratings