Open hannojg opened 12 months ago
Hi, thank you for the report. Are you sure you're using the org slug and not the display name? I wouldn't expect an org slug to contain an uppercase letter.
Hey, yeah we 100% used the org-slug. I have to ask the client but I assume the sentry account existed for a very long time (I guess nowadays you can't create a org with an uppercase letter?)
// Edit: I remember the client saying that he thinks the org-slug was even auto suggested to them when creating sentry - maybe that's a hint, that a system somewhere allows suggestion for uppercased names?
The org name has been renamed to circumvent this bug, but I just found proof in an email, it says "sail-Ok" which was the prior org name with a uppercase O
Interesting, I didn't think that was possible. I'll pass it along.
This issue has gone three weeks without activity. In another week, I will close it.
But! If you comment or otherwise update it, I will reset the clock, and if you label it Status: Backlog
or Status: In Progress
, I will leave it alone ... forever!
"A weed is but an unloved flower." ― Ella Wheeler Wilcox 🥀
Not sure, but we might want to keep that open?
Yes, let's keep this open. Maybe @loewenheim has an update once he's back.
This issue has gone three weeks without activity. In another week, I will close it.
But! If you comment or otherwise update it, I will reset the clock, and if you label it Status: Backlog
or Status: In Progress
, I will leave it alone ... forever!
"A weed is but an unloved flower." ― Ella Wheeler Wilcox 🥀
Not stale <3
Thanks @hannojg, I have placed the issue on our backlog to ensure StaleBot doesn't touch it
Hey all! I got this to work. I found that even though I already have the SENTRY_AUTH_TOKEN
in my eas.json
, I still had to add the SENTRY_AUTH_TOKEN
as a secret in Expo's EAS Cloud Dashboard as a secret in order for this to work, so there seems to be an issue with some variables in eas.json
not being used in the build proces.
I hope this helps.
Environment
CLI:2.17.5 OS: MacOS 14.0
Steps to Reproduce
Quick repo:
https://sentry.io/api/0/projects/{organization_slug}/{project_slug}/files/dsyms/
Extensive repo:
The api above is what the sentry-cli is trying to call when it executes the
Upload Debug Symbols to Sentry
step, when running:So you could reproduce by also setting up a iOS project and try to build it.
Expected/Actual Result
Expected: You get a 200 response
Actual: You get a 404 response
This post suggests that its due to the uppercase letter in the org name: https://forum.sentry.io/t/404-while-uploading-dsym-in-onpremise-setup/6217/2
Logs
Note: Also what's weird is that the API adds a
/unknown
path to the request URL. either that's a bug or a hidden API feature, not sure.