You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: src/collections/_documentation/platforms/android/index.md
+2-63Lines changed: 2 additions & 63 deletions
Original file line number
Diff line number
Diff line change
@@ -242,69 +242,8 @@ sentry {
242
242
}
243
243
```
244
244
245
-
### Manual Integration
246
-
247
-
If you choose not to use the Gradle integration, you may handle the processing and upload steps manually. However, we highly recommend that you use the Gradle integration, if at all possible.
248
-
249
-
### ProGuard UUIDs
250
-
251
-
After ProGuard files generate, you will need to embed the UUIDs of the ProGuard mapping files in a properties file named `sentry-debug-meta.properties` in the assets folder. The Java SDK will look for the UUIDs there to link events to the correct mapping files on the server-side.
252
-
253
-
Sentry calculates UUIDs for ProGuard files. For more information about how this works, see [ProGuard UUIDs]({%- link _documentation/workflow/debug-files.md -%}#proguard-uuids).
254
-
255
-
`sentry-cli` can write the `sentry-debug-meta.properties` file for you:
This file needs to be in your APK, so **run the script before the APK is packaged**. You can do that by creating a Gradle task that runs before the dex packaging.
266
-
267
-
You can, for example, add a Gradle task after the ProGuard step and before the dex packaging. The dex packaging executes `sentry-cli` to validate, process the mapping files, and write the UUIDs into the properties file:
Alternatively, you can generate a UUID upfront yourself and then force Sentry to honor that UUID after upload. However, this is **strongly discouraged**.
298
-
299
-
### Uploading ProGuard Files
300
-
301
-
Finally, manually upload the ProGuard files with `sentry-cli` as follows:
0 commit comments