#santhosh-kumar-r_api
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/1409766144977404015
๐ Have more to share? Add more details, code, screenshots, videos, etc. below.
- We are using this package '@stripe/stripe-terminal-react-native';
- We confirmed that there is no backend issue from our side; Our server is working fine
hello ๐ give me some time to catch up
Sure
feel free to provide more context if there is!
- This is happening in most of our device;
Issue Cabinet;
We logged for all stages in the sdk; it is not creating the payment intent
https://drive.google.com/file/d/1kGx804slfOhjGQ_3Fi2S4eeCfSvIO_9Y/view
Is there a specific error that's preventing PaymentIntent from getting created? I also do not have access to the google drive you shared.
Could you share with me the an impacted reader's serial number to use as an example?
sry for that; use this link
https://drive.google.com/file/d/1FZuF5zWtpOOHu_fef56AUKSte8qvpzoo/view?usp=drive_link
i think it is a issue in SDK
We are using this method;
const {createPaymentIntent, collectPaymentMethod} = useStripeTerminal(terminalConfig);
This function "createPaymentIntent" is not resolved
I can't verify without looking into the reader's log. Do you have the serial number of an impacted reader for us to use as an example?
sure; let me check
my client is offline now;
but i have the another reader serial number where we got this error on last thrusaday (4-5 days before)
will that help ?
Yup that would work
WPC323225003514
Info:
it is in production
Please make sure our debugging wont affect the production environment
It won't. We are just looking into the reader's logs
Would you be able to specify the date where this error occured?
no worries, so its 21 August then. I'll need some time to look into this with my team, appreciate your patience in the meantime
Hi @golden knot I'm also an engineer from Stripe. Was the the reader connected when you call createPaymentIntent ?
i think so
We can check here
I don't see any debug information in the video incidating that the reader was still connected
ok. you mean to check the status from SDK ?
connectedReader attribute ?
Also I noticed that the Bluetooth icon was blinking in the video, it seemed to me that the reader wasn't connected to your mobile device.
we are using USB to connect;
will POS disconnect after long time of activity ?
from SDk
we observed this issue only after long time of activity; when we restarted, it is working
ok; Let me check with client
if yes , what is the max time ?
can nt i keep the POS connected to our sdk without any disconnects ?
if it is disconnects how do we know, any guidance or docs reference will be much appreciated
Hi @golden knot the wise pad 3 will switch off after 5 mins https://docs.stripe.com/terminal/payments/setup-reader/bbpos-wisepad3#power However, watching the video, the device was powered on.
I'd also recommend adding some code in your app to ensure the reader is connected before calling createPaymentIntent
ok. i asked client but they said that bluetooth icon is also flahsing on working device too
Is the USB cable always connected to the android device?
can nt i keep the POS connected to our sdk without any disconnects ?
Hey! Taking over for my colleague. You can configure the SDK to reconnect automatically, when it disconnects by settingautoReconnectOnUnexpectedDisconnectto true on theConnectUsbReaderParams.
https://docs.stripe.com/terminal/payments/connect-reader?terminal-sdk-platform=react-native&reader-type=usb#handle-disconnects:~:text=Set autoReconnectOnUnexpectedDisconnect to true on the ConnectUsbReaderParams.
if it is disconnects how do we know, any guidance or docs reference will be much appreciated
Yes, there is a Callback calledonDidDisconnectthat notifies your App whenever the Reader got disconnected
https://docs.stripe.com/terminal/payments/connect-reader?terminal-sdk-platform=react-native&reader-type=usb#handle-disconnects:~:text=UserCallbacks includes onDidDisconnect that provides your application with the DisconnectReason to help identify why the reader disconnected.