How to handle dev-builds after migration from custom scheme to AppLinks and Universal links?

Get Help
,
1

I’m running two native apps. 1 for iOS and 1 for Android and using the WebAuth like this in apps:

On android (similar on iOS)

Code:

WebAuthProvider.login(auth0)
//.withScheme("https") //- dont work on dev builds. How to solve that?
.withScheme("mycustomscheme")
.withAudience("……”)
.withScope("…….")
.start(…..)

build.gradle:

manifestPlaceholders += mapOf(
"auth0Domain" to "``my.domain.com``",
"auth0Scheme" to "mycustomscheme"
//"auth0Scheme" to "https" //- dont work on dev builds. How to solve that?
)

I’ve had the custom scheme for Android and iOS for years but now its recommended to move to AppLinks/UniversalLinks with https instead according to the last email from Auth0.

So i did that, setting up everything and it seems to work on production builds that is signed with my keystore on iOS.

But on dev builds (still same package name but not release-signed) the login fails all the time when i tested on Android, guess its because its not signed with the release keystore.

How are we supposed to handle this case? Cannot find anything about this when searching the community either :thinking: I would prefer to use the same scheme for production and dev builds so that I test the same as my real users. Is that possible?

3

Hi @kristoffermatsson

Good to see that you are migration to Universal Links in your application!

The scheme should not be an issue regarding your configuration, I believe the issue might be caused by the fact that the production application is using the Release KeyStore whereas the development build should be using a Debug KeyStore which you have not configured within the application’s settings in the Dashboard.

You will need to retrieve your Debug SHA-256 Fingerprint then you will need to navigate to the dashboard, Application → Application → Your Native App → Advanced Settings → Device Settings → App Package name and Key Hashes.
Here you will need to add the debug fingerprint inside the Key Hashes field, you can have both the production and debug key hashes here by using a comma separated list. Once you have saved the settings, Auth0 will update the hosted assetlinks.json file at https://{your_domain}/.well-known/assetlinks.json to include both your production and debug signatures.

Let me know if the solution above helps you solve the issue!

Kind Regards,
Nik