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

Return the error when appcenter cli is not logged in #1241

Closed
jeremybarbet opened this issue May 23, 2022 · 0 comments · Fixed by #1243
Closed

Return the error when appcenter cli is not logged in #1241

jeremybarbet opened this issue May 23, 2022 · 0 comments · Fixed by #1243

Comments

@jeremybarbet
Copy link

jeremybarbet commented May 23, 2022

Environment

How do you use Sentry?

  • Saas

Which SDK and version?

  • @sentry/cli 2.0.4

Steps to Reproduce

  • Being logged out of appcennter (appcenter logout)
  • Run sentry-cli react-native appcenter <APP> <PLATFORM> <PATH>

Expected Result

When running this command directly from the terminal (appcenter codepush deployment history <DEPLOYMENT> --app <APP> --output json) that will results to:

{"succeeded":false,"errorCode":5,"errorMessage":"Command 'appcenter codepush deployment history' requires a logged in user. Use the 'appcenter login' command to log in."}

But it's not the case through the rust implementation. I wanted to contribute and return this error, but somehow I got an issue when trying to run the docker command: docker run --rm -v (pwd):/work sentry-cli react-native appcenter --log-level debug ... which throw

can't execute 'node': no such file or directory

In short, would be nice to get this error through the rust cli.

Actual Result

The command above gives the following error:

error: Failed to load AppCenter deployment history
  caused by:

Created a PR to make the documentation more clear on the docs repository: getsentry/sentry-docs#5063

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

Successfully merging a pull request may close this issue.

1 participant