#mja123_code
1 messages ยท Page 1 of 1 (latest)
๐ 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/1290972094858924113
๐ Have more to share? Add more details, code, screenshots, videos, etc. below.
๐
Yes I see, you should be connecting/disconnecting readers for each payment attempts..
is there any way to make it connect faster? Sometimes it takes 30+ seconds to initiate the payment
No honestly...
What you can do maybe is to stroe the reader Id in the local storage
like that you skip the discover phase
and don't do it each time after disconnect
will storing the id work? since it requires the Reader object instead of an id
Hi! I'm taking over from my colleague. Please, give me a moment to catch up.
sure
What does "it" refer to here exactly ? you can store all the reader object too if needed in your integration...
But I think you got the idea: avoid calling discover again after disconnecting..
i meant the connectLocalMobileReader function from the SDK.
so i tried using this method by storing the Reader object into the local Store, but if it try to connect to a mobileReader using the stored Reader after connecting to a terminal reader, i get {"code": "InvalidRequiredParameter", "message": "Could not find reader with id APPLEBUILTINSIMULATOR-1"}
i think the sdk is not able to find the mobile reader because i called discoverReaders and connected to a terminal reader beforehand
Yeah, does this work with the standalone reader? Maybe this doesn't support tap-to-pay
based on my testing this method only works when you connect to the same reader as you connected previously, but it doesnt work while switching from terminal -> tap to pay or tap to pay -> terminal reader
i think its because of calling the discoverReaders fn for each device type, it removes the other types devices from cache. Hence it fails to recognise the tap to pay reader when calling connect without discoverReaders
I see. This is unfortunate. I don't think there's another workaround, sadly.