#robert_63480
1 messages · Page 1 of 1 (latest)
Hi
com.stripe.stripeterminal.external.models.TerminalException: failed to connect to 192-168-50-117.yqydf6mfou6qtnk3b2yn.device.stripe-terminal-local-reader.net/192.168.50.117 (port 4443) from /192.168.50.249 (port 38700)
This seems to be a connectivity issue
Did you try to check the network you are using or treid another one ?
yes, we need to increase the timeout from 10 seconds to 30 seconds at least
because the issue is not connectivity, but when the terminal is under processing state for more than 10 seconds, this sdk function will throw timeout exception.
com.stripe.stripeterminal.external.models.TerminalException: failed to connect to 192-168-50-117.yqydf6mfou6qtnk3b2yn.device.stripe-terminal-local-reader.net/192.168.50.117 (port 4443) from /192.168.50.249 (port 38682) after 10000ms
processing state more than 10 seconds, will throw timeout
The error is failed to connect ... after 10000ms and it doesn't seems to be a processing timeout
Can you share the payment_intent Id ?
we have checked in our side, it is due to processing timeout. we cant check the detail because your stripe android sdk is not public in github.
hold on, let me find the payment_intent
hold on
btw, while i am finding the payment intent
we have checked in our side if the processing state is more than 10 seconds, the sdk library will throw the timeout.
Yes there is a a processing timeout
but according to the error you are sharing, it's a connection time out and not processing
but let's confirm this when you share the PaymentIntent Id
ok wait
finally found it: pi_3OJyMcDR6Y5g67tL0PB3hn23
om.stripe.stripeterminal.external.models.TerminalException: timeout
at com.stripe.stripeterminal.internal.common.remotereadercontrollers.CrpcResponseExtensions.withJackrabbitResponse(SourceFile:47)
at com.stripe.stripeterminal.internal.common.remotereadercontrollers.AsyncQueryJob.collect(SourceFile:71)
at com.stripe.stripeterminal.internal.common.remotereadercontrollers.AsyncQueryJob.access$collect(SourceFile:1)
at com.stripe.stripeterminal.internal.common.remotereadercontrollers.AsyncQueryJob$launch$1.invokeSuspend(SourceFile:41)
at s50.resumeWith(SourceFile:9)
at zx1.run(SourceFile:114)
at a99.run(SourceFile:29)
at wx7.run(SourceFile:3)
at nd1.run(SourceFile:94)
^ this is processing timeout?
it seems after this timeout, i will get failed to connect timeout
I just checked the payment intent, and there was no payment attempt/processing
Which means that you have a connectivity issue and not a processing issue, the request didn't reached to Stripe infrastructure
Now I inivte yout to double check your connectivity and see if you have network issues
we dont mind if the payment is processing or failed
but we want to increase the timeout or we want to get the response from stripe at least instead of we get the timeout but your stripe is still in processing
the problem now is
your terminal is still processing, but in application level we already get the timeout
this is confusing to user
No the terminal wasn't able to connect to Stripe
There was no processing attempt on the PaymentIntent Id you've shared
u can see in the image i send you
your terminal is in processing state (i am not sure why). we want your sdk not to throw timeout error, because your terminal is in processing state
if your terminal has returned failed after cannot connect to stripe, then u can throw an error, that is fine
Did you try to use a different network ?
we have
it actually happens during reboot window, that is why i try to activate the beta side
but seems the beta side getting too long and customer is getting angsty
what i am trying to say is
your sdk can throw an error after the terminal already get the final state.
if u are in processing state, why are you throwing an error to sdk? how if this payment successful actually?
Could you share more details about this ?
right now the reboot time is at 12am to 1am, this customer always have this issue during this time
What's happening in the reboot time exactly? can you share more details ?
OK so this is the beta feature you are referring to
there are multiple ways to solve this actually
I invite you reach out to Stripe Support via email.
what is slow ?
they response with the beta activation really slow
we just need this feature to be enabled to get this right
and your team should let us know if you have this reboot time at midnight, we are not aware of this at all
I see, I strongly encourage you to reach out back to Stripe Support as this is a beta feature.