#megalo_apps-sandbox
simple depotBOT
👋 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/1509274058381066281
📝 Have more to share? Add more details, code, screenshots, videos, etc. below.
gloomy quartz
Is the external test account a sandbox account?
grave flame
Yes a sandbox (not verified yet)
But I can't use the sanbox Oauth. I only able to use the test Oauth url
gloomy quartz
My suspicion is that's the issue but I'm not sure. I haven't seen this error before
Do you have another non-sandbox account you can test with
grave flame
Sadly no. I only have 1 account (verified business) but it will be the creator / publisher account for the apps
gloomy quartz
Why can't you use the sandbox link?
Also have you done: https://docs.stripe.com/stripe-apps/review-requirements#sandbox-support ?
grave flame
not sure why, just got this when I tried opening the sanbox mode url.
*also let me read that requirements docs first. I thought that was for publishing (which require a review from stripe).
gloomy quartz
No that doc is a prerequisite linked in the external test guide: https://docs.stripe.com/stripe-apps/test-app#before-you-begin
So yeah willing to bet you just haven't enabled sandbox installs
Not sure why we allowed you to use test install link though for a sandbox
But I recommend uninstalling and starting from scratch with sandbox installs enabled in your manifest
grave flame
I see...
let me try first. And get back to this thread if I still facing similar/weird issue 🙏
grave flame
Hey,
I'm able to install it now in sandbox mode.
But I'm still getting this erorr in the browser console's network tab:
{
"error": {
"message": "No such app_listing: tailorapp*AZ4YN3OHYwAAACA0#EhcKFWFjY3RfMVNlS2o5RkhmMWw1YWRoTQ",
"message_code": "missing_resource",
"type": "invalid_request_error"
}
}
It's on sanbox mode url, the app installed in sanbox account, but still got same issue.
My next attempt is to use a non-sanbox (verified business) account. But if you have any thing that I need to check, please let me know.
simple depotBOT
timid granite
megalo_apps-sandbox
Can you look at the Headers tab and see if there's a request id req_123 anywhere?
Disclaimer: Stripe Apps make no sense to me so I can never debug any of this but I'll try
you might want to delete, this might have some session/cookie id to avoid sharing but yeah no req_123
I'm looking into it, give me a bit of time
grave flame
wait, I saw a request id on response header
request-id
req_cPlwZunoMtdzBF
server
nginx
strict-transport-security
max-age=63072000; includeSubDomains; preload
stripe-action-id
dub1Dth7wlP1D3T0noxMyjU
stripe-notice
You are using an outdated API version (2025-06-30.basil). We recommend upgrading to the latest API version, 2026-04-22.dahlia. See https://docs.stripe.com/upgrades
stripe-version
2025-06-30.basil
x-content-type-options
nosniff
x-robots-tag
none
x-stripe-priority-routing-enabled
true
x-stripe-routing-context-priority-tier
api-testmode
x-wc
3ff
timid granite
ah nice, that's what I needed
Also just to be clear, are you testing on your own Stripe account in Test mode, or in a separate Sandbox?
grave flame
So I have 2 accounts
1 is the publisher (where the stripe apps created/ and will be published)
the other 1 is a dummy account, I want to test the Oauth
the dummy account is a sanbox (not a verified business)
timid granite
ahhhhhh
yeah that can never work I think
Your app has to be published to work on other accounts
Still digging in that error and trying to figure out what you did. Reall sorry you ended up with me and I don't understand this product at all 😓
grave flame
I see, but publishing requires a "review" process. I just want to try to test the experience from external account perspective.
I tried to use the External test url. And now I'm stuck here.
*it's okay, I think this is edge cases, or I might miss something.
timid granite
https://docs.stripe.com/stripe-apps/enable-sandbox-support#test-your-app-in-a-sandbox did you see this?
Sandboxes are weirdly different from our "legacy Test mode" flow (even though we try to pretend it's the same)
grave flame
Okay, I followed few steps
- use the managed sanbox keys
- enabled the manifest
sandbox_install_compatible: true
except this one:
- Create a new sandbox to test your updated app. Open the new sandbox
It seems the testing only feasible with sanbox env in same account 🤔 is this true?
*in the meantime let me test this also.
timid granite
Can you share the account id for both accounts? The one with the app and the one you're testing on
grave flame
main acc: acct_1SeKj9FHf1l5adhM
test/dummy acc: acct_1TZGndPGVrYiLBN5
timid granite
you seem to have 2 Apps on that first account, which one are you testing right now?
grave flame
something with version 0.0.1-dev.15
the other one, can you help me to delete it? I can't delete not sure how
timid granite
no idea sorry lol but all good I see the right one
Which of the 3 link did you use to do your test?
grave flame
the sandbox link
timid granite
can you try the second one Test mode link
Okay
Let's pause for a sec
You have a "separate account" with the id acct_1TZGndPGVrYiLBN5
but when you try to test you really are in a Sandbox which is a completely separate Stripe account with the id acct_1TZGnmAa3UYZIBau which is completely different. That second account has the App installed
is it possible you got mixed up when you tested? Like what exact URL are you on right now?
grave flame
can you try the second one Test mode link
I tried, same issue. White blank page
{
"error": {
"message": "No such app_listing: tailorapp*AZ4YN3OHYwAAACA0#EhcKFWFjY3RfMVNlS2o5RkhmMWw1YWRoTQ",
"message_code": "missing_resource",
"type": "invalid_request_error"
}
}
This is the test mode which is using acct_1TZGndPGVrYiLBN5
and the sanbox mode also same issue, which is using this account: acct_1TZGnmAa3UYZIBau
timid granite
Can you share the exact URL you are on when you try to do this?
grave flame
You mean this (the app url after Oauth)
- https://dashboard.stripe.com/acct_1TZGnmAa3UYZIBau/test/app/com.gocockpitai.cockpit
- https://dashboard.stripe.com/acct_1TZGndPGVrYiLBN5/test/app/com.gocockpitai.cockpit
or the oauth url from main account?
timid granite
are you okay with me installing that app just to try and reproduce?
grave flame
yes, it still not production ready yet. so should be okay
timid granite
I tried but I get
{"code":"STRIPE_APP_OAUTH_EXCHANGE_FAILED","message":"Stripe OAuth rejected code (status=400): {'error': 'invalid_grant', 'error_description': 'Authorization code provided does not belong to you'}","errors":[]}
did that step work for you?
grave flame
This is our backend logic.
Help me to understand a bit. Because I use the managed-sandbox secret key for the API signing. And because of that there's a mismatch happening on the signature.
It works for the test account sandbox, but not a new sandbox created on my main account.
Is this the correct approach? Did you try it on new account's sanbox? or on my account but with new sanbox?
But this is our issue. The issue I mentioned above is happening after this exchange step.
timid granite
I tried it on a brand new Stripe account
Okay so just to be super clear: you have never been able to finish the OAuth flow at all?
(except on your main account)?
grave flame
I did on the Test/Dummy account.
btw, let me fix that exchange issue first. This is separate issue. This is on me.
But the original issue
{
"error": {
"message": "No such app_listing: tailorapp*AZ4YN3OHYwAAACA0#EhcKFWFjY3RfMVNlS2o5RkhmMWw1YWRoTQ",
"message_code": "missing_resource",
"type": "invalid_request_error"
}
}
happening after the exchange step from our API. So once I fix the issue on our side, I received that error.
Let me get back to you later on this thread.
timid granite
sounds good