With this documentation change, we are making custom scheme mandatory. This is due to the reason that Expo uses the application ID or bundle identifier we use to as the scheme to open the application. This shows a popup when the login is done successfully and choosing the wrong option could break the application flow.
For this reason we have made custom scheme as mandatory for Expo application and added guidance on how to do it.
This will change in the next major where we will generate the scheme for callback URL with auth0 prefixed to the package name to avoid clash with Expo
Changes
With this documentation change, we are making custom scheme mandatory. This is due to the reason that Expo uses the application ID or bundle identifier we use to as the scheme to open the application. This shows a popup when the login is done successfully and choosing the wrong option could break the application flow.
For this reason we have made custom scheme as mandatory for Expo application and added guidance on how to do it.
This will change in the next major where we will generate the scheme for callback URL with
auth0prefixed to the package name to avoid clash with ExpoReferences
Issues were raised because of this
https://github.com/auth0/react-native-auth0/issues/582 https://github.com/auth0/react-native-auth0/issues/606
PR in repo - https://github.com/auth0/react-native-auth0/pull/610 PR in Docs - https://github.com/auth0/docs/pull/10243