#atoro-aws
true badger
hi! I don't really follow. Do you have a link to that Github issue maybe with more context?
lapis merlin
Here's the link: https://github.com/dj-stripe/dj-stripe/issues/1637
the full API 404 from the Stripe API is
{
"error": {
"code": "resource_missing",
"doc_url": "https://stripe.com/docs/error-codes/resource-missing",
"message": "No such file upload: 'https://s3.amazonaws.com/stripe-uploads/acct_17eWfWKdLeAuUpPvmerchant-icon-1455482561989-FH2.png'",
"param": "file",
"type": "invalid_request_error"
}
}```ok, we know nothing about dj-stripe to be clear, that's a third party.
But for the Stripe side, can you share the actual req_xxx value so I can have a look at the log?
lapis merlin
here's one from a few minutes ago: req_tjijO2cqYhNypm
true badger
thanks
hmm yeah, that request doesn't make much sense really. That's not how our API works, the file upload is not a raw AWS URL, it's a file_xxx object identifier.
Do you know the price_xxx it's trying to sync? Maybe I can figure out what that dj-stripe sync thing is trying to do wrong.
lapis merlin
let me check Sentry, see which one it starts with
{
active: True,
billing_scheme: 'tiered',
created: 1648599663,
currency: 'usd',
id: 'price_1KipHXKdLeAuUpPvOKRtf9wB',
livemode: True,
lookup_key: None,
metadata: {},
nickname: None,
object: 'price'
}```looking at the tracebacks, it looks like this error is coming from the base stripe lib
true badger
interesting. In my opinion what it's probably doing is as part of the sync it retrieves your Account object(you can see it doing here https://dashboard.stripe.com/logs/req_1EsIwOGFNwFFQ2 just before it gets the error) and then it looks at the https://stripe.com/docs/api/accounts/object#account_object-settings-branding-icon field
oh I know why I think, your Stripe account is quite old and at some point in time we did I think change this from being a raw URL to a file_xxx ID
lapis merlin
ahhhh, gotta love data structure changes
any way to refresh it into the new format?
true badger
I'm not sure this works, but try going to https://dashboard.stripe.com/settings/branding and uploading a new icon there(can be the same image (you can download it from the AWS link and save locally and re-upload in the dashboard)) and that might fix the state
lapis merlin
I'll give that a shot, thank you for the help so far
...it can't really have been that easy
welp, I'll go update that Github issue and close it, thank you again!
true badger
cool, so that worked?
lapis merlin
worked right away
true badger
ok, great! sorry for the problem. Technically that was a breaking change we made a while ago unfortunately and we didn't "backfill" the field to update to a file upload for reasons at the time. I'm just glad I remembered this...