# How to handle dev-builds after migration from custom scheme to AppLinks and Universal links? **URL:** \ **Category:** Get Help\ **Tags:** configuration, application\ **Created:** [November 25, 2025, 8:51am UTC](https://community.auth0.com/t/how-to-handle-dev-builds-after-migration-from-custom-scheme-to-applinks-and-universal-links/194880 "2025-11-25T08:51:12Z")\ **Posts on this page:** 1\ **Showing post:** 3
**Author:** ![nik.baleca](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/nik.baleca/32/68749_2.png) [@nik.baleca](https://community.auth0.com/u/nik.baleca)\ **Post date:** [November 25, 2025, 7:33pm UTC](https://community.auth0.com/t/how-to-handle-dev-builds-after-migration-from-custom-scheme-to-applinks-and-universal-links/194880/3 "2025-11-25T19:33:53Z")
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 --- _[View the full topic](https://community.auth0.com/t/how-to-handle-dev-builds-after-migration-from-custom-scheme-to-applinks-and-universal-links/194880)._