#lletfrix
vestal rampart
Hello! ES is in beta for tap to pay on Android. Are you in the beta?
proud lichen
I thought it was an open beta. How can I access it? Through the dashboard?
vestal rampart
I believe you would need to write in to support to request access to the beta: https://support.stripe.com/contact/email
proud lichen
Great, I'll do it right away. However, is there any way to check? Also, how is the app suppose to know that, through the locationId?
vestal rampart
I think it uses the location data for the reader and the location reported by the SDK.
Check what?
proud lichen
If my account is in beta as I don't know if a co-worker already asked for it. I'll find out. Thanks!!
vestal rampart
What specific step is throwing that error?
proud lichen
connecting to the reader
vestal rampart
This is flagged as a public beta internally, so it seems like it should be working. What version of the Terminal SDK are you using?
proud lichen
Let me check, actually the one that the stripe-terminal-react-native uses
vestal rampart
Oh, that's likely why. I don't think we support tap to pay in React Native at all, but let me confirm...
Yeah, we don't support React Native at all right now.
proud lichen
Well yes I think I found it
The changelog of that version says:
This release adds support for Tap to Pay on iOS and Android. Tap to Pay iOS is available in the US. Tap to Pay Android is supported in the Australia, Canada, France, Germany, Ireland, New Zealand, Singapore, the UK and the US.
And also Upgrade Android and iOS SDK to 2.17.1
So I think that's it. Like the simulated version worked but I guess I need the SDK 2.20.0 for it to work with the beta locations
vestal rampart
Well, to be clear, if you're using React Native it simply won't work at all.
proud lichen
Interesting, like that is not documented anywhere right? The text of my last message was on the changelog of the stripe RN library :/
errant stratusBOT
vestal rampart
The internal docs I'm reading say it's not supported, and if it was supported I would expect there to be a React Native tab on this page: https://stripe.com/docs/terminal/payments/setup-reader/tap-to-pay
There simply isn't a React Native option for tap to pay.
proud lichen
I get that, but the docs pages are not up-to-date indeed.
The code here won't work
https://stripe.com/docs/terminal/payments/connect-reader?terminal-sdk-platform=react-native&reader-type=simulated
vestal rampart
That's for a simulated reader, not a tap to pay reader.
proud lichen
Yes but it's not up-to-date, I expect that the docs are not ready yet.
vestal rampart
What do you mean it's not up to date?
proud lichen
Those pages refers to an old version of the RN integration
e.g the piece of code on the first snippet
didUpdateDiscoveredReaders: (readers) => {
// After the SDK discovers a reader, your app can connect to it.
// Here, we're automatically connecting to the first discovered reader.
handleConnectBluetoothReader(readers[0].id);
},
});```
Does not work, as the argument is `onUpdateDiscoveredReaders` instead of `didUpdateDiscoveredReaders`Ah, gotcha. I can flag that internally for an update.
proud lichen
I get that, but the docs pages are not up-to-date indeed.
The code here won't w...
Following the library specification, there's a connectLocalMobileReader on the return of useStripe() that connects to a tap 2 pay reader
proud lichen
Ah, gotcha. I can flag that internally for an update.
Great
proud lichen
Following the library specification, there's a `connectLocalMobileReader` on the...
And this works when discovering with method 'localMobile' and simulated:true
But throws the country error when is not being simulated. So that's why I guess RN is working, although not in the beta regions
vestal rampart
Yeah, I think that's just an oversight. Some of the APIs are there in anticipation of this working in the future, but it won't actually work until we officially support React Native for tap to pay.
proud lichen
Oh that makes sense. Then it's nothing I can do I guess apart from ejecting and implementing it natively.