docs: Update Android WebView guidance for connected traces
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- Half a day
- Newbie friendliness
- 76/100
- Issue type
- Documentation
- Clarity
- Clearly specified
- Activity status
- Active
- Tech stack
- android, javascript
- Domain
- documentation, mobile-dev, web-dev
Research direction
Start by reading the current Android WebView page at docs.sentry.io/platforms/android/configuration/webview/ and compare the related Apple and React Native WebView guidance. Update the page to cover document-start meta-tag injection via evaluateJavascript, host allow-listing, the @sentry/browser requirement, and the entry-pageload limitation. Done means the guidance matches the distributed-tracing continuation contract and is consistent across platforms.
Written by the indexing model from the issue text.
Description
Outcome
Replace the current Android WebView guidance — which states the SDK "doesn't interact with the mobile application's web views" — with setup for the new trace-connection support.
Acceptance criteria
- Documents how to inject the native trace context into a WebView (meta tags at document-start via
evaluateJavascript), the host allow-list option, the requirement that the in-WebView page run@sentry/browser, and the entry-pageload scope limitation. - Wording coordinated with the Apple and React Native WebView doc updates for cross-platform consistency.
References
- Meta-tag continuation contract the page should point to: https://docs.sentry.io/platforms/javascript/tracing/distributed-tracing/
- Current Android WebView page to replace: https://docs.sentry.io/platforms/android/configuration/webview/
- Cross-platform parity: RN docs issue (getsentry/sentry-react-native#6782), Apple docs issue
- Dominant language
- Kotlin
- Stars
- 1.4k
- Forks
- 478
- Avg merge
- 2d 12h
- Merged PRs (30d)
- 60
Getting set up
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from getsentry/sentry-java
-
Bug Java Platform: Android Platform: Java
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
getsentry/sentry-java#6138 · 1 comment ·
Maintainers usually reply within 1 day
-
Feature Java Platform: Java Spans
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
getsentry/sentry-java#5984 · 1 comment ·
Maintainers usually reply within 1 day
-
Android Task Traces
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
getsentry/sentry-java#5376 · 1 comment ·
Maintainers usually reply within 1 day
-
Android Docs Errors
Difficulty 2/5 1-3 hours Newbie friendliness 64/100
getsentry/sentry-java#5375 · 1 comment ·
Maintainers usually reply within 1 day
-
Android good first issue Task User Feedbacks
Difficulty 1/5 1-3 hours Newbie friendliness 68/100
getsentry/sentry-java#5354 · 1 comment ·
Maintainers usually reply within 1 day
All issues in getsentry/sentry-java
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
-
bug webview
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
home-assistant/android#7524 ·
Maintainers usually reply within 1 day
-
Issue: Bug
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
OpenAPITools/openapi-generator#25021 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
software-mansion/enriched-markdown#897 ·
Maintainers usually reply within 1 day
-
documentation
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
detekt/detekt#9761 · 1 comment · 2 reactions ·
Maintainers usually reply within 1 day