Closed carlosperate closed 1 year ago
Okay, so I've traced this down to the pyzmq
wheel. As the Mu build is run in CI runner with macOS 10.15 x86 the wheel pip fetches when invoked from pup is for the macosx_10_15_universal2
platform:
2022-11-14T12:08:07.3947990Z 20221114 120807 I pup.plugins.pip_install pip out: Collecting pyzmq>=17.1
2022-11-14T12:08:07.4066640Z 20221114 120807 I pup.plugins.pip_install pip out: Using cached pyzmq-24.0.1-cp38-cp38-macosx_10_15_universal2.whl (1.8 MB)
Looking at the current pup output (like this one) pyzmq
is the only non-compatible wheel, but this is only by chance, as there is no reason any of the other dependencies might not have the same issue in the future.
We might need to add a --platform
flag to the pip download
command from pup for building macOS 10.12+ installers, to avoid fetching newer wheels.
Created this pup issue as a feature request:
And draft PR here to test it:
I can confirm the generated macOS installer works in 10.12. To download it go this link and click on the highlighted installer (you need to be logged in GitHub for the link to work): https://github.com/mu-editor/mu/actions/runs/3688654382
Okay, I've merged PR https://github.com/mu-editor/mu/pull/2371 which will have fixed this issue for the next Mu release, thanks everyone for the report and the testing!
Double clicking on the .app bundle doesn't do anything, no visible crash and no crash reporter.
Using the
open
command in the terminal prints this error:And executing the launcher directly:
In comparison 1.1.1 had an issue with the user venv dependencies not being compatible, but the application launched and the crash reporter captured it.