sentry-android-gradle-plugin: Execution failed for task ':app:uploadSentryProguardMappingsEnvProductionRelease'. > Process 'command '/var/folders/mr/9xvfs__s61dddrt8fssgsq7r0000gn/T/.sentry-cli5305713540715026686.exe'' finished with non-zero exit value 1

Gradle Version

7.6-rc-1

AGP Version

7.4.0

Code Minifier/Optimizer

Proguard

Version

3.12.0

Sentry SDK Version

nil

Steps to Reproduce

  1. Try to build the apk in release env
  • compileEnvProductionRelease
  1. Task :app:uploadSentryProguardMappingsEnvProductionRelease fails with the below messages
> Task :app:uploadSentryProguardMappingsEnvProductionRelease
  INFO    2023-10-18 10:51:23.848597 +05:30 Loaded file referenced by SENTRY_PROPERTIES (/Users/gopikrishnans/AndroidStudioProjects/ecom_android_mobile_app/sentry.properties)
> compressing mappings

> Task :app:uploadSentryProguardMappingsEnvProductionRelease
> uploading mappings
error: not a JSON response

Add --log-level=[info|debug] or export SENTRY_LOG_LEVEL=[info|debug] to see more output.
Please attach the full debug log to all bug reports.

> Task :app:uploadSentryProguardMappingsEnvProductionRelease FAILED
not a JSON response

Execution failed for task ':app:uploadSentryProguardMappingsEnvProductionRelease'.
> Process 'command '/var/folders/mr/9xvfs__s61dddrt8fssgsq7r0000gn/T/.sentry-cli5305713540715026686.exe'' finished with non-zero exit value 1

* Try:
> Run with --stacktrace option to get the stack trace.
> Run with --info or --debug option to get more log output.
> Run with --scan to get full insights.

This is the Sentry.properties file

defaults.url=https://****.sandbox.****.co/
defaults.project=ecom-android-mobile-app-sandbox
defaults.org=*****
auth.token=******

Expected Result

The release apk is generated

Actual Result

The release APK generation fails since the Sentry can’t upload proguard mapping files.

About this issue

  • Original URL
  • State: closed
  • Created 8 months ago
  • Comments: 15 (9 by maintainers)

Most upvoted comments

@romtsn Our DevOps team is trying to fix the re-direction issue you mentioned. We are not sure yet. Dont close this bug for another few days, please!