#NewtReyes
1 messages ยท Page 1 of 1 (latest)
Trying to think of what this might be. Working on simulator but not phone is pretty impressive!
Just as a quick check, the M2 reader isn't connected through the phone's normal Bluetooth menu, right? That can get in the way of the reader being discoverable
Looking in to other general troubleshooting
Just as a quick check, the M2 reader isn't connected through the phone's normal Bluetooth menu, right?
It was initially (should have read the instructions) but I disconnected it some time ago so it is not right now.
I can see it now as part of the available devices in the phone's bluetooth menu but I just confirmed it is not connected.
What I am seeing is that the onUpdateDiscoveredReaders method is never getting called.
These are the logs I am seeing:
Thank you
Hmm not sure exactly what could be going on
Give me a few more mins to see if I can find anything
Thank you, bismarck
Hello ๐
Can you try completely removing the device from your bluetooth preferences (i.e. forget device) or something?
Gotcha. Hmm ๐ค
Does the reader have any LEDs flashing on it?
or are any LEDs just staying on constantly?
They flash when I turn it on
It beeps too
They are not staying on
And this is happening with 2 different M2 devices
Okay! And you have the correct location permissions configured right?
https://stripe.com/docs/terminal/payments/setup-integration?terminal-sdk-platform=android#configure
Can you try re-installing the App so that it asks for permissions again?
Also can you share the discovery configuration code?
ah nice ๐ค