You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In version 0.37, we were able to use universal links (e.g., https://example.com/app/redirect) as the returnUrl when finalizing the payment. This worked reliably across both iOS and Android. Now I have the problem on iOS, Android works fine because it is not listening on the returnUrl
After migrating to version 0.46, that support the new architecture (Fabric/TurboModules), this behavior no longer works. The universal link is not triggering the app anymore.
We are aware that the current documentation explicitly states that universal links are not supported as returnUrl. However, we would like to understand why this support was removed or is currently unsupported in the new architecture — especially considering it worked fine in 0.37.
Expected behavior
Universal links passed as returnUrl should behave as they did in version 0.37 — opening the app when the flow completes.
Current behavior
With new architecture versions, the universal link is ignored or fails silently. The app does not get re-opened, and there is no fallback or error.
We understand universal links are not currently supported according to the docs, but:
Why exactly was support dropped or is no longer functional?
Is this a known limitation due to architectural constraints?
Can we expect support for universal links as returnUrl to return in a future release?
This was a useful feature for handling redirection in a secure and clean way. If possible, we'd really appreciate insight into whether a fix is planned or if there's a recommended alternative.
Thanks in advance!
The text was updated successfully, but these errors were encountered:
In version 0.37, we were able to use universal links (e.g., https://example.com/app/redirect) as the returnUrl when finalizing the payment. This worked reliably across both iOS and Android. Now I have the problem on iOS, Android works fine because it is not listening on the returnUrl
After migrating to version 0.46, that support the new architecture (Fabric/TurboModules), this behavior no longer works. The universal link is not triggering the app anymore.
We are aware that the current documentation explicitly states that universal links are not supported as returnUrl. However, we would like to understand why this support was removed or is currently unsupported in the new architecture — especially considering it worked fine in 0.37.
Expected behavior
Universal links passed as returnUrl should behave as they did in version 0.37 — opening the app when the flow completes.
Current behavior
With new architecture versions, the universal link is ignored or fails silently. The app does not get re-opened, and there is no fallback or error.
Steps to reproduce
Use a universal link like https://example.com/app/redirect as the returnUrl.
Trigger the external flow (e.g., authentication or deep linking action).
Observe that the app is not opened upon completion in new architecture builds.
Environment
Library version: "@stripe/stripe-react-native": "0.46.0",
React Native version: "react-native": "0.79.1",
Platform: iOS
Using new architecture: ✅
Question
We understand universal links are not currently supported according to the docs, but:
Why exactly was support dropped or is no longer functional?
Is this a known limitation due to architectural constraints?
Can we expect support for universal links as returnUrl to return in a future release?
This was a useful feature for handling redirection in a secure and clean way. If possible, we'd really appreciate insight into whether a fix is planned or if there's a recommended alternative.
Thanks in advance!
The text was updated successfully, but these errors were encountered: