You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I was wondering if someone could offer me a bit of insight into the following problem. We have around 150 android devices running kiosk mode + a custom app.The app relies on this SDK to handle payments via sumup. Each device is restarted daily around 22:00. We login to sumup with username and password. We also
have a custom key.
Most of the time the payments are running just fine, but from time to time we receive information from SDK that the token has expired and we need to log-in. This appears to be at random times, random devices. Not all devices are impacted.
I'd like to implement some recovery mechanism but that may require re-login which in turn may require entering username and password again which is not ideal.
Is that a known problem? Does the session between SDK and the sumup servers have a TTL? How come some devices are not impacted.
Don't have much in terms of logs but I'll try to gather more. Sorry, can't reproduce this problem on demand. Sample message from the SDK:
Unsuccessful payment. payload={txCode=null, message=Access token invalid, resultCode=2, foreignTransactionId=null}
Unsuccessful payment. payload={txCode=null, message=Log in first before proceeding, resultCode=8, foreignTransactionId=null
My only theory is that upon a successful login a device obtains an access token that is being refreshed periodically in the background. Perhaps due to the
poor network connection this procedure fails and the token expires. The message from SDK says the token is invalid, not that it has expired though.
Setup:
Android 10
Sumup SDK 7.1.0 (but seen this also on 6.x versions)
Activity