LinusU / LinusU/flutter_web_auth
Chrome Custom Tab remains open in app switcher after the callback
Nobody has claimed this yet.
- Dominant language
- Dart
- Stars
- 213
- Forks
- 261
- PR merge metrics
- No merged PRs in 30d
Description
The login flow works, but the Chrome Tab doesn't close itself after the app scheme callback.
Adding the NO_HISTORY flag leads to the callback not working correctly: the app receives it, but the browser activity stays on top requiring the user to manually close it after which the flow finishes successfully.
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
Start by reproducing the login flow described in the issue and trace how the Chrome Custom Tab handles the app-scheme callback. The fix is complete when the callback still finishes authentication and the browser activity no longer remains in the app switcher or requires manual closing.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- dart, flutter
- Domain
- authentication, mobile
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100