Open zorrobyte opened 1 month ago
This is the output I get when I run the Apple developer tool "codesign" on the Spatial Metadata GUI application:
codesign -dv --verbose=4 "/Applications/Spatial Metadata GUI/Spatial Metadata GUI.app"
Executable=/Applications/Spatial Metadata GUI/Spatial Metadata GUI.app/Contents/MacOS/Spatial Metadata GUI
Identifier=com.spatialmetadata.gui
Format=app bundle with Mach-O universal (x86_64 arm64)
CodeDirectory v=20400 size=49147 flags=0x0(none) hashes=1529+3 location=embedded
VersionPlatform=1
VersionMin=720896
VersionSDK=721152
Hash type=sha256 size=32
CandidateCDHash sha1=ca894fcc2705da536cdc3e71405cba23fb3efcb6
CandidateCDHashFull sha1=ca894fcc2705da536cdc3e71405cba23fb3efcb6
CandidateCDHash sha256=c63bd1abd6b69bedf322a54345783883e292bd08
CandidateCDHashFull sha256=c63bd1abd6b69bedf322a54345783883e292bd08d7606fc6b2c3979e605ded79
Hash choices=sha1,sha256
CMSDigest=c5b77af12406e94854f81def75211ffa0772dc5cd1b53c51870af12b4ac5c214
CMSDigestType=2
Executable Segment base=0
Executable Segment limit=4505600
Executable Segment flags=0x1
Page size=4096
CDHash=c63bd1abd6b69bedf322a54345783883e292bd08
Signature size=4872
Authority=Apple Development: Andrew Hazelden (9GSMW7S76Y)
Authority=Apple Worldwide Developer Relations Certification Authority
Authority=Apple Root CA
Signed Time=Jul 17, 2024 at 3:54:18 AM
Info.plist entries=17
TeamIdentifier=858GCVQRJ9
Sealed Resources version=2 rules=13 files=7
Internal requirements count=1 size=188
FWIW, I'm currently running macOS Sonoma 14.4.1 here. I will try to explore further what changes are needed with the code signing process but I did actually register for a Apple Dev account, got the signing key, and did enter it under the Xojo build settings.
TBH I haven't done the one way upgrade on any of my gear to macOS 15 beta yet. I've heard BMD Resolve Studio v19 has issues on macOS 15 at the moment where an activation key based license fails to remember the authentication. So that issue with Resolve/Fusion would break the main tool I use my system with. 😬
No worries thanks for checking it out! If it’s working properly on non-beta macOS, then I wouldn’t worry about it for now.I should try to compile it myself as well just to see if compiled on v15 makes a difference. Could easily be an Apple bugOn Jul 18, 2024, at 2:13 PM, Andrew Hazelden @.***> wrote: FWIW, I'm currently running macOS Sonoma 14.4.1 here. I will try to explore further what changes are needed with the code signing process but I did actually register for a Apple Dev account, got the signing key, and did enter it under the Xojo build settings. TBH I haven't done the one way upgrade on any of my gear to macOS 15 beta yet. I've heard BMD Resolve Studio v19 has issues on macOS 15 at the moment where the activation key based licensed don't remember the authentication so that would break the main tool I use my system with. 😬
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you authored the thread.Message ID: @.***>
@zorrobyte It's been a few years since I released compiled software on macOS and had to deal with executable/library code signing for something I created.
It was quite literally 2017/2018 when I last did this process on an open-source fulldome/VR toolset called Domemaster3D. Since that point I've been solidly doing scripting in LuaJIT/Python.
If there is any tips/suggestions you work out from testing Xojo Lite on macOS 15 beta with code signing, please do share them here, or if you want you can email me andrew@andrewhazelden.com.
I really do want to make the installation process as seamless and low friction as possible. If I can do things better I do want to do that.👌
Apple has taken away/made it very difficult to run apps without a developer signature in macOS 15![image](https://github.com/user-attachments/assets/c62e6f6a-5f7b-40b3-9027-021faa0c88a4)
Users must go to Privacy & Security after launching it once and tapping Allow under Security, then launching again and entering their password
It may be worth adding instructions on how to bypass, or recompiling with a dev signature https://documentation.xojo.com/topics/application_deployment/apple_requirements/signing_your_mac_application.html