-
Notifications
You must be signed in to change notification settings - Fork 753
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
Update errors are not reported anymore in CheckForUpdateEvent event #365
Comments
How you intend to handle the case when args is null? How it can be useful? |
As it is in your example: Earlier args was null when there was an error. |
Yes, I get that part but I removed it cause it wasn't giving any error info besides setting args to null. Can you tell me what you intend to do in the if (args != null) block of your event? |
It is almost the same as in your example:
The difference is in the args==null... i don't want to show any messagebox, just log the problem. |
Yes, that it is true.. this is why I wrote:
Since now it is not possible to detect the problem. Earlier at least it was called with null. |
@zgabi Thanks for the explanation. I understand you want to log the error. I'll see what I can do about it. |
Before 2020.01.11 the
CheckForUpdateEvent
was called when there was an error with downloading the update xml with args==null.In this commit it was changed: 32e01a7
Now it is only called when Error is null and not possible to handle the error manually. The only options is just to show or not to show an error dialog.
We'd like to do different error handling without showing the error dialog.
The "Handling updates manually" section also shows an example for that:
I agree not to call this event handler in case of error, but please add another error event. (Or restore the previous behavior.)
The text was updated successfully, but these errors were encountered: