Closed thelight413 closed 3 months ago
@thelight413 the logs above are a warning from the SDK's failed attempt to fetch cached locations; it does not fail the discovery operation. The log immediately afterwards onUpdateDiscoveredReaders
confirms the sdk returns an empty list of readers to your application. Please see details ^1 for using your M2 reader, and let us know if you're having issues with discovery.
I got it to discover the reader but it stays on the status "connecting" for a while and then just disconnects. The error I get is "timed out waiting for connection token".
Just to add just in case this helps. It seems like connection token is being refreshed twice. once during initialization and once during forwarding offline payments. Its refreshing one after the other.
Terminal
requires a connection token ^1 to activate your session so the reader can take payments, it seems your application is not providing a ConnectionToken
hence the error. I'd suggest trying the example application ^2 if you haven't already to resolve integration errors in your application. Closing this out since it is an integration issue, feel free to open a new issue if you find bugs with the library.
I'm still having this issue. When you run the app for the first time, do an initialization, discover readers and trying to connecting to a reader it will not connect to the reader because it doesn't attempt at getting the connection token. I put logs before and after it gets a connection token and it doesn't try getting the connection token on a fresh install. But if I swipe out of the app and run the app again it does get the connection
Can you reproduce with example application ^1?
Summary
I'm getting an error when trying to discover readers whether it's NFC or an M2 reader. The error I'm getting is
Code to reproduce
Android version
Android 14
Impacted devices (Android devices or readers)
Pixel 6, M2 reader or NFC reader
SDK version
3.7.1
Other information