Please provide the following:
- SDK Version: 36.0.0
- Platforms(Android/iOS/web/all): Android/iOS
When using SDK 35.0.0 I had the following experience:
import { Linking as ExpoLinking } from "expo";
ExpoLinking.makeUrl("MagicLink", {to: 'Home')
would return
exp://127.0.0.1:19000/--/MagicLink?to=Home
I would then call const { path, queryParams } = ExpoLinking.parse("exp://127.0.0.1:19000/--/MagicLink?to=Home&token=x-xgDALR4LivucAL8SjE")
which would properly return path = “MagicLink”.
Now that I have updated to SDK 36.0.0 this same flow results in a path = “–/MagicLink” which causes issues as that route does not exist.
I am currently parsing out the “–/” but just seems like this shouldn’t be the expected behavior