Failed to Generate Signed Apk - An organization slug is required (provide with --org)

Question

After setting up the Sentry.io error tracking I get this error when I try to Generate Signed Apk:

Java Compiler
error: An organization slug is required (provide with --org)

Click on this image and open it to see more details:

I cannot understand anything from this one:

Process 'command
'/var/folders/j4/_fzm1rks3tsc2h3j4l2qbq4w0000gn/T/.sentry-cli1369818638611304938.exe'
' finished with non-zero exit value 1

This is the file address that was raised in error:

How can I solve this problem and Generate Signed Apk?

Answer 1

IT IS NOT A REAL ANSWER But it can solve our problem in the short term by setting false value to minifyEnabled.

app/build.gradle:

buildTypes {
    release {
        minifyEnabled false
        proguardFiles getDefaultProguardFile('proguard-android.txt'), 'proguard-rules.pro'
    }
}

but it added 1.3MB to the size my of Apk file.

Please let me know if anyone has a different better solution.

Answer 2

When you enable Proguard minification, symbols are uploaded to Sentry. This upload is done via the sentry-cli, which is throwing the error. The error says the CLI doesn't know which project within Sentry to associate your symbols with. You need to make sure to go through the gradle integration in the docs. Specifically:

defaults.project=airflow
defaults.org=sentry
auth.token=YOUR_AUTH_TOKEN

Alternatively you can use sentry-cli directly to upload symbols, although the gradle integration is advised.

Answer 3

The docs are not a bit clear, though its mentioned but easy to miss it. There are two different sentry.properties required here.

Please note the sentry.properties in your project root that configures sentry-cli is different than the one you include in your application resources to configure the Sentry SDK at runtime (as seen in the configuration documentation).

You need to have another sentry.properties file in the project root with

defaults.project=your-project
defaults.org=your-org
auth.token=YOUR_AUTH_TOKEN

and the runtime sentry.properties with DSN values, etc can be placed in app/src/main/resources directory(create resource directory if required)

Config Docs

Answer 4

instead of making

minifyEnabled false

Just add these rules to proguard rules file and keep minifyEnabled true

#sentry
-keepattributes LineNumberTable,SourceFile
-dontwarn org.slf4j.**
-dontwarn javax.**
-keep class io.sentry.event.Event { *; }

That solved my issue without disabling minification

Answer 5

You need to upload the Proguard mapping file to the sentry server.

create a file in the root project folder and set name sentry.properties.

defaults.url=https://sentry.io
defaults.org=TEST
defaults.project=TEST_DEV
auth.token=TOKEN

replace TEST, TEST_DEV, and TOKEN.

you can get TOKEN from https://sentry.io/api

if you are use custom sentry server, replace https://sentry.io to your server adddress.

and change file build.gradle

buildscript {
    
    dependencies {

        classpath 'com.android.tools.build:gradle:3.5.2'
        
        classpath 'io.sentry:sentry-android-gradle-plugin:1.7.27'

    }
}

and

apply plugin: 'com.android.application'
apply plugin: 'io.sentry.android.gradle'

...

sentry {
  autoProguardConfig true
  autoUpload true
}
    
android {
  ...
}
dependencies {

     ...

     implementation 'io.sentry:sentry-android:1.7.27'
     implementation 'org.slf4j:slf4j-nop:1.7.25'

     ...
}

Answer 6

For ReactNative/iOS, if you have such errors check that you put sentry.properties file in iOS folder

Answer 7

I also stranded here whilst trying to figure what was going wrong with my sentry source map uploads (not on android, but for web with a similar error). To debug my events that weren't matched, I was using the sentry-cli like so;

So I was searching how I could add the organization slug to my source map uploads. But this error wasn't about the event, but for using the explain CLI functionality itself!!! Which confused me.

I had to pass additional parameters to the CLI script to get the actual problem with the event;

Maybe this will help someone else who also skipped over the docs