#awais_api

1 messages ¡ Page 1 of 1 (latest)

lilac sableBOT
#

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

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

spark jolt
#

What framework are you using for this?

sour meteor
#

Kotlin

spark jolt
#

Got it thanks, let me see if I can get a colleague to assist.

sour meteor
#

thanks

short sandal
#

Hey a couple of questions to help diagnose:
1/ Have you tried this without USB to see if the same thing happens using bluetooth?
2/ Are there any SDK errors emitted in the device logs (via logcat) when this crash happens?

This doesn't sound like a stripe error:

Late-enabling -Xcheck:jni 08-25 06:38:13.108 14691 14691 D ProcessState: Binder ioctl to enable oneway spam detection faile

sour meteor
#

@short sandal Please check this

Screenshot_2025-08-22_at_1.23.23_AM.png
#

1/ Have you tried this without a USB to see if the same thing happens using bluetooth? No
2/ Are there any SDK errors emitted in the device logs (via logcat) when this crash happens? The issue is, I am not getting any error. But I get stuck here

short sandal
#

Check what, exactly?

#

Oh, i see you have inline notes at the end.

sour meteor
#

when 1st install the app in tab then it's initializes perfectly...
Even when we kill the app and open the app again then it will also works perfect.

But issue occurs when we keep the Tab and App on for straight 34 to 48 hours.. then 1st it disconnects with reader (m2 via USB) and didn't reconnect automatically.. and by restarting the app the app freezes on the SDK initialization. Then only restart of device works.
@short sandal Please read it once

lilac sableBOT
short sandal
#

What gives you the impression that error is coming from Stripe? That binder ioctl error seems to be a generic platform error from some initial research

#

device is the reader or device is the app host?

lilac sableBOT
short sandal
#
  • Have you tried force stopping your app then restarting it?
  • Can you share a snippet of code from your discovery & connect section?
sour meteor
#

Have you tried force stopping your app then restarting it?Yes
Can you share a snippet of code from your discovery & connect section? sure

short sandal
#

I'm hypothesizing that the issue might be failure to discover the reader (or any reader) and that your app might fall into a discovery loop

#

That platform "one way spam" check (Android platform, not Stripe's) sounds like its about apps "spamming" interfaces

sour meteor
#

// ReaderConnectivityFragment.kt:42
scope.launch {
EventBus.publish(AppEvent.EventStartDiscoverStripe(true))
}

// ExtensionFuns.kt:458+ - Reader discovery process
Terminal.getInstance().discoverReaders(
config = DiscoveryConfiguration.UsbDiscoveryConfiguration(
0,
Constants.IS_SIMULATED
),
// ... discovery listener implementation
)

sour meteor
short sandal
#

Can you add some debugging details where you call discoverReaders() to see if that's being called multiple times?
We also note in the docs:

When discovering readers using this method, DiscoveryListener.onUpdateDiscoveredReaders will be called every time a compatible device is plugged in or unplugged.

So you could additionally try unplugging and replugging the device

sour meteor