#ebad_docs

1 messages ¡ Page 1 of 1 (latest)

unborn epochBOT
#

👋 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/1463642439209455801

📝 Have more to share? Add more details, code, screenshots, videos, etc. below.

Below are links to other discussions we've had with you in the past week in case you want to review that information. If your question is related to one of these previous discussions, please provide a comprehensive summary of the current state and what you need help with now. We help many users simultaneously, so a summary allows us to resolve your issue as soon as possible.

shell trellis
#

Hello, looking in to this. What Stripe code specifically throws that error?

#

Also is this on our Android or iOS SDK? I notice they are both on 5.1.1 at the moment

#

Ah that looks to be an Android error

dim trellis
#

this is android tablet (kiosk)

shell trellis
#

I found a GitHub issue about this. Version 5.0.0 has higher hardware requirements, specifically the device's ECDH (FEATURE_HARDWARE_KEYSTORE version must be 100 or later.

#

They provide this code to run to confirm if this is the issue on your device:

    context.packageManager.hasSystemFeature(PackageManager.FEATURE_HARDWARE_KEYSTORE, 100)
} else {
    false
}```
dim trellis
#

basically we have built an application which was using a version 4.6.0 and we ran that code on same device and it is working fine do we need to add hasHardwareKeystore check on 5.1.1?

shell trellis
#

Our SDK does that check automatically, basically this issue may be getting thrown because when we do that check your device's hardware keystore version is <100

dim trellis
#

ok so if this check is false then device is not supported? and what exactly do we need to do work on latest version? or should i downgrade the version?

#

please answer asap

shell trellis
#

Correct, if it doesn't have the hardware it isn't supported on the newer SDK versions. So in that case a downgrade would be the best option to keep using those specific devices.

#

I'm double checking if there are workarounds, but as best I can tell there isn't a way to upgrade this hardware on an Android device

unborn epochBOT
dim trellis
#

please check and do let me know if there is any way on 5.1.1 version we can handle NFC payments successfully

shell trellis
#

Unfortunately as best as I can see there isn't a way to upgrade the hardware on the existing device and I'm not finding any workarounds. So your devices will still be usable on the older SDK versions but you'll need newer devices to do tap to pay on devices after 5.0.0

dim trellis
drifting night
#

Hi there, I'll be taking over for Pompey. I believe they've provided you with the best advice we have for the scenario here, but please let me know if you have further questions

dim trellis