#Dario - 403 error
wooden monolith
We don't have access to the request ID. We only have an image of the browser console from the user that specifies that the call 403'd. When we simulate this in our test environment, the UI of the Stripe App behaves the same way the user describes.
Near as we can tell though, there's not supposed to be a way to 403 on that call.
round solstice
Should we ask the user to open Developers / Logs or is it expected that this request is visible on the app's owner account? (To which we have access to.)
royal nova
It should show in your developer logs. If not, can you give me the account ID so I can track down the issue?
wooden monolith
To be clear, the calls don't show up in our developer log, because in a Stripe app frontend, they're not made with our key. Are you asking us to give you the account ID of the affected customer?
royal nova
No the acct_123 id. I can't investigate the issue unless I can see some logs/request id's that are failing
wooden monolith
Our app-hosting account is: acct_1Kr0pTFI0h79qFpp
But the affected user is: acct_1BfQVaFlB8ujOrUc
crystal dawn
Hello 👋
Taking over as codename_duchess needs to step away
Give me a moment to catch up 🙂 thanks
I'm not super familiar with Stripe Apps so its taking a while, Appreciate your patience.
cedar osprey
Hey there! Taking over here with some Stripe Apps context
Ok, cool. The team are actually on this already (I guess the error flagged up in logging)
Hopefully have some progress to share on this soon
wooden monolith
Awesome, thank you!
cedar osprey
We'll keep this thread active and relay updates
austere skiff
@round solstice can you work with our support team directly: https://support.stripe.com/contact explain you talked to us and that the engineering team is investigating and they can keep you updated as needed