Mobile Payments SDK Reader Connection Issues

Questions
22

The team made some changes and they’re asking if you can logout and reauthorize to pickup the changes. Also what’s the merchant account you have for development so we can continue to look into the issue? :slightly_smiling_face:

23

sure thing. doing it now.
We are using merchant SWAPEQD7SM6FV for our testing

24

also, do you mean to just deauth MobilePaymentsSDK and authorize again or full-on revoke the OAuth token and get a new one?

25

Deauth MobilePaymentsSDK and authorize again. :slightly_smiling_face:

1 Like
26

Done. Hopefully it helped… looking the same here.

["READERSDK: Will attempt to authorize..."]
["READERSDK: deauth starting..."]
["READERSDK: deauth done."]
["READERSDK: calling MobilePaymentsSDK.shared.authorizationManager.authorize(QJ8ZNBEK1Y74Z..."]
["READERSDK: reader Contactless and Chip (7920) added"]
["READERSDK: reader Contactless and Chip (2340) added"]
["READERSDK: authorized! (now wait a moment then reconnect readers)"]
["READERSDK: Authorized location QJ8ZNBEK1Y74Z!"]
["READERSDK: reader Contactless and Chip (2340) invalid because Reader state changed to: connecting"]
["READERSDK: reader Contactless and Chip (7920) invalid because Reader state changed to: connecting"]
["READERSDK: reader Contactless and Chip (2340) invalid because Connection state changed to: connecting"]
["READERSDK: reader Contactless and Chip (7920) invalid because Connection state changed to: connecting"]
["READERSDK: reader Contactless and Chip (2340) invalid because Connection state changed to: connecting"]
["READERSDK: reader Contactless and Chip (7920) invalid because Connection state changed to: connecting"]
["READERSDK: reader Contactless and Chip (2340) invalid because Connection Failed"]
["READERSDK: description = Generic Error - No Suggestion"]
["READERSDK: recoverySuggestion = 0"]
["READERSDK: failureReason = 1"]

We really appreciate the ongoing help!

27

If you have not sorted this yet, a solution that seemed to work for us was implementing the Reader SDK.

Once I had a barebones app running the Reader SDK, I was able to pair the readers fine. Ever since, connecting using the Mobile Payments SDK has been smooth. This has been for all readers and not just ones that had been previously connected using the Reader SDK.