AppImageCommunity
*.zsync exist but not found by AppImageUpdate
The URL - https://github.com/probonopd/OpenBoard/releases
Details as text:
Fetching latest release information from GitHub API
GitHub API request failed!
Could not find any artifacts in release data. Please contact the author of the AppImage and tell them the files are missing on the releases page.
ZSync URL not available. See previous messages for details.
It is well possible that I have screwed up with that application. Let me check...
Looks like new URL https://github.com/OpenBoard-org/OpenBoard/releases does not have AppImage anymore....
Well, it looks like the are not offering AppImages at all? Please chime in at https://github.com/OpenBoard-org/OpenBoard/issues/147 in case you would see a proper AppImage. That test repository of mine should then go away asap.
@TheAssassin maybe the error message text should print the update information there for easier remote debugging?
user@FreeBSD$ ./OpenBoard-4fca3a6-x86_64.AppImage --appimage-updateinformation
gh-releases-zsync|probonopd|OpenBoard|latest|OpenBoard*-x86_64.AppImage.zsync
@edmundlaugasson are you still getting the error now? I deleted one of two versions that wrongly were uploaded.
@edmundlaugasson are you still getting the error now? I deleted one of two versions that wrongly were uploaded.
Yes. But as it is outdated version anyway, then we need to use newest version, which doesn't have AppImage version currently.
@probonopd appimageupdatetool provides the -d flag which provides all the information you could possibly want.
I can confirm this issue still exists with the latest (as of December 29th, 2020, 1f52c72 continuous build) version of appimageupdatetool:
$ ./appimageupdatetool-x86_64.AppImage -d ./appimageupdatetool-x86_64.AppImage
Fetching release information for tag "continuous" from GitHub API.
GitHub API request failed!
Could not find any artifacts in release data. Please contact the author of the AppImage and tell them the files are missing on the releases page.
Parsing file: ./appimageupdatetool-x86_64.AppImage
AppImage type: 2
Raw update information: gh-releases-zsync|AppImage|AppImageUpdate|continuous|appimageupdatetool-*x86_64.AppImage.zsync
Update information type: ZSync via GitHub Releases
I am assuming it is possible for appimageupdatetool to be able to update itself with the zsync information. It doesn't seem capable of doing so, presumably due to the same issue the OP has raised.
Works fine here:
> ./appimageupdatetool-x86_64.AppImage -d appimageupdatetool-x86_64.AppImage
Fetching release information for tag "continuous" from GitHub API.
Parsing file: appimageupdatetool-x86_64.AppImage
AppImage type: 2
Raw update information: gh-releases-zsync|AppImage|AppImageUpdate|continuous|appimageupdatetool-*x86_64.AppImage.zsync
Update information type: ZSync via GitHub Releases
Assembled ZSync URL: https://github.com/AppImage/AppImageUpdate/releases/download/continuous/appimageupdatetool-x86_64.AppImage.zsync
> ./appimageupdatetool-x86_64.AppImage appimageupdatetool-x86_64.AppImage
Checking for updates...
Fetching release information for tag "continuous" from GitHub API.
... done!
Update not required, exiting.
Your call to the GitHub API failed. You might be IP blocked.
Is there some way for the logs to output more detailed information for that API lookup? I somehow doubt my IP is blocked. I also checked at a remote server just now (residential Spectrum internet here in the USA), I don't think both IPs would be banned by Github. Furthermore, I can do SSH push/pull using my credentials just fine (although maybe that is not related to an API blacklist)...
I'm referring to anonymous GitHub API usage, which is what AppImageUpdate uses internally.
Right, as I said before, is there some way to confirm whether the API lookup failed due to an IP block or the app? The logs output from the app were not helpful in that regard.
I face the same problem, the tool doesn't work in WSL (version 2, if it matters). The API isn't blocked because I can successfully fetch the headers (and the data) using curl:
curl -I https://api.github.com/repos/neovim/neovim/releases/tags/nightly
HTTP/2 200
date: Sun, 31 Jan 2021 12:50:02 GMT
content-type: application/json; charset=utf-8
server: GitHub.com
status: 200 OK
cache-control: public, max-age=60, s-maxage=60
vary: Accept, Accept-Encoding, Accept, X-Requested-With, Accept-Encoding
etag: W/"d56925761f0c43dc64be8acbed75152b97258240f1f862caa7805a6256d7c235"
last-modified: Thu, 01 Jan 1970 00:00:00 GMT
x-github-media-type: github.v3; format=json
access-control-expose-headers: ETag, Link, Location, Retry-After, X-GitHub-OTP, X-RateLimit-Limit, X-RateLimit-Remaining, X-RateLimit-Used, X-RateLimit-Reset, X-OAuth-Scopes, X-Accepted-OAuth-Scopes, X-Poll-Interval, X-GitHub-Media-Type, Deprecation, Sunset
access-control-allow-origin: *
strict-transport-security: max-age=31536000; includeSubdomains; preload
x-frame-options: deny
x-content-type-options: nosniff
x-xss-protection: 1; mode=block
referrer-policy: origin-when-cross-origin, strict-origin-when-cross-origin
content-security-policy: default-src 'none'
x-ratelimit-limit: 60
x-ratelimit-remaining: 45
x-ratelimit-reset: 1612100061
x-ratelimit-used: 15
accept-ranges: bytes
content-length: 13807
x-github-request-id: 88DA:1AA8:5016199:588F1EF:6016A77A
Hello, I am having the same problem with all the AppImages I have which support updates. When I try to launch an update I get this error
./AppImageupdatetool-x86_64.AppImage -d zsync2-12-486fc9a-x86_64.AppImage
Fetching release information for tag "continuous" from GitHub API.
GitHub API request failed!
Could not find any artifacts in release data. Please contact the author of the AppImage and tell them the files are missing on the releases page.
Parsing file: zsync2-12-486fc9a-x86_64.AppImage
AppImage type: 2
Raw update information: gh-releases-zsync|AppImage|zsync2|continuous|zsync2-*x86_64.AppImage.zsync
Update information type: ZSync via GitHub Releases
Failed to assemble ZSync URL. AppImageUpdate can not be used with this AppImage.%
I get this issue, GitHub API request failed!, with the provided release binaries.
Self building works. Fedora 33.
