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
Testing background Notifications. #47
Comments
I will test this again in the week |
Same, I haven't looked into this yet but will try to see if I can reproduce the issue at some point. |
Today I did launch the app, and left it in the background. Set to 3h update interval. I got one notification late in the day saying: Error checking for updates could not find suitable release. I opened that now and it just launched the app. Then I filtered apps and saw, two updates available for simple clock and file manager. |
Today I haven't launched the app and got the same notification about 30 min ago. From Github I can tell the same two app updates are available as well as NeoStore. |
Just got the same notification 3 hours later, which makes sense since my update interval is 3 hours. Not sure what the notification means but at least I know that so long as I'm always connected, obtanium is working in the background. Opened the app with the notification but noticed it still only showed updates available for simple file manager and clock, when there is in fact an update available for NeoStore. So I opened Neostore on Obtanium and then only did it register the update. |
Could not find suitable release means that Obtainium couldn't find an APK for one or more of your Apps. This could be due to the dev not attaching an APK to the latest release, or it could be that your filter settings (prerelease, regular expression, etc.) are the problem. When this happened, update checking used to stop, so all subsequent Apps would not be checked. I'm hoping this is what you faced; one App errored out (hence the notification you got) and the rest were never checked (hence no notification for them). This should be improved in the latest release (see issue #58) but still not fixed as I just realized that the fix for that issue would still result in no notification on error. Will make a change in the next release and that will hopefully resolve this issue. |
Okay, everything should be fine with the latest release: https://github.com/ImranR98/Obtainium/releases/tag/v0.5.10-beta |
Also note that background checking only notifies you of newly discovered updates; if an App already says "Update Available" in Obtainium, you won't get a notification for it again (this avoids repetitive reminder notifications for the same App every X hours). |
Okay, all good to know. It is probably the brave repo messing with my phone, as I know all the repos I've added to Obtanium have apks. Brave just has that weird release tagging. Anyway I will keep testing, don't close this issue yet. |
😗ooo I just got a successful notification to install updates for simple file manager. Variables: 3 hour update interval on latest Obtanium version. Outside variables: I didn't have internet connection for much of the morning but I have had connection for around 5 hours before this notification. The release was for simple file manager which is a 2day old release. Once opening the notification and filtering updates, I saw that there was also an update for brave browser. |
Yesterday I was in and out of internet connection (mostly out) and got no notifications, whilst I know there are updates. This morning I turned on the phone and connected, got a notification I've not seen before: 'Checking for updates' Okay the notification just changed to 'Updates available xxx app and 2 more apps have updates' |
Just got another successful update notification for an update that released 2 hours ago. 🙌 Hour by hour updates here 😋 |
And another successful notification for a new update 3 hours later. |
That "checking" notification is only supposed to show for a few seconds 💀 And yeah, if you don't have a connection, Obtainium will wait for it. But if you do have a connection and lose it in the middle of an update check, Obtainium won't try again until the next interval (as far as the scheduler is concerned, once update checking has started, the job is done, regardless of whether it passes/fails). This could be fixed but it seems uncommon enough that I'm not sure it's worth it (most of the time, you just need a few seconds of internet access for an update check to complete successfully). Anyways, I'm glad things seem to be working, hopefully they will continue to work as you keep testing. |
Cool cool. |
See some new feedback in Issue #60 |
Seems to be fixed on Alpha version |
App variables:
What happened:
I did not launch obtanium after reboots to test whether background update notifications would work.
After 3 days I never got notifications. Whilst I knew there were updates because of Octodroid.
Outside variables:
After launching and changing app update interval to 1 hour I did get update notifications. But not for all my apps it seemed.
The text was updated successfully, but these errors were encountered: