#bryanthompson_unexpected

1 messages · Page 1 of 1 (latest)

high bobcatBOT
#

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

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

finite raven
#

Can you share the account ID you're working with?
I suspect the account was connected using oAuth flow and only in live mode

hoary rain
#

Yes - acct_1AQ1k4HRaRDRJp5f is the connected account.

In my local env, I kick off the oAuth process and am able to see the 'test' banner and such. This account is also connected in production, so hopefully you see all of that.

#

also hi, and thank you 🙂

finite raven
#

Can you share the request ID where you're seeing the API error?

hoary rain
#

looking now

#

Here's one: req_nBBS72elLVjwUD

#

By that point i had started cutting from components & features, here's an early one that isn't as chopped: req_C4jglqaXRt1CWg

small depotBOT
molten zephyr
#

Thank you for the request IDs, looking in to them

hoary rain
#

Thank you

molten zephyr
#

So it looks like we always throw this error for accounts made in livemode, even if a testmode connection also exists. It looks like we want to discourage users from testing through the test mode connection on other real accounts. Tour test account's connection looks like it is a real account because it was created in live mode, so it is getting blocked by that restriction.
So I think you will need to create a new connected account in test mode and test with that. I get that that is inconvenient, and can put in feedback about this, but for now that is how you would have to test.

hoary rain
#

Interesting... I will give that a shot. Is there a reason this particular feature has this preference?

#

I ask because we may need to alter our dev env strategy for consistency and onboard fresh test accounts or I'll be fielding questions left and right 🙂

hoary rain
molten zephyr
#

I'm not immediately sure but will see if I can find a reason. My guess is that we didn't want to break backwards compatibility, so it is still allowed on existing features, but we will disallow it on new features as they are rolled out.

hoary rain
#

Roger, that makes sense.

I'll take the next steps here. I really appreciate your time and help on this.