#harcon_code

1 messages ¡ Page 1 of 1 (latest)

viscid wraithBOT
#

👋 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/1220400676862165152

📝 Have more to share? Add more details, code, screenshots, videos, etc. below.

past pilotBOT
grave plover
#

Hello, can you tell me what debugging happens around the crash? Do you get a certain exception or error, or anything else like that?

stiff tiger
#

@vivid shuttle

grave plover
#

I am still not sure what this may be. I will consult my colleagues on this and get back to you

quiet rivet
#

hmm yeah not sure we can sugest anything here but continue to use the older version until we fix this

#

I'll flag again internally so we continue to prioritise working on this

#

alternatively, you could use the PaymentSheet integration instead!

#

FWIW I use the <CardField> in my own demo app using 0.37.1 of our React Native library and it works fine. Is the crash only when it's inside a modal or some other type of specific view, in your case?

stiff tiger
#

Thanks for your message, and yes I believe so - out of interest and sanity, calls to /v1/tokens are done 'under the hood' using the SDK correct? So I am right in saying in order to be using the latest version of the API in those calls, we need to be on the latest version of the SDK.

quiet rivet
#

yes the calls are made by the SDK

#

I think it pins an API version, let me check, maybe you can override it. But also I don't think it matters (I don't know why we decide it's important to flag it as an "issue" on the dashboard personally) since it doesn't really change anything

stiff tiger
#

Thank you, can you also perhaps tell me what version of the SDK uses at least the 2023 API? The issue seems to be arising on versions prior to that

vivid shuttle
#

Hey guys. I'm here.

quiet rivet
#

like the fact the mobile SDK calls /v1/tokens using an old API version really doesn't matter (beyond some page on the Dashboard flagging it as a warning?) since we have never changed the /v1/tokens API shape; so I wouldn't focus too deeply on that.

if you're saying there's some crash in your app, let's try to get some technical detail about that like a stacktrace or example code to repro?

vivid shuttle
#

The crash we're seeing is the same thing mentioned in the GitHub issue posted above, so a stacktrace should be in there.

#

We're assuming this is not avoidable at the moment and if we want to use the latest SDK we would have the use the PaymentSheet.

#

@quiet rivet Is there any intent to deprecate the Card Element only?

quiet rivet
#

so to clarify you have a similiar set up to the users in that thread, in that you have the UI in a modal/other UI etc?

#

and to be clear https://github.com/stripe/stripe-android/pull/7787 might be the fix for that overall issue, but I'm not 100% if that is available in React Native yet(we fix/add things in stripe-android, and then a future relase of stripe-react-native bumps its own dependencies a little while later)

vivid shuttle
#

Yes that's correct--using it in a modal.

quiet rivet
#

then yeah seems like your options are

  • stay on old versions
  • wait for a fix from us(I've already re-pinged this internally to the teams involved to have another look)
  • use a different integration like PaymentElement
quiet rivet
#

but I don't see it ever going away completely

past pilotBOT