[Android] 3DSecure confirmation screen closed if app is put in background

Hi all. We currently have a bug happening on Android only. After using confirmPaymentMethod on a payment, the 3DS screen is brought up. If instead of confirming / denying the payment on this screen we go into background and then bring the app back to active again, 3DS screen is just dismissed, so the app is stuck. Obviously, at that moment Stripe payment is pending, but there’s no way to bring up the payment screen again. Even if there was, then the process would be repeated - if the user has to go to the bank’s app in order to confirm the payment or whatever, the problem would come back and always be present.

Note: this does not happen on iOs.

To Reproduce Steps to reproduce the behaviour:

1. Boot Android React Native app.
2. Confirm payment with a 3DS card.
3. When the hooks.stripe.com screen with the confirmation gets brought up, go into background.
4. Wait 2 seconds, open the app again.
5. There you have a problem.

Expected behavior The expected behaviour would be the same as in iOs, for this screen not to be dismissed until the user does some action upon it.

Desktop (please complete the following information): OS: MacOs Big Sur 11.2.3 Browser: Chrome Version: 91.0.4472.77 (Official Build) (x86_64)

Smartphone (please complete the following information): Device: Honor 9 Lite Android version: 9

Additional context Stripe version: 0.1.4 React native version: 0.63.4

Thanks in advance!

[cfeeney5]

Is there any update on this bug? Its causing a lot of issue for customers

[aaronSig]

I’m having the same issue.

To recreate:

• Initiate payment
• Leave the app to check for a 3D secure SMS.
• Re-open the app by clicking on the app icon on the home screen

The payment errors out with “Failed to retrieve a PaymentSheetResult”.

However, if you instead resume the app from the Android Task Switcher everything works as expected.

My manifest looks like:

<activity
    android:name=".MainActivity"
    android:label="@string/app_name"
    android:configChanges="keyboard|keyboardHidden|orientation|screenSize|uiMode"
    android:launchMode="singleTask"
    android:windowSoftInputMode="adjustResize">
    
    <intent-filter>
        <action android:name="android.intent.action.MAIN" />
        <category android:name="android.intent.category.LAUNCHER" />
    </intent-filter>

    <intent-filter>
        <action android:name="android.intent.action.VIEW" />
        <category android:name="android.intent.category.DEFAULT" />
        <category android:name="android.intent.category.BROWSABLE" />
        <data android:scheme="myapp" />
    </intent-filter>	
</activity>

I believe you’re right that changing the singleTask launch mode will fix but this breaks deep linking for our RN Android app.

Would there be another work around?