Skip to content

Commit ff89442

Browse files
docs(cli): Remove Proguard release association mention
We are removing the association between ProGuard files and releases. The association is already no longer visible in Sentry, and the CLI arguments to specify an associated release will be deprecated in the next version of Sentry CLI.
1 parent 528250c commit ff89442

File tree

1 file changed

+0
-18
lines changed

1 file changed

+0
-18
lines changed

docs/cli/dif.mdx

Lines changed: 0 additions & 18 deletions
Original file line numberDiff line numberDiff line change
@@ -226,24 +226,6 @@ sentry-cli upload-proguard \
226226
app/build/outputs/mapping/{BuildVariant}/mapping.txt
227227
```
228228

229-
Additionally, you can associate the ProGuard mapping file to a specific release:
230-
231-
<Alert>
232-
233-
This step is not required for deobfuscation to work but can help you identify which release a mapping file belongs to when multiple files exist for the same app.
234-
235-
</Alert>
236-
237-
```bash {5-7}
238-
# Associate the mapping file to the release [email protected]+1
239-
sentry-cli upload-proguard \
240-
--uuid A_VALID_UUID \
241-
app/build/outputs/mapping/{BuildVariant}/mapping.txt \
242-
--app-id my.app.id \
243-
--version 1.0.0 \
244-
--version-code 1
245-
```
246-
247229
After the upload, Sentry deobfuscates future events.
248230
To make sure that it worked, you can check _Project Settings > ProGuard_ and see if the upload mapping files are listed.
249231

0 commit comments

Comments
 (0)