Closed fhemberger closed 10 years ago
It used to be a problem, but I believe Asepsis is silent since v1.3.1 (October 11, 2013).
I have just tested v1.4 on my 10.9.3 system (without network connection) and it does not raise the dialog after restart.
It still is an issue with 1.4, I get the "Update failed" dialog about once a week when I'm working in an environment, where port 80 is blocked for Asepsis (though a network connection in general might exist at the time). This doesn't happen directly after a restart (I don't shut down my machine, just sending it to sleep), I mostly get it a while after I woke up my machine again.
Please reopen the ticket.
EDIT: I just updated to 1.4.1, I'll check if the issue still exists in the updated version.
I just got this again, network connection is available, but port 80 is blocked for Asepsis in this environment:
@darwin Any chances you can look into this issue anytime soon? The popup window is a bit annoying. ;)
This has really low priority for me. I believe this fix must go into Sparkle library which is not code I'm familiar with.
As a workaround, you can uninstall the updater completely and maybe remember to update manually when doing system upgrade (Yosemite):
asepsisctl uninstall_updater
I think this is the code which has to be revisited: https://github.com/binaryage/sparkle/blob/master/SUUpdater.m#L231-L278
Unfortunately I have no experience with SCNetworkReachability stuff.
Hmm, can't you just log failed updates instead of showing the dialog? For now, I'll remove the updater, as you advised.
Is there anyway to remove the notification as well? It pops up like every hour. Or at least an option to disable automatic update checking would be nice.
@dustindowell22 Create an empty file ~/.asepsis-suppress-update-errors
, that should do the trick.
@fhemberger Nice. Thanks.
I use Little Snitch to maintain several network configurations. One of the firewall rules is to block software updates via http on untrusted networks.
Other Mac applications fail silently when no network connection for updating could be established, but the Asepsis updater always shows an error message instead. It would be great if the behavior could be altered to match the general behavior of Mac applications and suppress the error (or make it at least configurable).