#damo-red61_api

1 messages · Page 1 of 1 (latest)

gaunt whaleBOT
#

👋 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/1272586415590346812

📝 Have more to share? Add more details, code, screenshots, videos, etc. below.

knotty spire
opaque pewter
#

oh, I didn't notice that that section had been added, previously the requirements were just for android 11+ and various bluetooth/nfc functionality.

Okay, can confirm that the device we're currently using for development is not listed under the supported devices section. So that would probably go some way to explaining the behavioural anomalies.

as far as the intermittent connection behaviour, we were able to get the device to register+connect if app + terminal initialisation + discovery process was restarted a "few" times (was not consistent).

knotty spire
#

Also what version of the SDK are you using?

opaque pewter
#

latest version I believe , version 3.8.0

knotty spire
#

Okay. And sorry that last sentence is tough for me to parse (I'm jumping between active threads). Are you saying the reader is not found if you do restart the process or it's only found if you restart the process?'

opaque pewter
#

no worries,

it's only found if I restart the process (but not always) seems like some kind of race condition, (which would make sense if it's the Terminal.initTerminal() that's meant to register the device against the location)

knotty spire
#

Okay yes that does sound like there might be a race condition occurring.