Size Analysis
Upload React Native iOS and Android builds to Sentry for size analysis.
Size Analysis is currently in Early Access. To access, turn on Early Adopter in your settings.
Size Analysis helps monitor your mobile app's size in pre-production to prevent unexpected size increases (regressions) from reaching users. Aside from being courteous to your users, a smaller app size helps boost installation and retention rates, especially for customers with limited storage or slower connections.
Size Analysis is most effective when part of your CI pipeline. To set up, follow our guide on integrating into CI.
Accepted Upload Formats: XCArchive (preferred) | IPA
Upload Mechanisms: Sentry CLI
Install the sentry-cli (version
2.58.3)We recommend using the latest version for the best possible experience, but at a minimum version
2.58.2is required.Authenticate the Sentry CLI by following these steps
Build your app to create an XCArchive (preferred) or IPA
Invoke the following CLI command to trigger the upload:
Copiedsentry-cli build upload app.xcarchive \ --org your-org \ --project your-project \ --build-configuration ReleaseAfter an upload has successfully processed, confirm the metadata is correct in the Sentry UI
Size Analysis is most effective when part of your CI pipeline. To set up, follow our guide on integrating into CI.
Accepted Upload Formats: AAB (preferred) | APK
Upload Mechanisms: Sentry CLI | Gradle
Install the sentry-cli (version
2.58.3)We recommend using the latest version for the best possible experience, but at a minimum version
2.58.2is required.Authenticate the Sentry CLI by following these steps
Build your app to create an AAB (preferred) or APK
Invoke the following CLI command to trigger the upload:
Copiedsentry-cli build upload app.aab \ --org your-org \ --project your-project \ --build-configuration ReleaseAfter an upload has successfully processed, confirm the metadata is correct in the Sentry UI
The Gradle plugin automatically detects build metadata from your git repository. On GitHub Actions, all metadata is automatically detected. On other CI systems, you may need to manually set some values using the vcsInfo extension.
- Configure the Sentry Android Gradle plugin with at least version
6.0.0-beta1 Set the auth token as an environment variable to be used when running your release build.
Copiedexport SENTRY_AUTH_TOKEN=___ORG_AUTH_TOKEN___
Enable uploading for size analysis for CI builds.
build.gradle.ktsCopiedsentry { sizeAnalysis { enabled = providers.environmentVariable("GITHUB_ACTIONS").isPresent } }
Invoke the following Gradle tasks to build your app and trigger the upload.
aabCopied./gradlew bundleRelease
After an upload has successfully processed, confirm the metadata is correct in the Sentry UI

Overriding Metadata
The Gradle plugin automatically detects build metadata from your git repository. On GitHub Actions, all metadata is automatically detected. On other CI systems, you may need to manually set some values using the vcsInfo extension.
Configure overrides in your Gradle build configuration:
build.gradle.ktssentry { sizeAnalysis { enabled = providers.environmentVariable("GITHUB_ACTIONS").isPresent } vcsInfo { headSha.set("abc123") baseSha.set("def456") vcsProvider.set("github") headRepoName.set("organization/repository") baseRepoName.set("organization/repository") headRef.set("feature-branch") baseRef.set("main") prNumber.set(42) } }
Available vcsInfo properties:
| Property | Type | Description |
|---|---|---|
headSha | String | Current commit SHA |
baseSha | String | Base commit SHA (for comparison) |
vcsProvider | String | VCS provider (e.g., "github") |
headRepoName | String | Repository name (org/repo format) |
baseRepoName | String | Base repository name |
headRef | String | Branch or tag name |
baseRef | String | Base branch name |
prNumber | Int | Pull request number |
We use build metadata to organize builds in the UI and ensure correct comparisons.
| Field | Description |
|---|---|
org* | Sentry organization slug |
project* | Sentry project slug |
build-configuration* | Build configuration describing how the app was built, for example Release or Debug or Release-Bazel |
head-sha | Current commit SHA |
base-sha | Base commit SHA (for comparisons, recommended to use the branch's merge-base) |
head-repo-name | Repository name (org/repo) |
pr-number | Pull request number |
head-ref | Branch or tag name |
base-ref | Base branch name |
* required field
Build configuration metadata keeps comparisons scoped to like-for-like builds. The Android Gradle plugin sends the build variant (for example, freeDebug or paidRelease). On iOS, set this to your Xcode build configuration, such as Debug, Staging, or Release.
Our documentation is open source and available on GitHub. Your contributions are welcome, whether fixing a typo (drat!) or suggesting an update ("yeah, this would be better").