snack
snack copied to clipboard
expo
Deep linking / AuthSessions don't function - "Can't make a deep link into a standalone app with no custom scheme defined"
Summary
Expo Snack features that use deep linking like AuthSessions cause Snack to throw the following error when previewing on Android and iOS:
Can't make a deep link into a standalone app with no custom scheme defined
This issue also occurs when opening the example on a device through the Expo Go app's project section, but not when running the same code in a newly created expo app on a computer.
What platform(s) does this occur on?
Android, iOS
SDK Version
40
Reproducible demo or steps to reproduce from a blank project
https://snack.expo.io/@dylmye/reddit-auth-code - the result of clicking on the snack button from here
https://snack.expo.io/@dylmye/authsession-case-issue - one I made myself with a app.json with a schema defined
We've also seen this in Expo SDK 44. It comes from https://github.com/expo/expo/blob/35f78160a9ec1758ca73eb9e079a1c278c9b1bb1/packages/expo-linking/src/Schemes.ts#L125 - but still trying to figure out what and why it happens.
Seems like the scheme property in some cases is undefined https://github.com/expo/expo/blob/e7f227977ff7aaadbabe8f0128c4f68a52462b06/packages/expo-auth-session/src/tests/SessionUrlProvider-test.ts#L152
Is there any progress on this issue? I'm facing this on expo SDK 41 after I updated the SDK from 40 to 41
Running into this now. Seems like a pretty big issue as we can't bundle our app with linking unless this is fixed
Running into this now. Seems like a pretty big issue as we can't bundle our app with linking unless this is fixed
Hello have you been able to fix this?
Also stuck on this, though I'm attempting to build a staging configuration locally to troubleshoot something. Not sure if that's correct to do even.
I found a solution https://reactnavigation.org/docs/deep-linking/#setup-with-expo-projects
I am trying to implement AuthSession in snack but it gives me the same error. In the local setup the same code works well.
unrelated, i was getting the issue while starting up the app the app was crashing. for me the issue was the scheme and my android package name were differrent. once i fixed them. it worked.
I'm getting this error only after eas building and uploading to the Play Store. when I download and launch the app it crashes. with the message "cannot deep link into standalone app with no scheme defined", but everything works fine in expo go.
unrelated, i was getting the issue while starting up the app the app was crashing. for me the issue was the scheme and my android package name were differrent. once i fixed them. it worked.
I have exactly the same error. can you explain how to do this, please?
unrelated, i was getting the issue while starting up the app the app was crashing. for me the issue was the scheme and my android package name were differrent. once i fixed them. it worked.
I'm just curious how this could possibly be a solution? My understanding is that package name does NOT have to be the same as the scheme. Unless I am wrong here?
Seeing this issue on iOS, Expo SDK 50.
I am not sure if this will help anyone else but we had a bug that closely resembled this issue with the consistent error was
Cannot make a deep link into a standalone app with no custom scheme defined
Even though a scheme was defined. The problem was caused by importing and calling react-navigation libraries while also using expo-router. For us, it was easier to remove expo-router but as long as the correct libraries are called in conjunction with each other, this may someone else.
react-navigation
unrelated, i was getting the issue while starting up the app the app was crashing. for me the issue was the scheme and my android package name were differrent. once i fixed them. it worked.
I have exactly the same error. can you explain how to do this, please?
hi, same here. did you fix it at last?
