Closed zwarm 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 | WordPress | |
Flavor | Jalapeno | |
Build Type | Debug | |
Version | pr20654-f980e0d | |
Commit | f980e0dd4f6b685a8fe0c09cb248b7276ce90473 | |
Direct Download | wordpress-prototype-build-pr20654-f980e0d.apk |
App Name | Jetpack | |
Flavor | Jalapeno | |
Build Type | Debug | |
Version | pr20654-f980e0d | |
Commit | f980e0dd4f6b685a8fe0c09cb248b7276ce90473 | |
Direct Download | jetpack-prototype-build-pr20654-f980e0d.apk |
All modified and coverable lines are covered by tests :white_check_mark:
Project coverage is 40.13%. Comparing base (
6ef913e
) to head (f980e0d
). Report is 25 commits behind head on trunk.
:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.
Fixes #20653
This PR addresses the potential for an IllegalStateException that can occur when updating from a background thread in the clearMenuStep(). The issue was due to invoking setValue() on _quickStartMenuStep directly, which throws an illegalStateException when called from the mainthread.
To resolve this issue, the clearMenuStep() function has been updated to use postValue() instead of setValue(). This ensures that the update to _quickStartMenuStep happens asynchronously on the main thread, preventing threading issues and IllegalStateExceptions.
To Test:
I was unable to recreate the crash, so the test validates all still works correctly.
Regression Notes
Potential unintended areas of impact Quick start tutorial doesn't work as normal
What I did to test those areas of impact (or what existing automated tests I relied on) Manual tests and unit tests
What automated tests I added (or what prevented me from doing so) N/A
PR Submission Checklist:
RELEASE-NOTES.txt
if necessary.Testing Checklist (strike-out the not-applying and unnecessary ones): N/A