Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

getting an error when trying to upload dsym #137

Closed
pvinis opened this issue Nov 1, 2017 · 11 comments
Closed

getting an error when trying to upload dsym #137

pvinis opened this issue Nov 1, 2017 · 11 comments
Assignees

Comments

@pvinis
Copy link

pvinis commented Nov 1, 2017

hello. i just installed the latest sentry-cli, and tried to do sentry-cli upload-dsym SwiftExample.app.dSYM.zip using the zip from the fastlane sentry plugin. i immediately get a error: EOF while parsing a value at line 1 column 0.
since this tool is used by the fastlane plugin and by the react native build phase, basically all three ways error out.
what is the problem?
is it something with my setup or something with this project?

@pvinis
Copy link
Author

pvinis commented Nov 1, 2017

btw i am trying with the brew version, latest, 1.12.0. i just tried to compile with cargo build and ran it, and it works fine, by asking me to enter an organization.

@jan-auer
Copy link
Member

jan-auer commented Nov 1, 2017

Thanks for reporting this issue. Just to clarify, you have sentry-cli version 1.21.0 installed and not 1.12.0, correct? Otherwise, please update your installation with homebrew.

Since the latese release we have not changed anything regarding dSYM uploads. However, we're planning a new release in the next couple of days. Since the development build works for you, this should resolve your issues. If it still persists, we can start to investigate this.

@jan-auer jan-auer self-assigned this Nov 1, 2017
@pvinis
Copy link
Author

pvinis commented Nov 1, 2017

yes, sorry. 1.21.0 indeed.

@pvinis
Copy link
Author

pvinis commented Nov 1, 2017

actually, im still trying to figure this thing out. if i run it from some specific directory, i get the error. in other directories, with the same command (absolute paths etc), i get no error..

@jan-auer
Copy link
Member

jan-auer commented Nov 1, 2017

Could you please share the CLI invocation that is causing the error and maybe add some context on your build setup? Also, please try to unpack the zip and pass the --no-zips so we can start to isolate the issue.

@pvinis
Copy link
Author

pvinis commented Nov 1, 2017

SENTRY_AUTH_TOKEN=blabla sentry-cli upload-dsym -o myorg -p myproj ~/Source/dir/some-other-dir/builds/MyApp.app.dSYM.zip
this is what i need to run, and i was running that but with the example swift dsym from the other repo of sentry.
somehow it works after i removed all the files from my repo/dir, and then brought them back with git. it was running normally except when i was in the actual project dir. i have no idea why instead of giving some normal error, it just breaks with the EOF error.

@jan-auer
Copy link
Member

jan-auer commented Nov 1, 2017

If you have the chance to reproduce, please run with --log-level=debug (as first argument to sentry-cli). From what you have shared thus far, I suspect that there was an invalid .sentryclirc or sentry.properties file in that folder which is why the error only occurs in certain directories.
For the record, this is probably related to #94 and getsentry/sentry-react-native#135

@pvinis
Copy link
Author

pvinis commented Nov 2, 2017

it is, but as you see, both are closed and unsolved. also, i tried adding --log-level=TRACE at some point, but i kept getting an error that unexpected log-level was added. can you have support for it anywhere in the call? i should be able to add it in the start, end, in the middle, anywhere.

@jan-auer
Copy link
Member

jan-auer commented Nov 2, 2017

Please invoke it like this: sentry-cli --log-level=debug upload-dsym ...

@jan-auer
Copy link
Member

Any update on this?

@jan-auer
Copy link
Member

jan-auer commented Feb 1, 2018

Closing this due to inactivity. Please feel free to reopen, if the problem persists.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants