Fix: Fix DeadObjectException inside AutoUpdateServiceConnection - #11
Merged
Aghajari merged 4 commits intoOct 6, 2025
Merged
Conversation
Member
|
Just to confirm, have you tested these changes? Maybe by manually throwing a DeadObjectException before the changes? |
Author
|
Yup! It worked in that way in the sample app. |
Member
|
Thanks for the PR @behnawwm |
This file contains hidden or 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
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.
This PR tries to resolve the
DeadObjectExceptioncrash on some devicesThe issue may come across two reasons:
So the issue could be calling
service.isAutoUpdateEnabled()inside a coroutine onDispatchers.IO, possibly seconds afteronServiceConnected()returns.That’s fine in principle, but if:
the binder proxy becomes invalid → DeadObjectException.