#NewtReyes
1 messages ยท Page 1 of 1 (latest)
When looking for the error on the internet, this is what I came up with:
This is the error from the stack trace:
And this is the initialization code in which file? There's a lot going on in this quickstart ๐
I'm looking at the error message and thinking this is coming from one of the callbacks being used there
Here's the full stack trace:
From what I can see, the last thing that happens on our custom code is this:
can you log that terminalToken?
I'm also firing up a JS integration to log some connection tokens. It's the same APIs on our end
D/TEST: Terminal Token: pst_test_YWNjdF8xSzJjc1pJSndreG5WbU5WLG84blhoNEg3RUhCZ0pPSTNGY3ZWWUMzVUlVb0hjR1I_00lQDmhA1O
Okay that's looking good so we can rule that out
Is it expected for the Terminal to try to read the device id?
Yes I believe so. We see specific device IDs in the log lines sent back to us
Right
Makes sense
But now access to those seem to be restricted
Apps signed with the platform key or privileged system apps
Oh wait, you mean the ID of the Android device?
Interesting. I don't have a test Android integration running currently but I have in the past. I don't recall needing to provide those permissions in the app manifest
Yeah
And even if I placed it in there, it's not like it will allow me still. Seems like those are not easily granted even if requested.
Sigh
I'm trying to get the quickstart code to run.
Thank you!!!
Also, please take into consideration that this is not happening when using an emulator
๐ค
but it is happening when trying to run it from my phone (Android 13)
Hmmm... I've got an Android 13 device I can test on. This may take a little bit
That's why we're here ๐
My esteemed colleague tracked down this Github issue which appears relevant: https://github.com/stripe/stripe-terminal-android/issues/266
Does this error actually prevent you from building your app?
Checking
Well, I can see the error in the logs
and I thought that was the reason why I couldn't discover readers
but maybe that's not the real reason?
That's my read of the response on the GH Issue
Okay so I have been able to get the Quickstart running and I do see the same error. However it doesn't prevent me from discovering my M2 reader
Awesome
That was a long way around the barn