#awais_api
patent parcelBOT
👋 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/1409950415771926548
📝 Have more to share? Add more details, code, screenshots, videos, etc. below.
Below are links to other discussions we've had with you in the past week in case you want to review that information. If your question is related to one of these previous discussions, please provide a comprehensive summary of the current state and what you need help with now. We help many users simultaneously, so a summary allows us to resolve your issue as soon as possible.
- awais_api, 21 hours ago, 25 messages
tame sand
hello! it looks like this is the same issue you were writing about yesterday correct?
did you try the debugging steps suggested most recently in the other thread?
#1409598515818004564 message
fierce goblet
@tame sand sorry about this, but my last thread was closed due to inactivity on Discord
@tame sand YES I DID
tame sand
no worries! it's always ok to come back and ask for help again 🙂
were you able to discover anything around discoverReaders() potentially being called more than once?
fierce goblet
no, I need to restart my device, then it works
tame sand
that's not quite what i'm asking, i'm wondering if you were able to add logging to your app to see if it's calling discoverReaders() more than once (and if so, is it calling it more than once)
also in the other thread you said this:
The main issue is, I have the same model devices, and getting issues on some devices
does this mean that you're only seeing this problem on some devices you test on but not all?
fierce goblet
does this mean that you're only seeing this problem on some devices you test on but not all?
yes but I got stuck on other devices as well after almost 72 hours
tame sand
ok, so on some devices it freezes after ~34-48 hours, and others ~72? are there any where it doesn't freeze at all?
fierce goblet
Yes, but it freezes
tame sand
i don't quite understand what you mean - it sounds like it freezes eventually on every device you have right?
tame sand
that's not quite what i'm asking, i'm wondering if you were able to add logging ...
ok, i want to revisit this:
- have you added logging around where your app is calling
discoverReaders()? - have you been able to determine if your app is calling it multiple times?
especially around the time that it's freezing
fierce goblet
tame sand
what exactly am i looking at here? this doesn't quite answer my question, is this the logs you're getting around the time it freezes?
fierce goblet
is this the logs you're getting around the time it freezes..yes
https://github.com/stripe/stripe-terminal-android/issues/618
@tame sand please look at this too
tame sand
is this your issue? or are you just also experiencing the same issue
fierce goblet
This is my issue
fierce goblet
ok, i want to revisit this:
1. have you added logging around where your app is c...
yes we have added logging around discoverReader()
it not calling multiple times!
app uninstalling and installing not fixing this issue.. only reboot of device works
fierce goblet
ok
patent parcelBOT
eager sorrel
I don't think this is the kind of thing that we're going to be able to solve for you here on Discord. We juggle threads and attempt to help many users at once. This is going to require a deeper investigation, so it will need to be a support case . I see you already have a Github issue open which is good. They might be able to help you there, but really I recommend you write in. You should be getting a dm to open a case.
patent parcelBOT
Hello @fierce goblet, we have sent you a direct message, please check it at https://discord.com/channels/@me/1409976987757576383
- 🔗The message has instructions on how to open a direct support case with our Developer Support team, in order to help you more effectively.
eager sorrel
The link you should have gotten dm'd will open a support case directly with our developer support team
So you don't have to waste time chatting in the chat bot like above
fierce goblet
ok