zsign

> A temporary cert only able to be created on another Apple system You don’t need an Apple system to codesign. Two results on first page of search results: https://github.com/zhlynn/zsign https://weisser-zwerg.dev/posts/ios-app-without-mac/ > make the process as unpleasant as possible but just so enough that Apple can claim they don't block sideloading Apple doesn’t claim they don’t block side-loading. Actually I believe they claim the opposite in the Epic case (even though it is possible via a supported process) because it was “necessary to ensure the safety of their user base” or something like that. > It's disingenuous Shifting goal posts from “you can’t” to “you can’t without X” once someone points out the first was factually incorrect is considered disingenuous by many too. (Edit for formatting and provide links)

Apple added requirements for their store to publish extensions, yes. They also added more privacy prompts. If you don’t test on MacOS in Safari, how would you know if your extension works correctly? Why not ask Apple to release macOS for any computer like Windows on x86? Why not ask for Safari to be published for and API compatible with Windows as on macOS? Why not ask Apple to ship Windows since mac-only APIs would be problematic? Fact is, Apple requiring a Mac to publish for a Mac-only browser is not a problem. It’s not even true. You can code sign for Mac from Linux[1], as I understand it. Worst case, a third-party service will step in to handle packaging and publishing the way we already do for cross-platform native apps and yet Apple will continue to expect devs to test on their Apple devices. I can run Firefox or Chrome on my Mac so