Open
Bug 1818424
Opened 2 years ago
Updated 10 months ago
[meta] Android 13+ notifications permissions prompts
Categories
(Fenix :: General, enhancement, P2)
Tracking
(Not tracked)
NEW
People
(Reporter: jmahon, Unassigned)
References
(Depends on 1 open bug, Blocks 1 open bug)
Details
(Keywords: meta, Whiteboard: [fxdroid] [roadmap])
Android 13+ notifications permissions prompts
In Android 13, system notifications now require permission. We incorporated a basic version of this into the Onboarding flow for the sake of the re-engagement notifications (which need the user to grant permission immediately, in order to work).
But, if a user rejects that "overarching" permission, we lose the ability to send them notifications for any of the other things (listed in the Android 11+ permissions audit).
Preferred scope (negotiable):
- Request all permissions at the outset.
- If permission is denied, have a follow-up prompt appear in places where the user's interaction might trigger the need for permissions (e.g., signing in to sync, downloading a file for the first time, or playing some media for the first time).
- We might also want to expose some kind of "permissions" page in our app's settings, even if that just directs to system settings, just to make it clear to the user that we have granular notification permissions settings that they might need to check.
- We should also make sure to connect with SuMo to help them document the various expected bugs that will occur if a user has not accepted permissions for any particular channel, and how to go into system settings to fix that.
Reporter | ||
Updated•2 years ago
|
Blocks: modern-permission-handling
Updated•2 years ago
|
You need to log in
before you can comment on or make changes to this bug.
Description
•