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
Inaccurate notifications #41
Comments
Greetings 👋🏻
Which configurations did you enable? If it only happens for specific websites, then which website specific configurations did you apply? If possible, could you share the websites this issue comes up with? Does it always happen the same way or does it vary?
Which is why I really need more information on your issue, to be able to reproduce it, as I do not experience it with the data I have.
|
Thank you for responding. I will attempt to answer all your questions to the best of my ability. I have 5 different websites I monitor (some on different hosting). I am using default settings in the Webmon app. I prefer not to share the websites at this time, as some are personal, and some are work for hire. "Does it always happen the same way or does it vary?": If I have answered anything not to your satisfaction, please clarify and I will attempt to provide better information if I am able to. Thank you again for your time to address this issue report. |
Interesting. This helps a lot. Could you turn on the feature, which ignores failure due to a missing internet connection, rather than the website being down? Was "saying one, some, or all of the websites were unreachable" just an example or does it vary?
Does that mean you issue a manual refresh or just look at the list of websites?
Are some of them on a development server, which has low performance? It would also help, if you provided more information about your phone. Do you use a custom ROM? The default one? Do you have power saving apps installed? As a side note: The app seems to be running in the background, since you are retrieving notifications, though I still want to point out that stock Samsung phones are extremely aggressive in regards to "power saving". It wouldn't surprise me at all, if there were internet connection issues on a stock Samsung phone. |
"Could you turn on the feature, which ignores failure due to a missing internet connection, rather than the website being down? Okay, I will try that and let you know the results. "Was "saying one, some, or all of the websites were unreachable" just an example or does it vary? That part does vary. "Does that mean you issue a manual refresh or just look at the list of websites?" Either shows the same result of all websites up. "Are some of them on a development server, which has low performance? None are on development servers. They are on GoDaddy hosting, and DirectNic hosting. "Do you use a custom ROM? The default one?" I use stock rom that came with the phone. "Either way, it would help if you posted information about the OS." Model: SM-S111DL "Do you have power saving apps installed?" Webmon is added to the "Apps that won't be put to sleep" list. |
Seems like this might be an issue. Still, I'll check it out and will try to reproduce the issue in various ways. I'll get back to this issue, when I get results. |
How did that go? |
I haven't had any notifications at all since changing settings, even when the websites are down. |
If that is the case, that means that the problem was always related to bad internet connectivity on your phone. Once you disable the feature, which ignores errors due to internet connectivity, the notifications should appear again, because your phone has issues staying connected with the internet. |
Did you receive notifications again, after disabling the feature? |
No feedback & cannot reproduce. |
Using F-Droid version 2.8.0 of Webmon,
on a Samsung Android 10 mobile phone.
I am experiencing inaccurate notifications which state that there was an issue with the website(s), but upon clicking the notification, the app itself shows no issues. This has been happening with previous versions as well.
I found a reference that someone else has reported this issue, but the issue report is now marked as closed:
#3
Please consider looking into this issue again, if you would. Thank you for your time.
The text was updated successfully, but these errors were encountered: