Skip to content

Conversation

@brycnguyen
Copy link

I am having issues with using a custom redirect URL on iOS where I am unable to get back a response from my request when logging in. For example my redirect uri is: com.some.random.app:/callback

https://stackoverflow.com/questions/52392359/custom-uri-scheme-unsupported-url

https://stackoverflow.com/questions/67368483/ios-react-native-fetch-with-redirect-to-custom-url-scheme-fails-with-network-re

It seems to be related to the issues above.

@mrj0
Copy link

mrj0 commented Apr 10, 2025

Thank you @brycnguyen for this code, it solved my problem as well. After upgrading to Expo 52 and iOS target 15.1, something broke with the custom schema redirect. I could see successful responses in the network panel but would get this -1000 Authentication error.

@cbartel
Copy link

cbartel commented Apr 14, 2025

Hi,
not 100% sure if this is the same issue, but we had issues with the redirect and expo aswell.

delegate: RedirectBlockingURLSessionDelegate.shared,

the custom delegation does not work well with expo dev tools which injects a custom protocol handler
https://github.com/expo/expo/blob/32ceab8e8f23a5b7439e55a223330c66fd308de0/packages/expo-dev-launcher/ios/DevLauncherNetworkInterceptor.swift#L75

We are currently forced to patch ExpoRequestInterceptorProtocol.swift to not interfere if our custom scheme is used.

@rmendonca
Copy link

Hi @cbartel,
how exactly do you patch ExpoRequestInterceptorProtocol, can you share ? I have the same problem and I think patch expo-dev-launcher will be easier than patch the pod and okta-oidc-ios.
Thanks

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants