Sessions DropIn can't be completed after dismiss

[johanehinger]

You can't complete a payment if the DropIn has been dismissed once.

To Reproduce

Steps to reproduce the behavior:

1. Go to Sessions Checkout
2. Press on DROP-IN
3. Dismiss the DropIn component using the close button.
4. Press on DROP-IN again
5. Press on Credit card
6. Fill in information and press pay.

The DropIn will now never trigger the onComplete callback and we won't be redirected to payment confirmation. We will be stuck in a loading state forever.

unhayyp.path.trimmed.mov

Expected behavior

The expected behavior is that no matter how many times you open the DropIn you should still be able to run the onComplete. If you never dismiss the DropIn this works great

happy.path.trimmed.mov

Additional context

I'm running your provided examples on a simulator, but the same issue is reproducible in different variations in our live app too.

[descorp]

Hey @johanehinger, thank you for feedback.

What happens here is that component.hide(...) cleans up the session internally. As a result, the second Drop-in you see is actually the "Advanced case" Drop-in, which expects an onSubmit callback.

This is Example app bug caused by a sort of expected behaviour:

The Sessions Drop-in flow was designed with the assumption that if a shopper closes the Drop-in, they are
a) abandoning payment;
b) making significant changes (adding/removing items or applying a discount code etc);

Both means that the /sessions would be requested again.

---

For now, the way to work this around is to re-render (for example by navigating back to "Checkout confirmation" step).

---

We are about to introduce components for Sessions in React Native SDK v3; behaviour in question will likely change towards your expected behaviour. We will keep you posted.

[johanehinger]

Thank you for looking into this @descorp

I completely missed this "switching to Advanced case", where can I read about this behaviour in the documentation?

[descorp]

I completely missed this "switching to Advanced case", where can I read about this behaviour in the documentation?

Normally, merchant choose \sesisons or \payments (aka Advanced) flow and stick to it.

You have spotted a bug in a current Example app: the app should navigate back to Main menu once DropIn is canceled, instead it stays on the same view and that cause described behaviour.