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
{{ message }}
Repository navigation
Commit c44fa03
Browse filesBrowse the repository at this point in the historyBrowse files
build(samples): Move the Android sample to its own build
The Android sample is now a standalone Gradle build that includes the SDK
build. It depends on io.sentry:* coordinates, which Gradle substitutes with
the SDK's projects, so there is nothing to publish first. The SDK build
doesn't include it back, so the sample's plugins (KSP, SQLDelight, Room,
CameraX) no longer load in the SDK build.
The macrobenchmark moves into the sample's build, because AGP requires a
benchmark and the app it targets to be in the same build.
Root check and spotlessApply no longer reach the sample, so preMerge runs
the sample build's check, and the format workflow runs its spotlessApply.
That check covers what the root check ran for it: lint, unit tests,
SQLDelight migrations and spotless.
Run it with ./gradlew -p sentry-samples/sentry-samples-android <task>.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@@ -110,7 +113,7 @@ The repository is organized into multiple modules:
110
113
111
114
### Utility Modules
112
115
-**`sentry-test-support`** - Shared test utilities, including `MockSentryServer` and envelope matchers
113
-
-**`sentry-samples`** - Example applications
116
+
-**`sentry-samples`** - Example applications. `sentry-samples-android` is a separate Gradle build that includes this one, so root tasks such as `check` and `spotlessApply` don't reach it
114
117
-**`sentry-bom`** - Bill of Materials for dependency management
or simply open the project in Android Studio and run the `sentry-samples-android` configuration.
14
+
or open the `sentry-samples/sentry-samples-android` directory in Android Studio and run the `sentry-samples-android` configuration.
15
+
16
+
The sample is a separate Gradle build that includes the SDK build, so changes to the SDK show up in the next build of the sample, with nothing to publish first.
17
+
The SDK build doesn't include the sample, so `./gradlew` from the repository root doesn't build, lint or format it.
15
18
16
19
You can also apply the [Sentry Android Gradle Plugin](https://github.com/getsentry/sentry-android-gradle-plugin) (SAGP) when building (not applied by default):
0 commit comments