Closed antonis closed 4 weeks ago
Issues
0 New issues
0 Accepted issues
Measures
0 Security Hotspots
No data about Coverage
0.0% Duplication on New Code
App Name | Jetpack | |
Flavor | Jalapeno | |
Build Type | Debug | |
Version | pr20636-f9674c5 | |
Commit | f9674c504af65b0de855c53626a63d5fabc78b57 | |
Direct Download | jetpack-prototype-build-pr20636-f9674c5.apk |
App Name | WordPress | |
Flavor | Jalapeno | |
Build Type | Debug | |
Version | pr20636-f9674c5 | |
Commit | f9674c504af65b0de855c53626a63d5fabc78b57 | |
Direct Download | wordpress-prototype-build-pr20636-f9674c5.apk |
Attention: Patch coverage is 0%
with 4 lines
in your changes are missing coverage. Please review.
Project coverage is 40.46%. Comparing base (
0384227
) to head (f9674c5
). Report is 6 commits behind head on release/24.7.
Files | Patch % | Lines |
---|---|---|
.../reader/services/comment/ReaderCommentService.java | 0.00% | 4 Missing :warning: |
:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.
I've changed the target to 24.7
since this came up in the release rotation (ref pcdRpT-6oc-p2#comment-9821) and the code changes should not have side effects.
This pull request was deployed and Sentry observed the following issues:
org.wordpress.android.ui.reader.services.commen...
View Issueorg.wordpress.android.ui.reader.services.commen...
View IssueDid you find this useful? React with a 👍 or 👎
Fixes #18666
Description
This PR prevents the app from crashing when the ReaderCommentService for comment snippet fails to start with a
BackgroundServiceStartNotAllowedException
/IllegalStateException
and logs the caught exception.Note that a wider refactoring is needed to tackle the root of this issue (see https://github.com/wordpress-mobile/WordPress-Android/issues/18666#issuecomment-1690415225) but given that it is the 3rd crash in number of events/users for the last (
24.5
) version of the app, handling the crash sounds reasonable.To Test:
I was not able to reproduce this crash thus I'd recommend a sanity of the functionality:
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):