![]() ![]() Apple has the concept of legacy contacts - see How to add a Legacy Contact for your Apple ID - but I’m not sure how it intersects with the developer programme. That it can be passed-off to others when I stop, one way or another.Ĭan the developer account or certificate credentials be transferred to I'm old and have setup this Open Source project and web site so All code that you ship to users must be signed in order to pass Gatekeeper.ģ. For a updater: Should both the main application and separate You might be able to build and ship a Mac product with 10.9-era tools, but it’d be a serious challenge.Ģ. Ten years ago the new hotness was macOS 10.9. Could you use ten-year-old tools to build and ship a Mac product today? Probably not. While I can’t predict the future, I find it informative to look at the past. Things are less strict for directly distributed Mac products but, even there, there are ongoing requirements like the notarisation stuff I mentioned above. Right now, for example, iOS apps must be built with Xcode 14.1, which is only about a year old. We expect developers to use reasonably up-to-date tools. The story for developer tools is very different. Sometimes that breaks - for example, back in macOS 10.15 we stopped supporting 32-bit apps - but, in general, binary compatibility goes back a long way. It sounds like you’re talking about customer support, and that’s a very different issue from the developer tools we’re discussing here.Īt a user level, macOS works hard to maintain binary compatibility for very old apps. I’m not sure what you mean by “end-of-support in December 2023”. that will work on the latest MacOS - after the end-of-support in.Xcode 13 runs on macOS 11, so I think you’ll be OK. Apple recently dropped support for our old notarisation infrastructure, which means that you must use Xcode 13 or later to notarise (well, in your case that’s the notarytool that’s bundled in said Xcode). IMPORTANT To pass Gatekeeper you must notarise your product. ![]() I’m not aware of any significant change since macOS 11, but something might have slipped my mind. macOS 11 is relatively old and Apple does change our code signing infrastructure from time to time. However, your real question is whether you’ll be able to sign code and disk images that are accepted by Gatekeeper, and that’s trickier to answer. Macbook Pro still be able to sign DMG files If I sign-up as an Apple Developer and pay the fee will this 2013 Guidance for a noob would be appreciated. Can the developer account or certificate credentials be transferred to someone else at that time? I'm old and have setup this Open Source project and web site so that it can be passed-off to others when I stop, one way or another. If I sign-up as an Apple Developer and pay the fee will this 2013 Macbook Pro still be able to sign DMG files - that will work on the latest MacOS - after the end-of-support in December 2023?įor a updater: Should both the main application and separate updater both be signed? The basic process is: Download updater into system temp folder, prepare and execute updater, stop desktop application, updater downloads new version, prepares and copies update to installed location, then restarts desktop application and ends the updater. It's been adapted to the MacOS look 'n feel. Deliberately supporting older systems due to the nature of this data management and back-up application. Very new to Apple, but a retired 48-year engineer trying to support MacOS for the first time.īuilding with Ant and appbundler task,, then creating a DMG with DMG Canvas. Have had a Macbook Pro 13" Late 2013 Retina running Big Sur 11.7.10 for 3 weeks. The self-contained application runs on Linux and Windows - now I'm trying to figure-out Mac. Have been working on a Java Open Source project for 8 years with the last 2+ years on a cross-platform desktop GUI for it with a separate updater.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |