#ceo_code
tender tangleBOT
👋 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/1275795275138728019
📝 Have more to share? Add more details, code, screenshots, videos, etc. below.
solar bearBOT
Below are links to other discussions we've had with you in the past week in case you want to review that information. If your question is related to one of these previous discussions, please provide a comprehensive summary of the current state and what you need help with now. We help many users simultaneously, so a summary allows us to resolve your issue as soon as possible.
shy light
hi there!
distant nova
Hi
we have some problems with stripe implementation. I wish to let me finish to explain all the steps I have done, to understand better the issue
So as first step after yarn add, was to length the token to the stripeProvider
I connected my app to the stripe terminal - StripeTerminalProvider
- I initialised the stripeTerminal in PaymentActionsComponent
- In PaymentWebView I created a new component which handle the search for reader. It looks like that:
- Discover readers with simulated false will return this error
- Discover readers with simulated true will return this dummy object - this is on real device
- But if I tried to connect to in production mode , this will display the same object with no locationId
why, even in production mode this return the locationId/location null ?
for me is the same with that dummy object, I was testing this on a real device , android , samsung A14
that displayed on pink, is the props of a reader object
so what I have done wrong ?
winged cairn
@distant nova would you mind waiting a bit? someone will be with you shortly to help you with your terminal issue
distant nova
FYI : I am a developer in Romania, which is not of the stripe tap to pay available countries - I do not know if it is relevant for you
@winged cairn yep, it is ok, I'll wait
tender tangleBOT
hearty tartan
Hello
Location ID is typically null on discover reader call (I believe it is set when you run connectReader function)
distant nova
ok, I understand the location id is ok to be null , but how I can connectLocalMobileReader to a dicovered reader to do something in the end
?
I am asking this question based on the above six points , where I am tring to explain the issue
hearty tartan
distant nova
- I used the discovers readers function from useStripeTerminal and as you see in the useStripeTerminal callback I used the handleDiscoverAreader to connect that reader to local mobile
- this is the function which help me to connectLocatilMobileReader, as you see is the same step 3 you recommended to me now
hearty tartan
okay? so what exactly does that do? I'm not sure I fully grasp the part you are stuck on really
distant nova
Why the reader have all the props null or undefined? And if the reader is quite empty how I can use it to connect to local mobile reader ?
hearty tartan
You're using simulated reader correct? In that case, this might be expected
It is not a "real" reader
distant nova
in one case I use simulated but I have one case with a real device with simulated false
hearty tartan
The reason you get an error when you set simulated: false is because of this: https://docs.stripe.com/terminal/payments/connect-reader?terminal-sdk-platform=android&reader-type=tap-to-pay#:~:text=For the non-simulated version of the Tap to Pay reader%2C the application isn’t debuggable
For the non-simulated version of the Tap to Pay reader, the application isn’t debuggable.
You can't use debug apps to test Tap to pay
You'd need to create production build and test that instead
You can still use your test mode API keys in production build
distant nova
6. But if I tried to connect to in production mode , this will display the same ...
here is a reader with a production build
that information is from that reader, so is it ok to be so empty ?
hearty tartan
I believe so, what happens when you try and connect to it?
Some fields are only used for Smart Readers like WisePOS E and S700
distant nova
I didn;t use smart readers , I use tap to pay feature from @stripe/stripe-terminal-react-native library
hearty tartan
I know. So what happens when you try to connect to the reader in production mode?
distant nova
nothing, it return that empty reader object
my android device will be the reader but somehow with stripe-terminal-react-native and useStripeTerminal hook , descoverReaders return an empty object in any case
@hearty tartan
hearty tartan
There has to be some error or log that being given when you try to connect to the reader..
It shouldn't fail silently
distant nova
it didn't fail, only return an empty object and I do not know which can be the cause. Why return an empty object if I am in production mode with simulated false ?
I expected to return an object with more detail to be able to connect reader
hearty tartan
So are you able to accept payments when you try and collect payment method?
~~What happens if you try to get the connected reader using connectedReader param? ~~
https://stripe.dev/stripe-terminal-react-native/api-reference/index.html#:~:text=<ConnectReaderResultType>-,connectedReader,-%3A undefined |
actually try getConnectedReader() function instead: https://stripe.dev/stripe-terminal-react-native/api-reference/index.html#:~:text=undefined | EventEmitter-,getConnectedReader,-%3A ()
distant nova
I was thinking : if I didn;t have connected a reader I can't collet payment or I didn;t be able to call getConnectReader() function, but I will try tomorrow and I will return with another questions
so if that reader is empty, It can be possible to jump after some steps to connect directly ?
hearty tartan
so if that reader is empty, It can be possible to jump after some steps to connect directly ?
I'm not sure what you mean by that.. The reader object is a skeleton for all types of readers. Like smart, bluetooth, USB etc
It is possible for the values to be null in cases where the connection mode is different. Like bluetooth reader won't have an IP address until the connection has been established between the SDK and the reader and I think the same restriction apply on Local reader (tap to pay) too
distant nova
Thank you for the information, but for the moment I have to leave