#dev-travis_docs
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/1423657195500732456
๐ Have more to share? Add more details, code, screenshots, videos, etc. below.
Hi there, looking into this now
Can you share the code that processing these payments?
Still looking, nothing immediately stands out from the code yet
I haven't found any issues with memory leaks specifically from the Stripe React Native SDK. In order to determine if this is coming from Stripe React Native vs other parts of your codebase, we would need a minimal reproducible example that focuses on the Stripe related code. If that example doesn't have a memory leak, then your issue is in other parts of the codebase. If it does have a memory leak, then you can file the issue on the GitHub repo, which the team actively monitors: https://github.com/stripe/stripe-react-native/issues
After a successful payment with Stripe, should we perform any additional cleanup steps?
For example:
Do we need to explicitly end or clear any previous sessions (e.g., reader, transaction, or discovery sessions)?
Or does the Stripe SDK handle this automatically after a successful payment?
I believe the Stripe SDK handles it, but I will double check
any updates?
Yes, I confirmed that the Stripe SDK will handle this automatically. What could happen is there can be a JavaScript closure that is holding on to some variable that might be preventing the memory from being released. The only way to tell is by creating that minimal reproducible example