Skip to content

docs(android): Document Gradle 8.14.2+ requirement for Sentry Android Gradle Plugin 6.x#17620

Open
InterstellarStella wants to merge 1 commit intomasterfrom
interstellarstella/docs/document-sagp-6x-gradle-requirement
Open

docs(android): Document Gradle 8.14.2+ requirement for Sentry Android Gradle Plugin 6.x#17620
InterstellarStella wants to merge 1 commit intomasterfrom
interstellarstella/docs/document-sagp-6x-gradle-requirement

Conversation

@InterstellarStella
Copy link
Copy Markdown
Contributor

@InterstellarStella InterstellarStella commented May 5, 2026

Summary

The sentry-android-gradle-plugin 6.x line is built against Gradle 8.14.2 and requires Gradle 8.14.2+ at runtime, but this is currently not surfaced in user-facing docs. Customers upgrading to @sentry/react-native v8 (which bundles SAGP 6.x) on Gradle 8.10.x hit a confusing java.lang.NoSuchMethodError: 'org.gradle.api.tasks.Exec org.gradle.api.tasks.Exec.setIgnoreExitValue(boolean)' at task registration. Disabling uploadNativeSymbols masks the error temporarily but doesn't fix the underlying ABI mismatch, so users have been chasing the wrong fix.

These doc changes were made at the request of a customer who hit this exact issue while upgrading to Sentry React Native v8 on a brownfield Android app. Support ticket: https://app.intercom.com/a/inbox/onh0p2wm/inbox/admin/9850682/conversation/215474146376271?view=List

What's in this PR

  • New migration guide page for SAGP 5.x → 6.0 (the migration directory previously had no entry for this version jump).
  • New troubleshooting entry on the Android troubleshooting page with the literal stack trace and the exact gradlew wrapper fix.
  • Cross-referenced troubleshooting entry on the React Native troubleshooting page.
  • Added the missing Gradle: 8.14.2+ bullet (with a warning Alert) to the React Native v7 → v8 migration guide's Android section.
  • Added a warning Alert to the main Gradle configuration page calling out the minimum runtime Gradle version for plugin 6.x.

Test plan

  • `pnpm dev` and confirm the new and modified pages render correctly.
  • Confirm the anchor link `#nosuchmethoderror-during-gradle-configuration-with-sentry-android-gradle-plugin-6x` resolves from both the React Native troubleshooting page and the React Native v7-to-v8 migration page.
  • Verify the new SAGP v5-to-v6 migration page appears in the Android migration sidebar above the v3-to-v4 entry.
  • `pnpm lint` passes.

Background

The only workaround the customer initially found was disabling `uploadNativeSymbols` and `includeNativeSources`, which obscured the actual root cause. Adding an explicit minimum-version guard inside the plugin itself (so Gradle fails fast with an actionable message) is being tracked separately in the sentry-android-gradle-plugin repo; this PR is just the documentation half.

The Sentry Android Gradle Plugin 6.x is built against Gradle 8.14.2 and
requires Gradle 8.14.2+ at runtime, but this requirement was not surfaced
anywhere in user-facing docs. Customers upgrading to @sentry/react-native
v8 (which bundles SAGP 6.x) on Gradle 8.10.x hit a confusing
java.lang.NoSuchMethodError on Exec.setIgnoreExitValue at task
registration. Disabling uploadNativeSymbols masks the error temporarily
but doesn't fix the underlying ABI mismatch, so users have been chasing
the wrong fix.

This change documents the requirement and the failure mode in five places
so it's discoverable from each angle a user might land on:

- New SAGP v5-to-v6 migration page (the migration directory previously
  had no entry for this version jump).
- New troubleshooting entry on the Android troubleshooting page with
  the literal stack trace and the exact gradlew wrapper fix.
- Cross-referenced troubleshooting entry on the React Native
  troubleshooting page.
- Added the missing Gradle 8.14.2+ bullet (with a warning Alert) to the
  React Native v7-to-v8 migration guide's Android section.
- Added a warning Alert to the main Gradle configuration page calling
  out the minimum runtime Gradle version for plugin 6.x.

Co-Authored-By: Claude <noreply@anthropic.com>
Co-authored-by: Cursor <cursoragent@cursor.com>
@vercel
Copy link
Copy Markdown

vercel Bot commented May 5, 2026

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
sentry-docs Ready Ready Preview, Comment May 5, 2026 2:13pm
1 Skipped Deployment
Project Deployment Actions Updated (UTC)
develop-docs Ignored Ignored May 5, 2026 2:13pm

Request Review

Copy link
Copy Markdown
Member

@romtsn romtsn left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@InterstellarStella this doesn't sound right -- ignoreExitValue has existed since version 1.0 of Gradle, so it's definitely not a new API. Also, we compile against version 8.9.0 in the gradle plugin and not 8.14.2.

Could you please share more details on the issue/share a link to support ticket? This needs further investigation

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants