-
Notifications
You must be signed in to change notification settings - Fork 34
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
background update check failed, stack trace shown #637
Comments
I see same crash reports. |
@myuseraccount Thanks for the detailed error report. I think this is a logic error on my side. The "background update check" notification is only shown, if the "Simple network test was not successful" failed for 5 times in a row. (with 30s waiting time between the first and second try, 60s between 2nd and 3rd, 120s ...) ("Simple network test was not successful" = a HTTP head request to e.g. https://api.github.com failed) I guess it is quite normal to have no internet/network for 30min. Maybe you also uses the airplane mode? |
@Tobi823 Solution: skip AppUpdater.kt when simple network test failed, because a failed HTTP head request is a good indicator for no internet |
Just got a slightly different crash. Stacktrace:
Logs:
Device information:
|
Important first questions
FFUpdater up-to-date: 79.2.5, F-Droid build
similar issues: 582 and 626, both closed
Describe the bug
I get notifications titled "background update failed" with a stack trace
To Reproduce
Not predictable. But I don't allow battery optimization exemption (unrestricted background) for ffupdater, and I leave data saver on. Update checks on metered networks is on, but not downloads.
Expected behavior
Ffupdater should tolerate data being turned off or restricted through intentional means in the OS.
Error message from FFUpdater
Stacktrace:
Logs:
Device information:
The text was updated successfully, but these errors were encountered: