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

App Updater won't load on Apple "M" computer #3

Open
martyknapp opened this issue Apr 27, 2023 · 4 comments · May be fixed by #4
Open

App Updater won't load on Apple "M" computer #3

martyknapp opened this issue Apr 27, 2023 · 4 comments · May be fixed by #4

Comments

@martyknapp
Copy link

I built an app (FAT) for the "M" chip Macs but the app updater helper will not load. If I set the app to open using Rosetta it opens fine. I did replace "Sparkle.framework" in this helper with the latest version from Sparkle and it seems to work but not sure if anything needs to be updated elsewhere.

@trevordevore
Copy link
Owner

@martyknapp As long as the API calls that https://github.com/trevordevore/levurehelper-app_updater/blob/master/sparkle.lcb uses haven't changed then I think that is all you need to do. At least I'm not aware of anything else. Would you be up for submitting a PR with the update to Sparkle?

@martyknapp
Copy link
Author

martyknapp commented Apr 28, 2023 via email

@trevordevore trevordevore linked a pull request Sep 14, 2023 that will close this issue
@trevordevore
Copy link
Owner

@martyknapp You can try downloading the code in the PR I just linked to this. I updated to Sparkle 1.27 which has universal support. If you had updated to version 2 of Sparkle in your test that may have caused problems. I'm not sure if the API is exactly the same. If you get a chance to try this out let me know how it goes. I haven't tested it yet.

@martyknapp
Copy link
Author

martyknapp commented Sep 14, 2023 via email

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

Successfully merging a pull request may close this issue.

2 participants