Skip to content

docs(android): Clarify manual init guidance #19297

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
0xadam-brown merged 1 commit into from
Sep 12, 2026
+2 −3
Merged

docs(android): Clarify manual init guidance #19297

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 2 additions & 3 deletions docs/platforms/android/manual-setup/index.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -80,7 +80,7 @@ Configuration is done via the application `AndroidManifest.xml`. Here's an examp
<meta-data android:name="io.sentry.session-replay.on-error-sample-rate" android:value="1.0" />
<meta-data android:name="io.sentry.session-replay.session-sample-rate" android:value="0.1" />

<!-- If your application has strict PII requirements we recommend using the Canvas screenshot strategy.
<!-- If your application has strict PII requirements we recommend using the Canvas screenshot strategy.
See the Android Session Replay documentation for details: https://docs.sentry.io/platforms/android/session-replay/#screenshot-strategy -->
<!-- <meta-data android:name="io.sentry.session-replay.screenshot-strategy" android:value="canvas" /> -->

Expand Down Expand Up @@ -124,7 +124,7 @@ Or, to completely remove the merging of the `ContentProvider`:

The next step is to initialize the SDK directly in your code.

The SDK can catch errors and crashes only after you've initialized it. For that reason, we recommend calling `SentryAndroid.init` in your Application class as soon as the application is created. If you don't already have a custom Application class, [check out the official docs on how to create one](https://developer.android.com/reference/android/app/Application).
The SDK can catch errors and crashes only after you've initialized it. For that reason, we recommend calling `SentryAndroid.init` once in your Application class as soon as the application is created. Avoid calling it from `Activity.onCreate()` or other activity lifecycle methods. If you don't already have a custom Application class, [check out the official docs on how to create one](https://developer.android.com/reference/android/app/Application).

Configuration options will be loaded from the manifest so that you don't need to have the static properties in your code. In the `init` method, you can provide a callback that will modify the configuration and also register new options.

Expand Down Expand Up @@ -243,4 +243,3 @@ public class MyApplication extends Application {
```

Additional options can be found <PlatformLink to="/configuration/options/">on our dedicated options page</PlatformLink>.

Loading