#NewtReyes

1 messages ยท Page 1 of 1 (latest)

cinder aspenBOT
next saddle
#

When looking for the error on the internet, this is what I came up with:

#

This is the error from the stack trace:

chrome tree
#

And this is the initialization code in which file? There's a lot going on in this quickstart ๐Ÿ˜…

next saddle
#

LOL

#

I agree

#

That's the step where I am seeing the issue

chrome tree
#

I'm looking at the error message and thinking this is coming from one of the callbacks being used there

next saddle
#

Here's the full stack trace:

#

From what I can see, the last thing that happens on our custom code is this:

chrome tree
#

can you log that terminalToken?

next saddle
#

Yes

#

Give me a sec

chrome tree
#

I'm also firing up a JS integration to log some connection tokens. It's the same APIs on our end

next saddle
#

D/TEST: Terminal Token: pst_test_YWNjdF8xSzJjc1pJSndreG5WbU5WLG84blhoNEg3RUhCZ0pPSTNGY3ZWWUMzVUlVb0hjR1I_00lQDmhA1O

chrome tree
#

Okay that's looking good so we can rule that out

next saddle
#

Is it expected for the Terminal to try to read the device id?

chrome tree
#

Yes I believe so. We see specific device IDs in the log lines sent back to us

next saddle
#

Right

#

Makes sense

#

But now access to those seem to be restricted

#

Apps signed with the platform key or privileged system apps

chrome tree
#

Oh wait, you mean the ID of the Android device?

next saddle
#

Seems like it

#

That's what the stack trace reports

chrome tree
#

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

next saddle
#

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

chrome tree
#

I'm trying to get the quickstart code to run.

next saddle
#

Thank you!!!

#

Also, please take into consideration that this is not happening when using an emulator

chrome tree
#

๐Ÿค”

next saddle
#

but it is happening when trying to run it from my phone (Android 13)

chrome tree
#

Hmmm... I've got an Android 13 device I can test on. This may take a little bit

next saddle
#

I suppose

#

Thank you for walking the extra mile with me!!!

chrome tree
#

That's why we're here ๐Ÿ™‚

#

Does this error actually prevent you from building your app?

next saddle
#

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?

chrome tree
#

That's my read of the response on the GH Issue

next saddle
#

Yeah

#

I will keep testing on my side

chrome tree
#

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

next saddle
#

Awesome

chrome tree
#

That was a long way around the barn

next saddle
#

then it's something else

#

LOL

#

thank you so much, Snufkin

#

I will keep banging my head on this rock until I break it

#

thank you!!!

#

and Merry Christmas!!!