#dev-travis_error

1 messages · Page 1 of 1 (latest)

rare oreBOT
#

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

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

turbid bridge
#

Hello, looking in to this. Do you know if this is thrown by a specific line of code when setting up our SDK or something else?

regal mortar
#

if (discoveredReaders.length > 0) {
const {error} = await connectLocalMobileReader({
reader: discoveredReaders[0],
locationId: location?.[2]?.id,
});
if (error?.message) {
Alert.alert(error.message);
}

turbid bridge
#

Gotcha, and do you know what changed when this error started appearing? Like did you upgrade the SDK between two versions or something similar?

regal mortar
#

We haven't made any code changes recently — everything was working fine. However, all of a sudden, some devices started throwing this error

turbid bridge
#

Gotcha. Do you have the object ID tmr_123 or serial number of any of the devices that you are seeing this error with? I can check if there was a firmware update for them recently

regal mortar
#

After checking GitHub, I found that other developers have reported the exact same error, all stating that it started happening recently and only on some devices.

regal mortar
turbid bridge
#

Can you link to any of those issues? I saw an issue on the terminal RN repo and a related one on the android one

regal mortar
turbid bridge
#

I see chr-stripe said this two weeks ago:

The fix in this case is actually independent of the SDK and can be applied even if you are not on the latest SDK version. If you are able to provide your acct_* token here, I can add you to the feature flag for this fix before it is rolled out fully in order to resolve this issue for you on any affected devices.
Have you passed along your account ID? If not you can write in to https://support.stripe.com/?contact=true and link to that GH issue to ask to be added to the flag for the fix