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

Auto-update fails when Calendr kept at ~/Applications #264

Closed
PuzzledUser opened this issue Oct 17, 2024 · 4 comments
Closed

Auto-update fails when Calendr kept at ~/Applications #264

PuzzledUser opened this issue Oct 17, 2024 · 4 comments
Labels
bug Something isn't working
Milestone

Comments

@PuzzledUser
Copy link

PuzzledUser commented Oct 17, 2024

I keep all third party apps in an Applications folder in my Home folder. This seems to traumatise your update script (irrespective of what I say to your grant permissions prompt — change nothing and select /Applications, or change to ~/Applications).

EDIT: I was on v1.13.3. Mac OS 14.6.1

@pakerwreah
Copy link
Owner

The update code will abort if you change the path, because it won't have permission to delete the old app.

No matter what you do, it will try to delete from /Applications and will fail because your app is on ~/Applications.

Previously I was just getting the location of your currently running app, but if you move it around, sometimes macOS gatekeeper will put it into quarantine and give me a random path like /Volumes/random-number/Calendr.app, which breaks the entire update process.

I will try to improve this in two ways:

  1. Only fallback to /Applications if the system gives me a "corrupted" path. This will open the save panel in the correct place for you, if nothing goes wrong.
  2. Always try to use the path that you selected. That way if the system messes up you can always select the correct location.

@pakerwreah pakerwreah added the bug Something isn't working label Oct 17, 2024
@pakerwreah pakerwreah added this to the v1.14.1 milestone Oct 17, 2024
@PuzzledUser
Copy link
Author

Thanks. I guess release for 1.14.1 will appear in due course (automatically 😉)...

@pakerwreah
Copy link
Owner

Yeah, but it will still use the old updater, so you will have to do this one manually.

@PuzzledUser
Copy link
Author

Tested. Works perfectly for me.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants