LinusU / LinusU/flutter_web_auth
iOS Authentication works in 0.4.0, but not in 0.4.1 - AQUIRE_ROOT_VIEW_CONTROLLER_FAILED
Nobody has claimed this yet.
- Dominant language
- Dart
- Stars
- 213
- Forks
- 261
- PR merge metrics
- No merged PRs in 30d
Description
I have an example app which authenticates with multiple identity providers, including Auth0 and Okta. Using 0.4.0, both buttons work on Android and iOS, but using 0.4.1, one button always results in an AQUIRE_ROOT_VIEW_CONTROLLER_FAILED error on iOS. For now, I will use 0.4.0, but I'm concerned I won't be able to update in the future.
As I understand it, the change was to support Flutter apps with "add to app" use cases, but I think this may have broken for "pure" Flutter apps. I'm having trouble debugging the plugin, but I wonder if it should check for `UIApplication.shared.delegate?.window??.rootViewController as? FlutterViewController` first, and then check for `UIApplication.shared.keyWindow?.rootViewController`.
Contributor guide
No contributing guide indexed for this repository
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
Compare the iOS authentication behavior between plugin versions 0.4.0 and 0.4.1, focusing on the code that resolves the root view controller and the AQUIRE_ROOT_VIEW_CONTROLLER_FAILED path. Reproduce the Auth0 or Okta flow in the example app on iOS and verify that pure Flutter apps still authenticate while add-to-app use cases remain supported.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- dart, flutter, ios
- Domain
- authentication, mobile
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100