You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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:
Environment
How do you use Sentry?
Which SDK and version?
Steps to Reproduce
appcennter
(appcenter logout
)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: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 throwIn 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
The text was updated successfully, but these errors were encountered: