-
-
Notifications
You must be signed in to change notification settings - Fork 32
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
A problem occurred starting sentry-cli-2.31.2.exe on Linux #728
Comments
hi @listvin |
@listvin did you have the opportunity to get a better log from it? |
Same here on macos: gradle plugin downloads and invokes Windows version of sentry cli with name sentry-cli-2.31.2.exe, not linux or macos version. It brokes gradle sync and I can't continue to work on my project. |
The extension (.exe) does not matter, you can even call it @RinatTalibullin please check your full Gradle logs, there will be the reason why the cli failed. Most likely you haven't specified org/projectName/authToken. |
I actually did nothing: it worked with previous versions of cli and it just stopped now. So my project was working correctly before. There are logs:
|
Still, manual run ./sentry-cli-2.31.2.exe on macos actually works and cli writes to terminal. Maybe something wrong with the plugin or how plugins starts cli? |
Further investigation showed, that in my case the issue was with gradle wrapper version 8.8. Wrapper versions 8.7 and 8.9 work correctly. |
@RinatTalibullin thanks for sharing the details, we'll try to reproduce with Gradle 8.8 and get back to you |
hey, good news everyone - seems we were able to reproduce the issue and the fix is on its way #748 |
Integration
sentry-android
Build System
Gradle
AGP Version
8.3.0
Proguard
Enabled
Version
io.sentry.android.gradle 4.7.1
Steps to Reproduce
bash:
SENTRY_OFFLINE=1 ./gradlew assembleProdRelease_r8
./gradlew uploadSentryProguardMappingsProdRelease_r8
ProdRelease_r8
here is flavour (Prod) + buildType (Release_r8).My build.gradle contains:
May be relevant: I am on LTE, good one, but still.
Expected Result
The first one should be able to complete build offline (with no connection to Internet), second uploads mappings.
It works as expected and never let me down before.
Actual Result
Now I just got following:
I did rerun same task with --debug, but didn't see issue again. I can not reproduce it. In my build script I inserted --debug for last task and saving of log, but for now this is all I have.
It is frustrating bc my custom build pipeline does a lot of work (like 20 minutes?) before this last step and has to be restarted.
Is invoking .EXE file normal part of mapping upload from LINUX?
The text was updated successfully, but these errors were encountered: