Skip to content

docs(cli): Explain how to add ProGuard UUID to Android SDK #4771

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.

Sign up for GitHub

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

Merged
merged 1 commit into from
Feb 28, 2022
Merged

docs(cli): Explain how to add ProGuard UUID to Android SDK #4771

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
11 changes: 9 additions & 2 deletions src/docs/product/cli/dif.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -273,15 +273,22 @@ sentry-cli upload-proguard \
```

Since the Android SDK needs to know the UUID of the mapping file, you need
to associate it with the upload. If you supply
`--uuid`, it sets that value:
to associate it with the upload. If you supply `--uuid`, it sets that value:

```bash
sentry-cli upload-proguard \
--uuid A_VALID_UUID \
app/build/outputs/mapping/{BuildVariant}/mapping.txt
```

Which then also needs to be included in your `AndroidManifest.xml` file:

```xml
<application>
<meta-data android:name="io.sentry.proguard-uuid" android:value="A_VALID_UUID" />
</application>
```

After the upload, Sentry deobfuscates future events. If you want to send an obfuscated crash to Sentry to verify the correct operation, ensure that the ProGuard mapping files are listed in _Project Settings > ProGuard_.

### Upload Options
Expand Down