Retry sync on DeadObjectException #503
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
sunkup
changed the title
ArnyminerZ
approved these changes
Feb 13, 2025
ArnyminerZ
deleted the
495-periodic-sync-sometimes-fails-silently-with-deadobjectexception
branch
Doesn't fix the issue for me. |
Can you try to install DAVx⁵ please, set it up with any CalDAV server and sync a calendar? Does the scheduled background sync work in this environment? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Purpose
The DeadObjectException at sync may occur when the remote process dies, or (since Android 14) when IPC (for instance with the calendar provider) is suddenly forbidden because our sync process was demoted from a "service process" to a "cached process". DAVx5 seems to have had the same problem and simply retries the sync.
Short description
Checklist