This situation does not only affect Livecode, but all development tools. Even Xcode. To get your programs trusted by macOS you need to sign and notarize. There is little that can be done about it.
We can either accept it or stop developing for macOS. Of course it would be great if the standalone building process would include the option to code sign and notarize right after building the standalone. Or if at least the Livecode Ide would have a plugin that would allow us to do the whole process directly from Livecode. But currently we have to do it manual. I am not sure if you tried already my Notarize Helper Stack, which does all needed steps for code signing and notarizing. The stack is far from being perfect and everyone is welcomed to optimize it, but at least it works. You just have to enter some information (Developer ID, passwords and other information) once. After that you can use it to code sign and notarize your Livecode standalones. I did not try it under macOS12 so far, but did not hear about any problems about it yet. You can find it here in the lesson about code signing and noterizing https://lessons.livecode.com/m/4071/l/1122100-codesigning-and-notarizing-your-lc-standalone-for-distribution-outside-the-mac-appstore > Am 26.01.2022 um 21:39 schrieb Keith Martin <thatke...@mac.com>: > > f only it was easier to do. 😢 > I've actually stopped using LC much because the process of making apps that > people can run without fuss has become ridiculous. I'm still hoping for a > solution that isn't so aggressively hostile! The current situation feels like > a direct threat to LiveCode the company, as it must be putting off more than > a few people from becoming or staying customers. > _______________________________________________ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
