To reproduce:

1. npm install create-react-app -g
2. create-react-app demo
3. cd demo && npm install @exponent/sentry-utils
4. Add to src/App.js

   import ExponentSentryClient from '@exponentjs/sentry-utils';
   ExponentSentryClient.setupSentry([SENTRY DSN], [RELEASE], [EXPERIENCE ENTRY FILE]);
   

5. npm run build

The publish script isn't working for me. On the command line, it says that it went through, but when I check Sentry, there are no artifacts. My suspicion lies in the usage of getsentry.com instead of sentry.io in your scripts, because sentry now uses the latter domain.

CLI Output:

Checking for clean work tree...

Publishing a release for 'ios' platform on the 'juwan-wheatley/pul' Sentry project...

Please entry your XDE host port: 19000

Current version: v0.1.1
Bump version?
1) Yes
2) No
#? 2

Releasing 0.1.1...
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100  1257  100  1257    0     0  32559      0 --:--:-- --:--:-- --:--:-- 33078

Fetching build from XDE...(may take a while, due to minify)
######################################################################## 100.0%

Fetching source map from XDE...
######################################################################## 100.0%

Modifying bundle and source map...
Delete existing Sentry release?
1) Yes
2) No
#? 2
Creating Sentry Release:
######################################################################## 100.0%

Uploading source to Sentry:
######################################################################## 100.0%

Uploading source map to Sentry:
######################################################################## 100.0%

===============================================================

If you change code between now and uploading to exp.host, be sure to run this script again!
--Fin

Thanks

Looks like the client has a method for logging warnings (via Raven.captureMessage()), but not for capturing exceptions. Should we be using this method for capturing exceptions as well, or should we be using Raven.captureException() directly?

I'm also happy to write a logException() method I added a logException() method in #9 that could also be used.

Hi expo team,

I find publish-sentry-release really handy but I'm kind of confuse about platform and "Delete existing Sentry release?" logic.

publish-sentry-release requires a platform as one the the arguments, which makes sense because the bundle for ios can be different to the one for android.

So I was trying to upload a bundle per platform but I got prompted with "Delete existing Sentry release?" whenever I try to upload the second one.

Looking at the logic that checks for existing bundles, it doesn't have platform as a parameter.

  local releaseStatusCode=$(curl -o /dev/null --silent --write-out '%{http_code}' -H "Authorization: Bearer $SENTRY_AUTH_TOKEN" "https://app.getsentry.com/api/0/projects/$SENTRY_TEAM/$SENTRY_PROJECT/releases/$RELEASE_ID/")

This makes me wonder, which is the correct way to upload bundles per platform? Am I doing something wrong?

Thanks in advance,
JM

It would be really helpful if this script was able to be called programmatically without interactive prompts, but instead using flags so that one could use this in a CI environment where one can't enter options inside the terminal