Closed antonis closed 1 month ago
App Name | Jetpack | |
Flavor | Jalapeno | |
Build Type | Debug | |
Version | pr20533-fb90630 | |
Commit | fb90630f67e9a98b7bece9d542796fb430b809a1 | |
Direct Download | jetpack-prototype-build-pr20533-fb90630.apk |
App Name | WordPress | |
Flavor | Jalapeno | |
Build Type | Debug | |
Version | pr20533-fb90630 | |
Commit | fb90630f67e9a98b7bece9d542796fb430b809a1 | |
Direct Download | wordpress-prototype-build-pr20533-fb90630.apk |
Attention: Patch coverage is 22.22222%
with 7 lines
in your changes are missing coverage. Please review.
Project coverage is 40.24%. Comparing base (
7ff5847
) to head (fb90630
).
Files | Patch % | Lines |
---|---|---|
...ndroid/util/crashlogging/WebviewVersionProvider.kt | 0.00% | 7 Missing :warning: |
:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.
Hey @wzieba 👋 I've added you as a reviewer on this PR since you might have a better understanding of the crash logging implementation in https://github.com/Automattic/Automattic-Tracks-Android. If you have the time any feedback is more than welcome 🙇
Thank you for the prompt review and feedback @wzieba 🙇
Issues
0 New issues
0 Accepted issues
Measures
0 Security Hotspots
No data about Coverage
0.0% Duplication on New Code
Description
This PR adds the Webview version in Sentry crash logging to better monitor issues like https://github.com/wordpress-mobile/WordPress-Android/issues/20147
Notes
I initially considered adding the version in the extras https://github.com/wordpress-mobile/WordPress-Android/pull/20533/commits/4ba20a721dec802fc7b34a97b77d7d9e7a942e09. This worked (example) but additional data are not searchable/filterable making the added data less valuable. I switched to using a tag by using the
applicationContextProvider
that exposes it's data as tags. Another alternative would be to add a new dedicated field in the CrashLoggingDataProvider. Since this might not be valuable for other apps and to keep the enhancement simpler I didn't choose this path.To Test:
webview.version
tag (example)Regression Notes
Potential unintended areas of impact
What I did to test those areas of impact (or what existing automated tests I relied on)
What automated tests I added (or what prevented me from doing so)
PR Submission Checklist:
RELEASE-NOTES.txt
if necessary.Testing Checklist (strike-out the not-applying and unnecessary ones):