#twafiq_error
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/1385041562538610720
๐ Have more to share? Add more details, code, screenshots, videos, etc. below.
Hi ๐
Hey
And you are saying that this is not resettting the 24 hour reboot timer?
no i am saying that my app does not handle this 24 hour reboot properly
Sorry I'm not getting what it is you are trying to do here
so I want to find a way to simulate/reproduce this issue as opposed to waiting for the 24 hour security reboot to happen again.
My app breaks when the 24 hour security reboot happens.
Looking for a better way to fix this issue as opposed to implementing a fix and waiting for the 24 hour reboot to happen to see if it works.
I think you would need simulate this yourself by calling the rebootReader method. I'm looking through our docs and SDK but I don't see any method to simulate the 24 hour reboot other than manually triggering a reboot
hmm. When i call the rebootReader() method it works properly
The closest thing we have is simulating a required update: https://docs.stripe.com/terminal/references/testing?terminal-sdk-platform=android#simulated-reader-updates
When you say your app isn't handling this well, does it fail to reconnect?
Yeah
But it works fine whenever i call the disconnectReader and rebootReader methods which is why I am trying to simulate the security_reboot
Yeah, as far as I know there shouldn't be any difference between the security reboot and a manual reboot. I assume you've got logging statements in both Success and Failure callback functions.
There are no callback functions for the security reboot
Since the command seems to be programmed into the OS of the terminal
You should still have your MobileReaderListener class firing onDisconnect so you can attempt reconnection
hmmm ok
I would start by adding logging statements to that callback function to get the disconnection reason
So the failure should theoretically be logged in the onFailure callback in this class.
The MobileReaderListener doesn't implement an onFailure callback as far as I can see
https://stripe.dev/stripe-terminal-android/external/com.stripe.stripeterminal.external.callable/-mobile-reader-listener/index.html