#tyrzaphir_unexpected
1 messages Β· Page 1 of 1 (latest)
π 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/1484259200128520242
π Have more to share? Add more details, code, screenshots, videos, etc. below.
hello! fyi the server is a little busy atm but i will be with you asap π
oof just read your question and this sounds urgent, 1 sec
Thanks for looking into it, appreciate any help you can provide
I'm working with my tech on-site to get as much information as we can, I will update you with what he reports
do you have any more info about the crash? steps to reproduce, error messages, serial numbers of impacted devices, anything like that?
sounds like you're still working on steps to reproduce
but i might be able to get some useful info if we just have serial numbers along with timestamps for when the crash occurred
STR70Z1C509003145
This was the first reported device to have an issue, they tried rebooting a bunch of times and last I heard that device was working but trying to figure out exactly which ones are currently not working
I believe it is currently offline because my tech is taking it to another location where he can plug it into a computer and get more details. Same with STR70Z1C509003041
hmmm. i am seeing a lot of errors reported for that device that look like they might be related to networking problems. i see a huge spike around 17:23:00 UTC. it's possible the software update is related, but would it be possible to try running one of the impacted devices off of a mobile hotspot as a short term troubleshooting solution?
We will try that out and let you know
you said this is for an event, is this at a single site? is it a new network you're connecting the devices to? or is it across multiple sites, and if so are you seeing issues across all of those sites?
Hi π
I'm stepping in as my colleage had to go
We have a two-weekend event that went great last weekend and opens tomorrow for this weekend. They are preparing for this weekend and seeing the devices get stuck into a boot-loop
The errors we are seeing for these readers do primarily indicate the issue is with network connections
When you say a boot-loop, do you have insight into what that means exactly? What screen is loaded?
Checking
The error logs for STR70Z1C509003145 is showing that it cannot connect to one of the domains we use for device management.
It's a basic HTTP request timeout error and we see these all the time for terminal readers where there is something wrong with the network.
Either the local WiFi network has some firewalls or config that prevents access or the connection from the local WiFi network to the wider internet might be at issue.
The quickest way to test this out is to switch one reader to a mobile hotspot
If it "suddenly works", that means it's the network
The device is stuck on this screen. If it is manually rebooted it launches the app and then sometimes rebooted again. We did a lot of testing all this week and had thousands of transactions last week and did not encounter this until after the 2.40.1.0 update. The picture/video attached are on our office wifi, not the event site wifi
Okay so that's clearly an Android application crash. Do you have logs of the error being thrown?
We donβt know how to pull device logs off a non-dev device, trying to reproduce on a dev device currently
We do see some errors in our server for the API endpoint that handles the connection token request. It's saying device id not found. Did something change in this update regarding the API call the device makes to our server when it asks for a connection token?
Are the errors coming from the Stripe API request? If so, can you share the request ID? It will start with req_
Here's how you can find a request ID: https://support.stripe.com/questions/finding-the-id-for-an-api-request
Checking
We figured it out, it was a misconfiguration done by one of our clients on this event. Sorry for the hassle. This issue has been resolved