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
Describe the bug
On android when confirming 3D secure, return to merchant does not working with mozilla in app navigator ( but work with chrome )
To Reproduce
Steps to reproduce the behavior:
Set up an android phone with mozilla as default navigator
Add 4000002760003184 this payment method
Call confirmSetupIntent
Click on confirm authentication
When you click on open with mozilla ( in navigator option ), mozilla app is openning and return to merchant button is working, but not with "inApp navigator powered by mozilla"
Expected behavior
I expect the app to go back to the app ( urlScheme is valid and working with chrome ) setUrlSchemeOnAndroid is set to true
Smartphone (please complete the following information):
Device: [e.g. Samsung S10E]
OS: [e.g.Android 11 ]
Browser [Mozilla]
Version [e.g. 22]
The text was updated successfully, but these errors were encountered:
In @stripe/stripe-react-native we bumped the stripe-android version to the one with a possible fix. Can you please try to update @stripe/stripe-react-native to 0.2.0 and check it the error is still there?
Describe the bug
On android when confirming 3D secure, return to merchant does not working with mozilla in app navigator ( but work with chrome )
To Reproduce
Steps to reproduce the behavior:
Set up an android phone with mozilla as default navigator
Add 4000002760003184 this payment method
Call confirmSetupIntent
Click on confirm authentication
When you click on open with mozilla ( in navigator option ), mozilla app is openning and return to merchant button is working, but not with "inApp navigator powered by mozilla"
Expected behavior
I expect the app to go back to the app ( urlScheme is valid and working with chrome ) setUrlSchemeOnAndroid is set to true
Smartphone (please complete the following information):
The text was updated successfully, but these errors were encountered: