Guard mutex unlock in isLocked check to avoid errors during local data uploads #17472
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.


Fixes #17463
The goal of this fix is to prevent possible data loss while their content is uploaded to the server.
While we weren't able to reproduce the crash we noticed it occurs for some users when they start the app, if their internet connectivity is active and there are local changes to be synced to the server.
This fix is applied to to prevent possible
IllegalStateExceptions when the mutex is already unlocked by the system during a cancellation / completion while the mutex locking function is suspended.To test:
Nothing much to test here, verify CI checks are green.
Regression Notes
Potential unintended areas of impact
N/a
What I did to test those areas of impact (or what existing automated tests I relied on)
N/a
What automated tests I added (or what prevented me from doing so)
N/a
PR submission checklist:
RELEASE-NOTES.txtif necessary.