Skip to content

Universal links no longer supported as returnUrl in new architecture versions #1933

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
remllov91 opened this issue May 14, 2025 · 0 comments

Comments

@remllov91
Copy link

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!

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

No branches or pull requests

1 participant