-
Notifications
You must be signed in to change notification settings - Fork 518
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
spurious offline alerts #4139
Comments
I've since completely uninstalled LuLu and am still seeing this at about the same frequency. I'll try to find some time to fire up NNW from source in Xcode and see if I can provide more info. |
What type of account(s) are you using in NetNewsWire? |
Just iCloud, On My Mac is disabled. |
This error message is surfaced by CloudKit. It just means that for what ever reason, a sync was attempted, but iCloud couldn't be reached. I have seen this message while the network appeared to be up, so I'm not sure what all the failure points are that could cause it. Because all the network connections to sync using CloudKit are handled by the framework, I'm don't know what NNW could do to avoid this error. |
Huh, interesting. I should clarify that I don’t see it sporadically in the sense that it is up when I turn to the app, but only when I manually refresh, which prevents me from refreshing at the time. Which is what makes it look like a NNW issue! But I understand the iCloud opaqueness.
|
First off, I'm not 100% sure that this isn't related to me recently installing a Mac-wide internet filter in the form of LuLu, but I've tried its disabling feature as well as verified that NNW has unfettered access to hosts and ports, yet I still see this from time to time.
Everything else is online at the time. I'm not sure if anyone else is seeing this, so I thought it worth reporting. Version 6.1.4.
There is also a third possibility, that having a system-wide filter is interfering with something in NNW in an unintended way regardless of the way that the filtering app is written or operating.
The text was updated successfully, but these errors were encountered: