Repository navigation
Replies: 3 comments 2 replies
|
Hi, maybe it is an internet slowdown that would cause wrong checksum detection. Have you tried to re-update? |
1 reply
|
@vishnu350 We should find a solution for these false positives. |
0 replies
|
Hi @ivan-hc, @LiTeFlame. It is a random network downtime problem, Github's uptime is just terrible at the moment. Almost everyone is complaining about it. There is not much we can do about this. Fortunately the checksum feature came along just in time for us to be able to deal with this issue. Else we will just be using half downloaded appimages and not even know it. Do not use the app if the checksum is mismatching. It is a broken download. |
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment

Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Hi! I've been getting checksum mismatch warnings quite often lately after running
appman -u, and I'm wondering if this is a known issue or something on my end.Today, four apps triggered the warning:
I manually verified one of them (zapzap-enhanced) and the hashes genuinely don't match:
Expected: 7fe7ba88549bbfc0b8ed28d406bb1f89c9f1966e157c1f1a6baa04a064ba250e
Got: 67d7734c6d48957183b6d58fb7081a2bcda48fb89fb0e3113913de2f996b7a8a
The apps seem to be working fine, so I'm not sure if this is an upstream issue (digest files not being updated alongside new releases) or something else entirely.
Has anyone experienced the same recently? Any idea what might be causing this?
System info:
All reactions