Skip to content
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 check fails in v1.7.0 #24

Open
porg opened this issue Jan 12, 2024 · 4 comments
Open

Update check fails in v1.7.0 #24

porg opened this issue Jan 12, 2024 · 4 comments

Comments

@porg
Copy link

porg commented Jan 12, 2024

v1.7.0 contacts via HTTP to:

http://quantum-technologies.iap.uni-bonn.de/alberti/iTunesVolumeControl/VolumeControlCast.xml.php?version=1.7.0&osxversion=Version%2011.7.10%20(Build%2020G1427)

which fails with: 404 - Component not found.

Proposal: Correct the server side handling so that elder clients also get the convenient auto update.

  • If too much effort, never mind.
  • Then users of elder versions need to manually update.

Good news for the current version 1.7.4

I went to the Github homepage README.md and downloaded the newest ZIP, then got v1.7.4 and then the update mechanism works again.

@porg
Copy link
Author

porg commented Jan 12, 2024

  • In v1.7.4 the update server is raw.githubusercontent.com and it already uses HTTPS (443).
  • So yes I think a redirection on the legacy server to raw.githubusercontent.com makes no sense as likely the whole update procedure in the 1.7.0 app is not compatible with the newer one.

@porg
Copy link
Author

porg commented Jan 12, 2024

TL;DR:

  • In Volume-Control 1.7.4 (or slightly earlier) the updating check server and protocol was changed.
  • If you use Volume-Control 1.7.0 (or slightly newer, or older) then automatic updating will fail.
  • Please go to https://github.com/alberti42/Volume-Control/ and download the newest release from there.

@alberti42
Copy link
Owner

alberti42 commented Jan 12, 2024 via email

@porg
Copy link
Author

porg commented Jan 12, 2024

  • Thanks for official confirmation.
  • Am hereby closing this issue as "wontfix" but "documented/outlined with a solution".

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants