#damo-red61_ttpa-discover-readers
blazing tapirBOT
👋 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/1272936182824833107
📝 Have more to share? Add more details, code, screenshots, videos, etc. below.
nova waspBOT
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.
- damo-red61_api, 21 hours ago, 10 messages
pearl steppe
Hi 👋 apologies for the delay, the server is pretty busy at the moment. I'm not familiar with the call to that endpoint, it's not something I've seen discussed before. Let me review the flow for connecting to the TTP readers.
tight turret
no worries
pearl steppe
You mentioned this happens when calling discoverReaders, correct? Is the onFailure callback being hit?
tight turret
no, what we're seeing is that there just doesn't seem to be any "readers" at all in the discover readers code, so not hitting onSuccess() nor onFailure
i.e. for the following code, we never see the "starting reader loop" message :
discoveryCancelable = Terminal.getInstance().discoverReaders(
config,
readers -> { displayCallback.showMessage("Starting reader loop");
which I guess for non-anonymised code, would be that it's the
DiscoveryListener.onUpdateDiscoveredReaders()
function that doesn't seem to be getting called
torn shoal
Hello! I'm taking over and catching up...
What does your DiscoveryConfiguration look like?
tight turret
hello, currently it's just :
DiscoveryConfiguration config = new DiscoveryConfiguration.LocalMobileDiscoveryConfiguration(false);
we have managed to get it to trigger the attestation phase previously, for the same device, with the same code :
request id for prevous attestation/bind : req_3jknLxKYLWhnPa
but havent managed to trigger it again since
torn shoal
Hm. What version of the SDK are you using?