Native SSO UX issue when viewing the Privacy Policy
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 293
- Forks
- 132
- PR merge metrics
- No merged PRs in 30d
Description
Hi,
there seems to be an issue with the SSO process when the user is viewing the Access to Information OAuth2 consent screen, after tapping on the "(APP NAME) will use this information according to its (Privacy Policy)" link.
Once tapping on the link, the correct page opens, but when pressing the Back button once on the device to go back from the Privacy Policy to the SSO page, the SSO page closes, which results in a failed login result. The expected behaviour is to remain on the SSO page so the user can approve or reject the consent form, after viewing the Privacy Policy.
We are using com.uber.sdk:rides-android:0.6.+
Thanks.
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 source file or test is named. Reproduce the flow from the Access to Information OAuth2 consent screen, open the Privacy Policy, and press the device Back button; trace the native SSO navigation and verify that the consent screen remains available so the user can approve or reject the request.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- android, java
- Domain
- authentication, mobile
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100