Why can't AppImageUpdate update itself when prompted by the user?

[RagglenLove]

As you can see from the screenshot, AppImageUpdate isn't signed and so cannot be updated.

Why is this?

For being able to update the updater is a good idea for security reasons, users should be able to update it when updates are available.

[TheAssassin]

It did get updated. It just warns about the missing signature, that's all. The update was successful.

This should be communicated more clearly, I guess.

[RagglenLove]

Thanks for the clarification!

[TheAssassin]

Let's keep this open as a reminder.

[RagglenLove]

This should be communicated more clearly, I guess.

It would be nice if this is how it looked to avoid confusion:

[axelsimon]

Using the word "problem" will inherently make users think that whatever action they were trying to do failed.

A yellow line also indicates the thing failed.

Someone with UI/UX/design experience needs to look at this to better convey the right information, because right now the application tells you the update failed.

[Drugoy]

Let's keep this open as a reminder.

@TheAssassin In the current state the ticket is basically about changing the GUI to better convey to the user that the updated succeeded, it's just that the new file was not signed and thus is a dupe of #173.
If you think that this ticket is about signing the AppImageUpdate itself - well, then it's a dupe of #158.

[TheAssassin]

True. Let's close this issue then.