Closed valynor closed 4 months ago
@valynor I don't have an Apple Silicon Mac so I can't build native binaries for ARM. You can still compile it yourself natively though.
For Windows, I don't think ARM64 adoption will be very fast, it'll take at least 5 years imo for ARM64 to overtake x86. Even then, WoA has x64 emulation built in, so just providing a standard x64 binary will suffice for now.
Feel free to reopen if you have any additional comments :)
Hello and thanks for your work on the project :) GitHub actions now has runners for ARM64 macOS, would it be possible to use that to publish an ARM64 build?
Never used runners, and even if I did, I wouldn't be able to test it.
I'm spinning up a Scaleway M1 Mac so hopefully I can compile it from here, but if not, so be it.
@valynor @ZingyAwesome Good news, native binaries coming soon! Gonna put them here and I need you guys to help me test. Expect something from me in two hours.
@valynor @ZingyAwesome Please confirm that this native ARM .app runs on your systems :) Picocrypt-arm64.zip
Can anyone confirm that the arm64 binary works on Apple Silicon?
I can't run damaged file error. tested on m3 pro
Can anyone confirm that the arm64 binary works on Apple Silicon?
Doesn't work for me. Tested on M1 Pro.
"Picocrypt is damaged and can’t be opened. You should eject the disk image."
I am also getting the picocrypt is damaged error.
Workaround: open up a terminal and enter:
xattr -d com.apple.quarantine /Applications/Picocrypt.app
It runs normally after this. Tested some basic encryption and decryption and that seems to work.
This error is due to some Apple code signing/notarization thing and has happened with other software with macOS ARM builds (e.g. webcord), nothing to do with the app I believe.
@ZingyAwesome I encountered the same issue (working fine on x86 but on ARM it is "damaged"), so I recall doing xattr -c Picocrypt.app
. Looking up xattr, -c clears attributes, -d deletes, so I guess both our commands accomplish the same thing. Do you know which is "better"? If so, I should probably add one of these two commands to the README.
@dsm @ANiceCupOfTea Can you guys confirm whether xattr -c Picocrypt.app
solves the issue?
xattr -c
clears ALL extended attributes which isn't needed. There may be side effects to that but I'm not sure.
We only need to remove the com.apple.quarantine
attribute which is the one that prevents the app from being started, so I prefer xattr -d com.apple.quarantine <app>
.
Perfect, I was looking for some info like that. I'll add a note to the README shortly.
@HACKERALERT Thanks a lot for making this available so quickly. 🙏
Closing, feel free to reopen if running the xattr command doesn't work.
@valynor @ZingyAwesome @dsm @ANiceCupOfTea
New automated builds via GitHub Actions for macOS arm64! Need help testing though. Can someone confirm this works? Ping me if it works.
https://github.com/Picocrypt/Picocrypt/actions/runs/9622314576/artifacts/1626906959
@HACKERALERT
The app works, usual workaround using xattr
is required.
Slight oddity of there being a nested zip (i.e. Picocrypt.zip is inside build-macos.zip), that is all.
Thank you for your work :)
Yeah, its because .apps are folders and artifacts can only be files..it's a small slight inconvenience but now macOS builds are always native and up to date without my manual work ;)
Please consider making available a macOS ARM64 version of Picocrypt as a direct download. The times of Intel Macs are over since 2020. :)
Windows for ARM64 will probably be a popular thing very soon, too.