#robinsky_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/1379482777090527311
📝 Have more to share? Add more details, code, screenshots, videos, etc. below.
Hello, if you open RN's dev tools, are any errors outputted when this crash happens? Also, is this in both iOS and Android?
I get this from the JS debugger whenever the crash occurs. (No other errors displayed)
Only tried on iOS.
stripe.api_key = config.STRIPE['secret_key']
endpoint_secret = config.STRIPE['endpoint_secret']
@router.post('/payment-sheet')
async def payment_sheet(deposit: DepositRequest):
customer = stripe.Customer.retrieve("SOME ID")
ephemeralKey = stripe.EphemeralKey.create(
customer=customer['id'],
stripe_version='2024-12-18.acacia'
)
paymentIntent = stripe.PaymentIntent.create(
amount=deposit.amount * 100,
currency='usd',
customer=customer['id'],
setup_future_usage='off_session',
payment_method_types=['card']
)
response = {
"paymentIntent": paymentIntent.client_secret,
"ephemeralKey": ephemeralKey.secret,
"customer": customer.id,
"publishableKey": "MY KEY"
}
return response
To give you better context, this is how I generate the payment intent, customer and ephemeral key from my server.
Hi hi! I’m going to be taking over for my colleague here. Are you able to get any further details or logs from the device indicating what the error is?
Hi! I will try to give you some logs but from what I experienced so far, it just silently crashes the app. Let me try to give you some output.
I get :
Unknown device with ID XXXXXXXX
at WebSocketServer.<anonymous>
Whenever the crash happens which is normal I guess
I mean, without logs to at least see where it is occurring, it's going to be near-impossible to diagnose this.
Ahh that's frustrating. Unfortunately without seeing details of the error, there's not going to be much anyone can do to help diagnose this.