#badshah420_code
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/1409440974094077953
đ Have more to share? Add more details, code, screenshots, videos, etc. below.
Following screen shot shows the device details in which we are using our koisk app:
So you are developing an Android app, and connect to the reader (not the AppOnDevices), correct?
But issue occurs when we keep the Tab and App on for straight 34 to 48 hours.. then 1st it disconnects with reader (m2 via USB) and didn't reconnect automatically.. and by restarting the app the app freezes on the SDK initialization. Then only restart of device works.
Do you mean restarting the Android phone, or restarting M2?
Restarting the Android Tab! there is no concern with reader yet.. problem with the SDK initialization.
this is the version I am using currently:
implementation("com.stripe:stripeterminal:4.5.1")
yes! the above screen shot is the specifications of that tablet.
I see this is "Rooted". Highly likely there will be unexpected behavior in that case. Can you try a different device?
For your reference I want to mention that:
in the following screen shot when issue happens and we try to restart the App only not the device.. then only log 1 prints but log 2 never prints..
Exactly.. I also have the same concern! I also asked the same to my client.. but he said all these types of kiosk tablets manufactured and comes rooted by default..
unfortunately, we didn't tested it on any other devices for that long time!
@simple pumice are you suggesting to do first testing on the non-rooted device? if yes? then what will be the solution for our devices?
I am not sure TBH. But it's a good idea to rule out and testing in a normal device. Any Android phone for example
"//Log 1" and "//Log 2" is just comment. Where are they printed out?
I have just write it now just only to give an idea
Hey! Taking over for my colleague. Let me catch up.
yeah hi..
When the Terminal.init freeze, what are the logs you are seeing ? Is it possible to display the verbose logs and share it with us when tha thappens again ?
val logLevel = LogLevel.VERBOSE
it's might be lot difficult to do that.. because device is not with me I can also access it by the AirDroid(remote control app)
but for your info.. I want to tell you that..
when this error occurs.. even the uninstalling and installing the app also didn't work.. Only Android Device needs to be restart works.
This seems to be something related to the device then...
The only way to know what's happening and what's blocking the SDK from initializing is collecting the verbose logs
yes! but client wants a solution for this.. I have also suggested to change and upgrade the hardware but that also not possible for him for 3 years atleast
is there any way I can get the all logs and store it somehow remotely?
As I am able to send my custom logs to the firebase
I think you can do something with Firebase
how can I send Stripe logs to firebase? means I can I first get programatically?
I think these logs are handled by your sdk itseld
Checking this...
https://firebase.google.com/docs/analytics/debugview#android
Yeah you need to find a way to send all your app logs to Firebase or something else
Okay! allow me some time to do that.. Once I got the logs! then I will ping you back.
Between, when you say the terminal is stuck, aren't there any execption thrown ?
Please see this screeshot.. when this trminal stuck happens then the code always runs the try block it won't goes to the catch block.. plus I have implemented the log to firebase if any type of exception occurs:
I have also set some logs in the token provider function.. and found that the api calls perfectlly and it got the secret too!
Try to catch RuntimeException too
? how it will catch the runtime exception? when code is enterin in the try block?
I'm saying this just in case there is another execption missed and the device isn't crashing the app
Okay! sure..
Honestly, the straight forward path here, is to collect all verbose logs or try and reproduce it on tnhe device....
They can try upgrade their device, or at least reboot it once per day if the customer don't want to do any thing else to their device
I have two device currently on this error state.. and I am working on to get the whole logs.
yup I have also suggested the same:
"They can try upgrade their device, or at least reboot it once per day if the customer don't want to do any thing else to their device"
I am working on it.. allow me 30-40 minutes aprox.
to get the whole logs.