#radu-m_api

1 messages ¡ Page 1 of 1 (latest)

peak forgeBOT
#

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

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

sharp robin
#

hey there, looking into your question now

regal coral
#

Hello

#

thanks, I'll be here to provide more details, as required.

sharp robin
#

thanks. can you share some timestamps from when this reader didn't go online as expected (i.e. when you reset/restarted the reader)?

on our side it looks like tmr_GXgqagMBEMj50U has been online since this morning

#

when you say that the device no longer goes online, do you mean it doesn't connect to your local network, or it doesn't connect to the SDK/POS device?

regal coral
#

Well, the Input field on the #help is too small to explain it thoroughly.

#

The steps are as follows:

  • device offline
  • take a transaction offline - need to insert card
  • bring device online (connect to Wi-Fi)
  • take a transaction while online - need to insert card

The Terminal SDK doesn't go online, even if the offline payment intents get forwarded. Any subsequent transactions, taken with the device connected to Wi-Fi, go through the offline path (user has to insert the card).

This happened ~ 06:58 UTC today. Even now, the device is online, but if I try to put through a transaction, I need to insert the card. The card is not read contactlessly.

raven geyser
#

Hey! Taking over for my colleague. Let me catch up.

#

This happened ~ 06:58 UTC today. Even now, the device is online, but if I try to put through a transaction, I need to insert the card. The card is not read contactlessly.
Is this your account Id "acct_1Oh9T1H029wHUS4e" that faced this issue today ?

regal coral
#

yes, that's the platform account ID

raven geyser
#

Thx.

#

Not seeing any error relating to the offline payments..

#

I see that you've migrated your reader's version to the latest version but you are still using an old sdk

regal coral
#

Well, the reader version is outside of our control , that's controlled by Stripe.
But yes, we're using Stripe Terminal v4.7.3 on our Android devices.

We already migrated to v5.2 on a separate branch, but that hasn't been released yet.
I was working on a hotfix on our Production devices, who run v2.40.1.0 reader firmware, with Stripe Terminal SDK v4.7.3.

#

Well, there aren't any errors that I could see, it's just the SDK doesn't go online and always asks for the user to insert the card instead of taking the transaction contactlessly

raven geyser
#

As youare using an Android integration, there is a coupled link between the terminal version and the SDK you are using.

#

We usually recommend the server driven integration to bypass the connectivity issue.

#

Well, there aren't any errors that I could see, it's just the SDK doesn't go online and always asks for the user to insert the card instead of taking the transaction contactlessly
Yeah I understand. You said that you have a branch using SDK 5.2, are you seeing the same issue or not ?

regal coral
#

Now I see the device SDK went online, rougly 2h after actually connecting the device to Wi-Fi

raven geyser
regal coral
#

with 4

raven geyser
#

Can you please try doing the test with 5.2 ?

regal coral
#

It'll take some time for me to test, can I come back on this chat in about 30 minutes?

raven geyser
#

Also can you try to force the connection to the reader when you are sure that the reader is back online via your android app by re-calling this :

Terminal.getInstance().connectReader(
    reader,
    config,
    object : ReaderCallback {
        override fun onSuccess(reader: Reader) {
            // Placeholder for handling successful operation
        }

        override fun onFailure(e: TerminalException) {
            // Placeholder for handling exception
        }
    }
)
regal coral
#

As far as I recall, you need to disconnect the reader first, then run discovery and then connect reader.

raven geyser
#

Your reader got disconnected here and then it went online, right ?

regal coral
#

No, the reader doesn't get disconnected. It stays offline.

#

We just tested on a Production device, running v2.40.1.0, and the SDK comes online immediately after the device comes online (connected to Wi-Fi).
So to me, this looks like a regression in v2.41.2.0

raven geyser
#

No, the reader doesn't get disconnected. It stays offline.
Ah sorry I got confused then (you said your run off/on the wifi)

raven geyser
#

That's why I have a doubt about the mobile app's stripe SDK version, which is old.

regal coral
#

the mobile app SDK.

#

when you say the "reader SDK", I assume you refer to the "Reader version" in the device diagnostics:

2026-04-21_13.29.52.jpg
raven geyser
regal coral
#

OK, I am now building the app with the upgrade to Stripe Terminal SDK v5.3.0. Will let you know in about 5 minutes whether this issue is still reproducible.