#thiagomacauba88
1 messages ยท Page 1 of 1 (latest)
hey @autumn wraith
Hi ๐ I'm not too familiar with Android, so I'm checking to see if one of my teammates is.
ok thanks
How long is it typically taking? Is it possible the reader is being updated during that period?
Is this happening consistently across multiple devices (both android device and reader)?
We have a user with this issue
and i just tried to replicate and yes, it happens a lot
we have a beep(reader) and that's all
we have a success some times or just stuck on this
Hello ๐
hey @whole halo
The behavior you're describing is very close to how the reader behaves while its getting updated on initial connection and if it fails then it will try again later.
You said it isn't updating, how sure are you exactly?
Have you implemented the bluetooth listener shown here?
https://stripe.com/docs/terminal/payments/connect-reader?terminal-sdk-platform=android&reader-type=bluetooth#update-reader
give me a couple of minutes and I'll check it
Could you also share the reader serial number? I'll try pull up the logs to see if there's anything relevant there
Sure
Right, In recent logs I see the reader was updated to the latest firmware
So yeah I believe it was installing the updates
If you add the listener described on the link above then you should be able to handle that scenario gracefully
Its quite possible that the update didn't succeed the first time or if the reader was on an old version so it took multiple updates to get it to the latest one
I have everything implemented
override fun onStartInstallingUpdate(update: ReaderSoftwareUpdate, cancelable: Cancelable?) {
runOnUiThread {
toast("Updating reader software")
loadingReaderLocation.visibility = View.VISIBLE
}
}
override fun onReportReaderSoftwareUpdateProgress(progress: Float) {
runOnUiThread {
toast(progress.toString())
}
}
override fun onFinishInstallingUpdate(update: ReaderSoftwareUpdate?, e: TerminalException?) {
runOnUiThread {
loadingReaderLocation.visibility = View.GONE
}
}
I already put breakpoints, but nothing :/
It won't hit the breakpoints now since the reader has updated already
but should I able to see the toast, right?
the user is with this behavior for the last weeks
so, i dont know if is still updating
One thing you can try to check if your code above works as expected is to simulate reader updates
https://stripe.com/docs/terminal/references/testing?terminal-sdk-platform=android#simulated-reader-updates
This would let you test if the toast shows up on update prompt or not
You can use it with simulated reader
https://stripe.com/docs/terminal/payments/connect-reader?terminal-sdk-platform=android&reader-type=simulated
Sure
https://stripe.com/docs/terminal/payments/connect-reader?terminal-sdk-platform=android&reader-type=simulated
the code on this link will show you how to create a simulated bluetooth reader
https://stripe.com/docs/terminal/references/testing?terminal-sdk-platform=android#simulated-reader-updates
On this link, you'll find configuration parameters you can pass in to tell the simulated reader to update
do i need to call this: Terminal.getInstance().simulatorConfiguration before connect?
a question, if i update the reader... Should i keep trying to do that?
do i need to call this: Terminal.getInstance().simulatorConfiguration before connect?
yes it should be before connect
a question, if i update the reader... Should i keep trying to do that?
Not sure I understand, At the moment we're trying to check if that the UI works or doesn't work on reader update
ok, but right now my reader is updated
why am i still stuck on something without any feedback?
why am i still stuck on something without any feedback?
Do you mean you're still seeing long connection time?
I thought you said earlier that it worked fine?
Do you see any bluetooth related errors or exceptions thrown by the SDK in your logcat?
Just that the reader was updating and some logs from android device about bluetooth connection timing out (which is also possible when the reader is connected but inactive for 5 or more minutes).
Can you try cloning the example app from here and connect the reader via that app?
https://github.com/stripe/stripe-terminal-android
I'll do again.. can you check pls?
sure
can you try connecting to the reader multiple times using the example app?
sorry but the example doesnt work for me
I'm still stuck on many loadings
can we try to understand why it taking so long?
That's what I am trying to do. We need to narrow down on what exactly is causing this.
Is it the reader? OR is it your code?
If you're seeing the same behavior with example app then it could be something with the reader.
If you're not seeing the same behavior with example app then it must be your code.
We haven't heard any other complaints regarding slow connection time from other terminal users so I doubt it is related to the firmware.
So if you can get the example app working then we should be able to narrow down on what's causing this
ok
i can't create any location from there
can you explain me why i dont have this issue in qa/dev?
Your code OR configuration might be a little diff in qa/dev
That also indicates that the issue might just be in the code and not with the reader
what configuration?
A different SDK version or something. Just a hunch though.
The next step here would be to see if you can get the example app working then we can check if the reader behaves similarly there.
OR
You can send us the code you have and we can try and reproduce this on our end (this would need to happen async, you'll need to create a ticket via Support)
Ah, maybe that function needs to call your endpoint to create the location ๐ค
Are you able to select any of your existing locations?
no locations
Ah seems like the example expects folks to fill out this function
https://github.com/stripe/stripe-terminal-android/blob/master/Example/kotlinapp/src/main/java/com/stripe/example/network/ApiClient.kt#L49
@old stump I know it has taken a while to narrow down on this.
Can you write in via our support (https://support.stripe.com/?contact=true) with sample of your code so that I can try and reproduce this on my end?
Make sure to mention you can spoke with hanzo on discord
I'll grab the ticket and respond as soon as I can.
ok
let me know once you write in
please share all the classes that implement functions from our Terminal SDK and any other code that runs while you connect to the reader
NP! Let me check if we received it
Interesting, can you just archive them in a zip file and send?
Alternative would be to host the files on Google Drive or something and share the link
Got it. Thanks again for your patience.
I'll respond as soon as I find anything.