Closed sebdanielsson closed 10 months ago
Have you verified the new build on apple silicon? I have only old Intel based MacBook.
I've tested to start the build created from this PR and macOS starts it as a native application without using Rosetta.
However I wasn't able to test the functionality since both this build and the previous build from the PR before mine result in this error when flashing the USB flash drive. Error: @rpath/QtDBus.framework/Versions/A/QtDBus
Does https://github.com/FedoraQt/MediaWriter/pull/666 make any difference?
Does #666 make any difference?
Hmm, it does, but the error shifts to QtCore instead.
Alright, I fixed the issue. Can you please rebase? By that I mean to include the same change I just merged in your job?
Hmm, that's strange. I rebased your fixes on top of my commits and added:
"$Qt6_DIR"/bin/macdeployqt build/src/app/FedoraMediaWriter.app -qmldir=src/app/qml -executable=build/src/app/FedoraMediaWriter.app/Contents/MacOS/helper -appstore-compliant
to the macos-arm64 build but now macOS won't open the app because it's damaged.
Hmm, that's strange. I rebased your fixes on top of my commits and added:
"$Qt6_DIR"/bin/macdeployqt build/src/app/FedoraMediaWriter.app -qmldir=src/app/qml -executable=build/src/app/FedoraMediaWriter.app/Contents/MacOS/helper -appstore-compliant
to the macos-arm64 build but now macOS won't open the app because it's damaged.
I don't think that any change I did could damage the build/bundle somehow, it just added yet another binary to work with in the macdeployqt
to fix the libraries and paths, but nothing really fundamental. Does the non-arm64 build work for you? Or both builds are now broken? It at least worked for me yesterday.
Hmm, that's strange. I rebased your fixes on top of my commits and added:
"$Qt6_DIR"/bin/macdeployqt build/src/app/FedoraMediaWriter.app -qmldir=src/app/qml -executable=build/src/app/FedoraMediaWriter.app/Contents/MacOS/helper -appstore-compliant
to the macos-arm64 build but now macOS won't open the app because it's damaged.
I don't think that any change I did could damage the build/bundle somehow, it just added yet another binary to work with in the
macdeployqt
to fix the libraries and paths, but nothing really fundamental. Does the non-arm64 build work for you? Or both builds are now broken? It at least worked for me yesterday.
The x86_64 version still works just like before, only the arm64 version is reported as broken.
That's weird. Any chance you can run it in a terminal to get some logs why it reports it's broken? Or it doesn't even mount?
Starting the app from the terminal doesn't give me any output. I started the macOS Console.app and started the app and got lots of output. Here's the output filtered by MediaWriter
:
This line stands out to me. I tried to disable Gatekeeper, but still got the same error.
default 10:21:02.243864+0100 kernel ASP: Security policy would not allow process: 16036, /Applications/FedoraMediaWriter.app/Contents/MacOS/FedoraMediaWriter
Whoa!
Actually disabling Gatekeeper and re-enabling it did the trick. It's flashing my USB stick now!
Update: USB stick is flashed and everything is working fine!
sudo spctl --master-disable
spctl --status
sudo spctl --master-enable
spctl --status
Thank you!
One difference I noticed for builds using the new CI system is that the new app filename doesn't contain spaces. Is this intentional? Many users will probably end up with two versions if it's not the same.
Thank you!
One difference I noticed for builds using the new CI system is that the new app filename doesn't contain spaces. Is this intentional? Many users will probably end up with two versions if it's not the same.
Yes, I changed it to simplify it and avoid potential issues when I omit to escape spaces or things like that in the build script. I don't think we have that many users or that many users who keep using FMW frequently on MacOS so hopefully it won't be a big deal.
Current universal build doesn't work. I added another job to build a separate macOS arm64 version. Having them separated also reduces the size of the application.
Closes #380