Linking.parse keeps "--/" in path

Please provide the following:

  1. SDK Version: 36.0.0
  2. 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


I would then call const { path, queryParams } = ExpoLinking.parse("exp://") 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

The parsing was changed in this pull request.

Please can you create a new issue here with the details of the change in behaviour from SDK 35 to SDK 36? Or if you think it’s just a difference instance of this issue, then it would probably be best to add a comment there.

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.