![]() I've successfully signed it using codesign with a "Developer ID Application" certificate.Ĭodesign -s "Developer ID Application: MY_CERIFICICATE_NAME" -v -deep -timestamp -entitlements ist -o runtime "dist/MyApp.app" -force I've built a working MacOS app from python, using Tkinter as GUI, and pyinstaller to build. My question is – what is the most straightforward process to get my app released for internal use? Is it possible to release the app without a sandbox or even code signing? I completely understand the requirements for security here but I am just trying to build an internal tool that will be used by a handful of people. This is when I hit that wall of bureaucracy and complexity that is code signing, sandboxing, entitlements, etc. Swift is a nice language and the dev process was very smooth until I had to release the app so my colleagues can use it. I set to build an internal tool and most of my colleagues are OSX users so I thought why not give Swift and SwiftUI a shot? The program is fairly simple, it lays audio back to video files leveraging FFmpeg. Hi there and thanks for the help in advance.īefore I ask my question let me give you some background I am reasonably new to swift and the OSX dev ecosystem so apologies for my ignorance in my post below. So, how can I sign my app without breaking it? I don't know if this libffi is central to the problem or just the first thing to fail. projects/eagle_eyes_video_scanner/dist/EagleEyesScan.app/Contents/MacOS/mai projects/eagle_eyes_video_scanner/dist/EagleEyesScan.app/Contents/MacOS/main Termination Reason: Namespace ROSETTA, Code 0 ![]() After signing with the same command I used for the arm64 version:Ĭodesign -s "Developer ID Application: MY_CERTIFICATE_NAME" -v -deep -timestamp -entitlements ist -o runtime "dist/MyAppName.app" -forceĮntitlements file just sets .allow-unsigned-executable-memory to true - apparently necessary for python programs. I've built a conda environment for x86_64, built the app with pyinstaller, and verified that it runs when I double-click on AppName.app. Now I am trying to do the same for x86_64, on the same machine. I have already built, signed, and notarized the app successfully on the native arm64 architecture - so far so good. Is there a way to copy MyProg.app out of the enlocing DMG and keep the notarisation without resorting to command line? Dropping down to command line is not a problem for me, but it is for quite a few of my users - not everybody is comfortable with command line, and debugging what they did wrong sometimes turns out to be quite a futile undertaking.Ĭontext : I'm developing a python app with Tkinter GUI on a 2020 M1 Macbook Air. If I copy MyProg.app from the DMG container into another directory by "cp -R" or "ditto" instead of D&D or C&P in Finder, everything works as it should and the notarisation is not broken. MyProg.app: a sealed resource is missing or invalid Spctl -ignore-cache -assess -vvvv MyProg.appĪfter I copy MyProg.app out of the DMG using FInder gives This is my first post here, I hope I am not asking what is considered to be common knowledge.Īfter a long and very frustrating day, I have found out why copying out my (correctly signed and notarised) MyProg.app from the (correctly signed and notarised) enclosing DMG breaks it ("Is damaged and can't be opened"): it seems that D&D or C&P from Finder does something to destroy the notarisation.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |