#yogen_error
1 messages ยท Page 1 of 1 (latest)
๐ 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/1491802184118177853
๐ Have more to share? Add more details, code, screenshots, videos, etc. below.
I think my initial message truncated the full log. Here it is:
Hello
You'd likely want to look at the logs prior to AIDL RPC Error line to understand what's going on
also 3.x.x is a very old Terminal SDK
Can you try a newer one instead? https://github.com/stripe/stripe-terminal-android/releases
These are the logs prior:
D class=ConnectionTokenRepository message=fetchConnectionToken.onSuccess
I class=HandoffReaderController message=discoverReaders location=null
D class=HandoffRpcClient message=bindToService aidlServer=com.stripe.core.aidlrpc.AidlServers$Reader@b2bc741
D class=AidlRpcClient message=bindToService action=com.stripe.stripeterminal.handoffclient.RPC_REQUEST packageName=com.stripe.reader className=com.stripe.reader.services.AidlServerService
D class=AidlRpcClient message="Context::bindService completed" success=false
And before these it's just fecthing the connection token from our backend successfully.
Agreed we're a bit far behind on the sdk version and we will be updating to the latest version beginning May
Can you share the reader serial number?
Also, a complete logcat would be useful to look at
Agreed we're a bit far behind on the sdk version and we will be updating to the latest version beginning May
Can you try to use a newer version in an example/simple project and see if the issue fixes itself?
Generally we only support the older SDK version for limited time after a new major version is released and if it's an issue with older dependencies then the only fix would be to upgrade the SDK
Serial number: 713-348-635
And the full log.
We've updated to 4.x for our mobile app integrations and business terminal is next. We haven't able to update to 5.x as it meant a good chunk of our users who already use Tap to Pay wouldn't be able to use it anymore.