#cargo.insiten-react-native

1 messages · Page 1 of 1 (latest)

languid stone
#

Hello 👋
Give me a moment to catch up here, I'll respond as soon as I can 🙂 thanks

#

what errors are you seeing exactly? Can you share the traces/logs?

spare zealot
#

sure, give me just a second to reproduce the issue and capture some logs

languid stone
#

NP! 🙂

spare zealot
#

sorry this is taking so long. I actually am dealing with a different issue. I'll have those logs soon

languid stone
#

👍

spare zealot
#

thank you for your patience. there are three possible outcomes on device waking:
1. the presentPaymentSheet method does not return anything yet and continues to function normally
2. the presentPaymentSheet method returns this object and does not close the payment sheet. attempting to use the payment sheet appears to work but the code has already returned so it does not actually work.
present payment sheet result Object {
"error": Object {
"code": "Canceled",
"declineCode": null,
"localizedMessage": "The payment has been canceled",
"message": "The payment has been canceled",
"stripeErrorCode": null,
"type": null,
},
}
3. the presentPaymentSheet method returns this object (the same response as from a successful payment confirmation). the payment sheet stays open. In a downstream call we have an error because the subscription's invoice status is not "succeeded"
present payment sheet result Object {
"paymentOption": undefined,
}

lapis ivy
#

Hi there 👋 taking over for hanzo.

Is there any rhyme or reason as to which of the 3 possible outcomes is achieved? If I understand correctly, you are getting each of these three outcomes at different times, yes?

spare zealot
#

it seems pretty random. only one of the three outcomes occurs each time I reproduce the bug

#

It seems like outcome 2 is most common

lapis ivy
#

I'm going to get a second opinion and see if we can offer any insight. I'll circle back in a few minutes

spare zealot
#

ok thanks!

lapis ivy
#

Okay, so it looks like this could be a bug. The default behavior seems dubious. Would you mind creating an email thread and include both your handle and mine (two-shoes) so we can file a bug report and get the product team to look at it?

spare zealot
#

sure, no problem

#

do I create the email thread here on discord somehow? sorry, I'm new

lapis ivy
#

Just start an email thread with the above info