#zishaansunderji - Android Terminal

1 messages ยท Page 1 of 1 (latest)

spice forge
#

HI ๐Ÿ‘‹

formal jay
#

Hi there!

spice forge
#

Do you have any example request IDs from the APIs that correspond to these errors?

formal jay
#

Hey yeah for sure!!

#

Sorry for the late reply - I had to jump into something

#

So the payment intent ID is: pi_3LLD58Fk5BSitd8b0iWej5KR

#

It looks like a pretty normal transaction

spice forge
#

There's a lot going on right now so don't worry about being late. I likely will too

formal jay
#

Haha sounds good!

#

Thanks!!

spice forge
#

Okay there are no errors associated with that payment. Are you sure this triggered an error in the Terminal SDK?

formal jay
#

Yuppp we got an error on the SDK but the readere said the payment processed successfully

spice forge
#

Which...it did.....

formal jay
#

Yupp exactly!

#

Hmm is it possible that the error could be from something other than the process payment?

#

It looks like we could have a connection token request at the same time maybe?

spice forge
#

So your call is hitting the onFailure block, right?

formal jay
#

Yupp!

#

So one nuance about our circumstance is - if you notice it says sendEvent - which is actually used for all reader related methods

#

but we grab all the events and send them together - so if it's a connection issue or payment issue it'll send the event to a stream of logs - which could potentially be causing it?

spice forge
#

Hmmm... that's a bit outside what I am familiar with here TBH

formal jay
#

Gotcha! I'm going to dig into our logger to see if my theory is correct, if I find anything I don't fully understand with any Stripe related outputs I can just message in the Discord

spice forge
#

Sure thing! And I would definitely try to disambiguate all the events in your stream. Like possibly logging which event is received so you can review the Android logs and see if your app is getting overlapping events coming in

formal jay
#

Yuppp makes sense! I'll refactor it that way so we can see each event - at the time it was just easier to log them sequentially to sort it out as opposed to making sense out of them from multiple collections