AppAuth browser is not retain same screen when user goes on another app to copy code and come back to the app that was in the background.
Nobody has claimed this yet.
- Dominant language
- Objective-C
- Stars
- 2k
- Forks
- 867
- Avg merge
- 4d 48m
- Merged PRs (30d)
- 1
Description
Is your feature request related to a problem you're having? Please describe.
AppAuth browser is not retain same screen when user goes on another app to copy code and come back to the app that was in the background. Once user goes to copy code on another app and come back AppAuth restart journey from login page.
Describe the solution you'd like
User click on Login screen and want to use login details from another app or screen. If Application goes in background still AppAuth should retain same screen where user left. Currently user navigate to back on first login screen. every time user lose all entered detail and restart journey from login. User unable to login if they want to copy and paste login detail from external app.
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
No file or test is named. Start by reproducing the login flow, then trace how the AppAuth browser handles the app entering the background and returning to the foreground. Done means returning from another app preserves the current login screen and entered details instead of restarting the journey.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- objective-c
- Domain
- authentication, mobile
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100