Any ideas of how to customise Incoming Deep Links in this RFC?

[AlvSovereign]

Hi all

I'm currently dealing with handling authentication that uses a # character in the deep link URL, which Expo Router does not handle as a search param and therefore cannot find the screen needed to deal with auth tokens.

This was achievable via React Navigation which needed a linking prop, where I could customise the config to rewrite the incoming URL to replace the # with a ?.

Any ideas?

[AlvSovereign]

I ended up patching the Linking config to resolve this:

diff --git a/node_modules/expo-router/build/getLinkingConfig.js b/node_modules/expo-router/build/getLinkingConfig.js
index 19f1cdb..612299a 100644
--- a/node_modules/expo-router/build/getLinkingConfig.js
+++ b/node_modules/expo-router/build/getLinkingConfig.js
@@ -63,7 +63,19 @@ export function getLinkingConfig(routes) {
         config: {
             // @ts-expect-error
             initialRouteName: routes.initialRouteName,
-            screens: getReactNavigationScreensConfig(routes.children),
+            // START OF PATCH
+            screens: {
+                ...getReactNavigationScreensConfig(routes.children),
+                'auth-challenge': {
+                    parse: {
+                        'auth-challenge#access_token': (path) => {
+                            return path
+                        },
+                    },
+                    path: '/:auth-challenge',
+                },
+                // END OF PATCH
+            },
         },
         // A custom getInitialURL is used on native to ensure the app always starts at
         // the root path if it's launched from something other than a deep link.