#mja123_code

1 messages · Page 1 of 1 (latest)

livid oakBOT
#

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

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

supple ore
#

Hello

#

When you say "not connecting" what does that mean exactly?

#

You get an error?

spark forge
#

no error. it only displays the loading ui

#

which is supposed to be gone after tap to pay reader connects

#

it does work in intended way when the xcode debugger is attached

supple ore
#

Have you added logs to see if the connectLocalMobileReader() promise resolves?

spark forge
#

yes, it does gets resolve when i am checking with the xcode debugger or running the app in debug mode

#

but that doesn't seem to be the case w/o the debugger

supple ore
#

Hmm okay give me a second to see if I can find anything

spark forge
#

sure

#

thanks

supple ore
#

Do you have the reader ID that you are testing with?

spark forge
#

sorry i do not have that

#

let me see if i can log it

#

**keeping the chat alive

#

b972f9b219ac433272dbd73c1589d22fca6ee5cb0d19345e0eaeb9295ef675e6

#

serial

#

tml_FrwxOAWAW1XD0s location

supple ore
#

Thanks, let me see if I can see anything in our logs

spark forge
#

sure

supple ore
#

Can you perform a fresh test right now actually so I don't get conflicting logs from your earlier tests that were working?

spark forge
#

sure

#

doing the test right now

supple ore
#

👍

spark forge
#

did the test

supple ore
#

Thanks, looking

#

Hmm I'm seeing duplicate requests coming through

#

Where it is showing an exception: INTEGRATION_ERROR.AlreadyConnectedToReader

#

So I see 3 connection attempts... looks like the first one was successful and then there are 2 more that have that exception

#

Any chance you are having some re-renders trigger or something that might be doing this?

spark forge
#

yes could be

supple ore
#

I think that is where I would recommend starting in terms of a debug. See if you can ensure that you are only calling connectLocalMobileReader() a single time

#

Also do you have unexpected disconnect handling in your code?

#

Wondering if that would fire at all from an issue like this

spark forge
#

since i am handling the exceptions, thats shouldn't be an issue though

#

yes disconnect handling is implemented

#

onDidReportUnexpectedReaderDisconnect(error?: StripeError) {
if (error) {
Sentry.captureException(error);
}
showError({
header: 'Reader Disconnected',
message: 'Reader disconnected unexpectedly, Attempting to reconnect...',
});
},

supple ore
#

Yeah only thing I see on my side is these duplicates which are leading to an integration error. They are within milliseconds of each other so maybe that is leading to a race condition which is breaking the promise from actually resolving?

#

Not sure.

#

If you want us to look into this further then you'd want to write into our Support team via https://support.stripe.com/contact/login and include a screen recording of what is happening, your code, and the info about the device you are testing with.

#

Then we can take a deeper look. But not much more I can do to troubleshoot from here right now.