Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Permissions controller cannot handle requests that become outdated after presentation #65

Open
shagedorn opened this issue Aug 25, 2016 · 0 comments
Labels
Milestone

Comments

@shagedorn
Copy link
Contributor

  • present the permissions controller (the container)
  • while presented, one or more "waiting" (i.e., not visible, but queued) requests becomes outdated, i.e., it cannot be presented anymore
    • this may happen when a system alert is unintentionally triggered, see Demo app requests Camera access after launch #64
    • can also happen when multiple requests (modern and legacy) are presented that share one system permission, e.g., AssetsLibrary vs Photos, AddressBook vs Contacts (currently not implemented), Local/Remote Notifications vs User Notifications

Expected result:
The stale permission is skipped silently.

Actual result:
The stale permission is skipped, but another one is presented twice, at least when opting for "Later".

@shagedorn shagedorn added the bug label Aug 25, 2016
@shagedorn shagedorn modified the milestone: 2.0 Aug 26, 2016
@shagedorn shagedorn modified the milestones: 2.1, 2.0 Oct 18, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant