#Poutine-Terminal-Android

1 messages ยท Page 1 of 1 (latest)

grizzled swallow
#

Hello! give me a sec to catch up

sonic talon
#

Sure!

grizzled swallow
#

just pasting the question here for my own info:

StripeTerminal: class=Terminal message="targetSdkVersion should be <= 30 to use Terminal" target_sdk_version=31

However I believe Android requires packages to be pointing to target / compile version 31 by November. Just curious if the SDK version support for 31 will be addressed sometime in the near future? Currently investigating an issue we're having with one of our tablets suddenly being unable to pair to a reader via USB and am wondering if this could be the cause.```
#

ok so my Android skills are very rusty but let me read thoroughly

sonic talon
#

I believe in you ๐Ÿ™‚

grizzled swallow
#

asking internally, not seeing anything in the changelog about it

grizzled swallow
#

ok I flagged to them and they said they'll fix it, they didn't realize we were warning in the SDK on that

sonic talon
#

Ah okay, good to know ๐Ÿ™‚

#

So presumably that shouldn't have any effect on USB suddenly no longer connecting correct? (I can make a separate thread about that)

grizzled swallow
#

it should not no, but we can take the second question in this thread too

sonic talon
#

Ah okay -- one sec then, will post the question (I contacted support@stripe but their reply was all about Bluetooth which we're trying to get off of :S)

#

"Looking to get some help debugging an issue we're having with one of our providers.
Historically, their tablet was accepting payments on a BBPOS reader connected via USB without issue. About 2 days ago, suddenly they received a USB_UNEXPECTED_DISCONNECT during a payment.

Since then, they have not been able to reconnect to any reader / using multiple cables via USB. Interestingly, the reader charges without issue, and the reader can still connect to the tablet via Bluetooth, which makes us think that there isn't an issue with the reader or the cable being used.

I was able to pull out system logs from the device, but haven't found anything conclusively suggesting an issue with USB permissions or USB functionality on the device.

Attached below is the full logs pulled from the device, and an excerpt of the logs surrounding a USB connection attempt. I can also pull some session logs if think that'd be helpful (specifically pertaining to the original USB unexpected disconnection).

Could use some help trying to understand why the device would suddenly be unable to connect via USB. Let me know if any further information is needed!"

#

I also have some logs that I can provide from the device itself

#

(The session logs would be from another tool and not nearly as verbatim as the logs, hence leaving it out for time being)

#

2 days ago => August 17