Closed shresthaashok closed 1 month ago
@shresthaashok Did you find anything?
You've not mentioned which permission specifically but sounds like you're referring to USE_EXACT_ALARM
as Google says it's only for calendar and alarm clocks. If so, Google had already stated in their own docs that this was subject to their approval that implied there was risk involved and was relayed in the plugin readme https://github.com/MaikuB/flutter_local_notifications/tree/master/flutter_local_notifications#androidmanifestxml-setup. When they introduced changes in Android 14, they had provided guidance on this as well (see https://developer.android.com/about/versions/14/changes/schedule-exact-alarms) and the plugin was updated in 16.0 to accomodate. The section I linked to earlier in the readme also mentions this. Have you checked this?
Hi! @MaikuB I added the permissions below to the AndroidManifest.xml file and published the app to Google Play Store.
However the publishing failed due to Exact Alarm permission.
Publishing failed :| Google Play failed to upload artefacts. You must let us know whether your app uses any exact alarm permissions: { "error": { "code": 403, "message": "You must let us know whether your app uses any exact alarm permissions", "status": "PERMISSION_DENIED" }
Could you please check this issue?
This isn't a plugin issue. If you need exact alarm permissions then the readme for the plugin and Android's own docs provide details on how to handle this already. If you're going to continue to intentionally use USE_EXACT_ALARM
then you need to check the Google Play store/console (e.g. see https://github.com/MaikuB/flutter_local_notifications/issues/2348#issuecomment-2185804813) as this isn't a plugin issue