-
-
Notifications
You must be signed in to change notification settings - Fork 42
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Seamlessupdate does not handle force stop then restart gracefully #16
Comments
Interesting, not sure why this would happen. |
It looks like it's update_engine that screwed up though? Unless it did successfully apply the update and the only issue was the UI not showing a notification. |
I think what you suggested was the case. The progress bar hung and I had to check logcat to do the reboot manually. |
I think perhaps force stopping Updater didn't stop the update, so it succeeded anyway, but the app wasn't running? |
It definitely lacks a way to contact update engine and pick up where it left off. |
It now uses a foreground service tied to the progress notification for downloading + verifying + installing so issues like this should be far less frequent without the user triggering it. It still won't handle this well when it's triggered via force stop. |
Sometimes when seamlessupdate hangs, a user might want to force stop the service and restart it by pressing on "check updates", but this fails silently without a UI prompt for reboot and seamlessupdate will refuse to restart until reboot.
Logcat Logs:
The text was updated successfully, but these errors were encountered: