#deadshot_error
pseudo lodgeBOT
👋 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/1394407841237958828
📝 Have more to share? Add more details, code, screenshots, videos, etc. below.
grizzled raptor
fading matrix
Hello, looking in to this. Have you been working with your M2 for a bit, or has this behavior been present ever since you started trying to work with it?
grizzled raptor
No, this was not happening until i used stripe terminal SDK version v3.9.5
Started happening when i upgraded to 4.4.0
implementation ('com.stripe:stripeterminal-core:4.4.0')
implementation 'com.stripe:stripeterminal-handoffclient:4.4.0'
implementation ('com.stripe:stripeterminal-taptopay:4.4.0')
Here's the logcat file for you to analyse. If it helps
fading matrix
Gotcha, can you send me your code for connecting to the reader and initiating the payment? My colleague tried to reproduce this issue but wasn't able to. We want to make sure we're testing as close to your setup as possible, and this may need to be escalated to the eng team
fading matrix
Thank you, bringing this back to my colleague and will get back with what we can find.
grizzled raptor
Sure.
Here the video of what's happening. Check for pos-stripe-latest-version
@fading matrix , Just want to let you know that this issue is a P0 that we are facing in production and we are in a very critical situation. So it will be great if we can get a solution or a workaround as soon as possible. Its impacting our customer sentiment
fading matrix
Thanks for the context, escalating as best we can. One more quick thing, can you send the serial number of a reader seeing this issue (preferably the one from the screenshot if you have it handy?)
grizzled raptor
Sure
STRM26214080078
Also, this is on all the M2 readers both through USB and BLE connection modes
fading matrix
And to make sure I understand the context fully, you just pushed a new version of your android app that uses this new terminal SDK version, so pushing a new one that reverts that change would be diffcult?
grizzled raptor
We are totally fine with S700s
grizzled raptor
And to make sure I understand the context fully, you just pushed a new version o...
Yeah about that, only the newer SDK supports the eligible amount calculation for pre tipping cases for S700, in the older SDK version the tip percentages were calculating from the grant total and we want it to calculate from the subtotal of the order
fading matrix
Ah I think I may see a report about this from you from earlier today, so reverting to 4.4.0 resolves the memory issues but the loss of the feature is hurting customer sentiment?
grizzled raptor
Yes
fading matrix
Gotcha, just making sure I understood the full situation.
grizzled raptor
We want that feature as well, and our customers use both M2s and S700 so we cannot have two different release as well
fading matrix
Gotcha, thanks for the context. Escalated this and will let you know what I hear back. We may need to move this to an email thread depending on what followup looks like. Will let you know when I hear more
grizzled raptor
Sure Thanks a lot @fading matrix
fading matrix
Can you test this again while passing autoReconnectOnUnexpectedDisconnect = false and see if you still see this behavior?
https://docs.stripe.com/terminal/payments/connect-reader?terminal-sdk-platform=android&reader-type=usb#handle-disconnects
grizzled raptor
Where you able to reproduce this?
Coz, Currently i don't have a M2 reader with me as I left my office space
pseudo lodgeBOT
plush quarry
👋 stepping in for my teammate. We haven't tried to reproduce on our end yet but have escalated your issue. We'll need to move this to an email thread so we can continue to provide updates there.
pseudo lodgeBOT
Hello @grizzled raptor, we have sent you a direct message, please check it at https://discord.com/channels/@me/1394421384582664202
- 🔗The message has instructions on how to open a direct support case with our Developer Support team, in order to help you more effectively.
plush quarry
I don't have a resolution at the moment so, for now, please follow the steps in the DM to open a support case with us
grizzled raptor
I already have a support case going on. Anna gave me this discord channel to directly contact engineering team
plush quarry
Ah, I was not aware of that. Give me a mins to find that case
grizzled raptor
Sure
plush quarry
Ah, I see you have two open cases actually and that you were working with my teammate, Jack. We'll continue to keep you updated via Jack's thread
grizzled raptor
I didn't get a resolution there, that's why i've tried through discord channel.
plush quarry
I see Jack most recently asked for more details to try to reproduce
I think we have what we need now based on what you shared in Discord though
grizzled raptor
Yes
plush quarry
We'll follow up over email with next steps
grizzled raptor
Please let me know if guys found anything or is there any temporary workaround for this to not happen