Actions
Feature #2912
closed
Updater handles unsigned updates poorly when used on beta/snapshot releases
Status:
Resolved
Priority:
Low
Assignee:
-
Category:
-
Target version:
-
Start date:
03/27/2013
Due date:
% Done:
0%
Estimated time:
Plus Target Version:
Release Notes:
Description
Running 2.1 beta, and notified of an available snapshot update, the updater attempts to download the update but only afterwards advises it can't do anything anyway, because it's not signed.
The user can fix this by allowing unsigned updates, but if that's needed for beta versions, the code should 'know' or detect it's unsigned, before downloading it all, not download it all then fail.
Improve or warn user of the possible need to flip this setting?
Updated by 
Updated by
Actions