I have a view that:
- Creates an observer for
UIApplicationDidBecomeActiveNotification
with invokes a selector - Sequentially asks the user for permissions to: use the camera, location & receiving push notifications.
- The view has three
UIButton
s with state depending on each permission state, which navigate the user to settings if permissions for anything were rejected - Tapping a button which represents a permission with rejected state navigates the user to settings
- Once each alert hides, using the observer action, next alert is triggered and all button states are updated to reflect any changes
Once all permissions are granted it pushes next view with the rest of the signup/in flow.
The problem is: on some devices, when running the app from a clean state (app removed and reinstalled), permissions for location & notifications are set to rejected by default, as if the user was presented an alert that was rejected.
I couldn't pinpoint any rational issue behind this, except for leftover settings from some outdated build that don't get deleted when installing a new one. This view seems to be the only place that can possibly trigger these alerts.
Did anyone have a similar issue and can suggest anything?