How does AppAuth work with an App Extension where there is no AppDelegate?
Nobody has claimed this yet.
- Dominant language
- Objective-C
- Stars
- 2k
- Forks
- 867
- Avg merge
- 4d 48m
- Merged PRs (30d)
- 1
Description
From the Authorizing – iOS example, it appears to me that AppAuth always assumes that it has to run in a context of an iOS (containing) app because AppAuth expects "UIApplication.shared.delegate" to be available for handling the redirect.
How is this supposed to work in an iOS App Extension where there is no "UIApplication.shared.delegate"? In the context of an app extension, I only have NSExtensionContext. Please help.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the Authorizing – iOS example and trace the redirect-handling path that expects UIApplication.shared.delegate. Compare that flow with the NSExtensionContext available to an app extension, then determine whether the result should be documented as supported usage or require a defined implementation change.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- objective-c
- Domain
- authentication, mobile-dev
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100