glyca_android-ttp-error

[split tide]

👋 Welcome to your new thread!

⏲️ We'll be here soon! Typically we respond in a few minutes, but sometimes we might take a bit longer if the server is busy or if you have a particularly tricky question.

⏱️ We close idle threads, which makes them read-only. Once a thread is closed it won't be reopened, but you can always start a new thread if you have another question.

🔗 This thread will always be available, even after it's closed. You can find it again using Discord's search, or you can save this link: https://discord.com/channels/841573134531821608/1475516947515838578

📝 Have more to share? Add more details, code, screenshots, videos, etc. below.

[blissful plinth]

We use the latest Stripe Terminal SDK 5.2.0

[safe tulip]

Looking in to this. Do you have any info on when specifically this error is thrown? Like is it when the card is tapped, or when some Stripe SDK code is called before the screen even asks for a card?

[blissful plinth]

Unfortunately we do not know. It must be during the processPaymentIntent call, but we don't know when after that.

                        CollectPaymentIntentConfiguration collectConfig = new CollectPaymentIntentConfiguration.Builder ().build ();
                        ConfirmPaymentIntentConfiguration confirmConfig = new ConfirmPaymentIntentConfiguration.Builder ().build ();

                        Terminal.getInstance ().processPaymentIntent (
                            pi, collectConfig, confirmConfig,
                            new PaymentIntentCallback () {
                                @Override
                                public void onSuccess (PaymentIntent processed) {
                                    Log.i("[TERMINAL]", "Payment OK. status=" + processed.getStatus ());
                                    nativeOnStripeTerminalPaymentProcessed ();
                                }
                                @Override
                                public void onFailure (TerminalException e) {
                                    Log.e("[TERMINAL]", "Payment failed: " + e.getMessage (), e);
                                    reportStripeError ("processPaymentIntent", e, pi.getId ());
                                }
                            }
                        );

(When we arrive at this point, the Terminal is properly initialized and ready)

[safe tulip]

Unfortunately not finding much on this. Do you have the full stack trace for an instance of this? It looks like it is supposed to be a generic message for an unhandled error so it is hard to say what may be triggering it without more context. Looking into if we have recommendations on how to dig further in to this

[blissful plinth]

Maybe you can see something on your end with the payment intent ID pi_3T3wUmAXuBhZG0px0MIEagtz or maybe more useful the terminal reader id tmr_GZjxFgyyLDHYwG ?

I understand that without device access it is hard to debug (I have no specific stack trace), but I'm open to any pointers you may have indeed to dig further into this

[safe tulip]

No errors logged there unfortunately. That does make a certain amount of sense because that looks like a local error, wheras if the Stripe backend raised an error (even a 500 internal server error), the client should know how to handle an error response and display the error.

I am having trouble finding more debugging steps, reaching out to my colleagues to see if they have a better idea

[safe tulip]

It could be helpful to enhance your logging, both by adding more log lines to see what the last Stripe call is before the error and to log the full stack trace if possible. It will also be helpful to collect info from the end-users that have reported this. Like how often does this happen, does it seem to effect all devices, or only some, what do they do to get to the point where this specific error breaks?