#thiagomacauba88_api
1 messages ยท Page 1 of 1 (latest)
Below are links to other discussions we've had with you in the past week in case you want to review that information. If your question is related to one of these previous discussions, please provide a comprehensive summary of the current state and what you need help with now. We help many users simultaneously, so a summary allows us to resolve your issue as soon as possible.
- thiagomacauba88_api, 21 hours ago, 56 messages
- thiagomacauba88_api, 1 day ago, 15 messages
๐ Welcome to your new thread!
โฒ๏ธ We'll be here soon! We typically respond in a few minutes, but in some cases we might need a bit more time (e.g., server's busy, you've got a complex question, etc.).
โฑ๏ธ We close idle threads, which makes them read-only. Once a thread is closed it won't be reopened, but you can 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/1255611158568636486
๐ Have more to share? Add details, code, screenshots, videos, etc. below.
hey
1 sec
I'm stuck on this
when I test ttp on android
i was talking to another person yesterday
and he asked my readerId = e5511944-b839-4b8a-9705-4c5da203ed23 (this one is for now)
Okay and what error do you see exactly?
Or there is no error?
And it is just frozen on that screen?
Can you show me your client-side code here?
you mean the payment method?
No I mean your client-side code for your Tap to Pay integration
Or are you working with a third party here?
I see some reference to "chargestripe" in your logs
chargestripe is our project
this is the ttp fragment, we are connecting in this fragment and we are doing the payment in another one
but if something was wrong to connect... i shouldn't see the TTP screen... or am i wrong?
Most likely
However if there was a disconnection issue or something then that could be the culprit
Hard to say exactly
But yeah if you can share your payment method collection code that would certainly be helpful
this class is kind of a mess right now, a lot of things going on here.... but maybe you have a guess
While I look, you said e5511944-b839-4b8a-9705-4c5da203ed23 was a serial ID?
Can you reproduce with that phone right now?
Then I can also look at our internal logs
Thanks
just tried
Also have you tried on any other device?
yep, i don't have another device right now... but another person tried using a pixel 4
and the result was the same
what about your logs?
Hmmm do you have Programmatic cancellation (https://docs.stripe.com/terminal/payments/collect-card-payment?terminal-sdk-platform=android#programmatic-cancellation) set up anywhere in your code?
I'm seeing that the payment method collection was canceled
1 sec
what i have is this:
Terminal.getInstance().collectPaymentMethod(
paymentIntent,
object : PaymentIntentCallback {
override fun onSuccess(paymentIntent: PaymentIntent) {
processPayment(paymentIntent)
}
override fun onFailure(exception: TerminalException) {
runOnUiThread {
context?.toast(exception.errorMessage)
lottieLoading.visibility = View.GONE
}
}
})
let me put a breakpoint and check if what i have again
And nowhere do you use that cancelable variable?
Ah you aren't setting a cancelable at all...
yep
not for collectPayment
Terminal.getInstance().retrievePaymentIntent() it's working
but Terminal.getInstance().collectPaymentMethod(
i dont have any feeddback
What version of the Terminal Android SDK are you using?
implementation "com.stripe:stripeterminal:2.21.1"
implementation "com.stripe:stripeterminal-localmobile:2.21.1"
Hmmm that's pretty old
if i jump to the latest i'll need to rebuild a lot of things :/
This is definitely weird -- the only thing I see from our internal logs is that you call collectPaymentMethod() and then that request is immediately canceled
any reason for the cancel?
Terminal.getInstance().retrievePaymentIntent(
clientSecret,
object : PaymentIntentCallback {
override fun onSuccess(paymentIntent: PaymentIntent) {
Terminal.getInstance().collectPaymentMethod(
paymentIntent,
object : PaymentIntentCallback {
override fun onSuccess(paymentIntent: PaymentIntent) {
processPayment(paymentIntent)
}
override fun onFailure(exception: TerminalException) {
runOnUiThread {
context?.toast(exception.errorMessage)
lottieLoading.visibility = View.GONE
}
}
})
}
override fun onFailure(exception: TerminalException) {
runOnUiThread {
context?.toast(exception.errorMessage)
lottieLoading.visibility = View.GONE
}
}
})
should be work ๐ฆ
Yeah not seeing any further explanation in the logs
Let me ask a teammate for a second pair of eyes
thanks
hey @kindred wadi do you have any ideas?
Apologies for the wait. I'm catching up on the thread and I have another more experienced mobile dev to assist. I'll circle back when I have more info
@warped dew can you try upgrading your SDK version and see if that resolves the issue? It looks like you're on 2.21.0 which is pretty old
well i cant go to much further, i tried 3.6 but i need to refactor the whole app
what version do you suggest?
The latest version is ideal. We're not sure what's causing the hang up at this point, so upgrading the version is the last step before we escalate to the product eng team (who is going to tell you to upgrade anyway).
where can i get the list of versions? github?
I would think that 3.0.0 is a good start if you want to progressively upgrade from there, since that's where the bulk of the more foundational changes occur: https://github.com/stripe/stripe-terminal-android/blob/master/CHANGELOG.md#300---2023-09-08
ok
com.stripe:stripeterminal
com.stripe:stripeterminal-localmobile
should be the same version
right?
yes