FormidableLabs / FormidableLabs/react-native-app-auth
Apple rejection - We still noticed that the user is taken to the default web browser to sign in or register for an account, which provides a poor user experience.
- Dominant language
- Java
- Stars
- 2.3k
- Forks
- 473
- PR merge metrics
- No merged PRs in 30d
Description
## Issue
Apple rejected with below reason today. Please review and recommend the next step.
Guideline 4.0 - Design
We still noticed that the user is taken to the default web browser to sign in or register for an account, which provides a poor user experience.
Next Steps
To resolve this issue, please revise your app to enable users to sign in or register for an account in the app.
You may also choose to implement the Safari View Controller API to display web content within your app. The Safari View Controller allows the display of a URL and inspection of the certificate from an embedded browser in an app so that customers can verify the webpage URL and SSL certificate to confirm they are entering their sign in credentials into a legitimate page.
---
## Environment
* **Your Identity Provider**: `Azure`
* **Platform that you're experiencing the issue on**: `iOS`
* **Your `react-native` Version**: `~0.73.7`
* **Your `react-native-app-auth` Version**: `^7.1.3`
* **Are you using Expo?** No
Contributor guide
Research direction
Start by reviewing the iOS authentication flow in react-native-app-auth and how Azure sign-in currently opens the default web browser. Compare the available AppAuth behavior with Safari View Controller, then verify that sign-in and registration remain inside the app and satisfy Apple's stated requirement.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- azure, ios, react-native
- Domain
- authentication, mobile-dev
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 28/100