#noskill_best-practices
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/1400459764579700847
đ Have more to share? Add more details, code, screenshots, videos, etc. below.
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.
- noskill_stripe-apps-public-id, 2 days ago, 77 messages
Not sure why you'd need to upload the app to use fetchStripeSignature?
Let me find the doc, it's there as a step. And when I didnt do that I ran into errors. When you upload it gives you ownedship over the unique id of the app and that is needed to generate the signature
What exactly are you trying to test and what's not working? Is there an error? When is it thrown?
Ive been writing a stripe app and doing my dev loop with stripe apps start + localhost backend.
Now I want to have the equivalent of an end to end test environment that is closer to production. So that, I think, means the uploaded app in test mode + backend test env hosted in Azure.
Let me run the exact steps again and paste them here.
Is that proposed process accurate for how to do integration testing of a stripe app before going to production?
The recommended way is to set up an external test that can be installed on a non-publishing account: https://docs.stripe.com/stripe-apps/test-app#set-up-test
But uploading that way doesn't block testing, or at least shouldn't is my understanding
Does it need to be setup as a public app to do that?
I dont see External Test there
And how do I allow it to be installed in a non publishing account while also not making that version visibile to anyone else (in case it's broken)
Hi, taking over as my teammate needs to step away. Let me catch up.
Have you already uploaded the app in test mode: https://docs.stripe.com/stripe-apps/upload-install-app#install-your-app-in-test-mode ?
You can update the the version of yoru test app: https://docs.stripe.com/stripe-apps/test-app#update-test-version
External testing is currently only available for public apps.
You can set up an external test to enable other accounts to install your app before you publish and distribute a new version to the App Marketplace. : https://docs.stripe.com/stripe-apps/test-app#update-test-version