-
|
Are there currently any circumstances or reasons that might lead you to consider publishing the app on the Microsoft App Store and Apple App Store (yes, there's the paid developer account, which we all don't like)? I recall you, @sircharlo, mentioning that it wasn’t in the plans at the time, but that was quite a while ago. Since then, the macOS installation process has become a bit more challenging for regular users, with all the terminal commands and such. What’s your perspective on the current situation and potential future scenarios? |
Beta Was this translation helpful? Give feedback.
Replies: 4 comments 17 replies
-
|
Reading this discourages me: How to Release an Electron App on the Mac App Store The time, equipment and resources required to do this are all out of reach for the moment, unfortunately. |
Beta Was this translation helpful? Give feedback.
-
|
Do you mean that it involves re-building the app, or what exactly is the most challenging? |
Beta Was this translation helpful? Give feedback.
-
|
The re-building itself is not challenging, but the whole process involves having an Apple developer account of ~$100/year, maintaining three signing certificates which expire every year, maintaining provisioning profiles which expire every year and being reviewed by Apple before a release becomes available. This means annual costs, extra recurring maintenance and a significantly slower release cycle. |
Beta Was this translation helpful? Give feedback.
-
|
Got it, thanks for the answer |
Beta Was this translation helpful? Give feedback.
-
|
This, combined with the fact that all A/V instructions are written for Windows, makes it too much effort for too little gain (in my opinion). |
Beta Was this translation helpful? Give feedback.
-
|
@mtdvlpr If someone (like me) were to offer to do this with their mac as a developer, would it be worth considering? I realize it adds some difficulty to the process, but the up-side for our friends who are using mac devices for one reason or another is tremendous. |
Beta Was this translation helpful? Give feedback.
-
|
After doing some research, I think that the best way for us to implement this, would be to not publish the app to the App Store, but to sign and notarize the app from GitHub. This would resolve the existing security problems and require almost no extra efforts once it's setup. Steps to perform1. Code Sign the app from GitHubCode Signing is currently done by the user with the 2. Notarize the app from GitHubNotarizing the app takes care of the second command that the user currently needs to execute: To notarize the app we need the following variables: ImplicationsUsers
Developers
Certificates (https://developer.apple.com/support/certificates/)
Resources
@sbscomp, if you or someone else is willing to provide us with the necessary certificates and credentials, we would be able to implement this without changing the release procedure. |
Beta Was this translation helpful? Give feedback.
-
|
@sbscomp, @sircharlo, I'd love your feedback on this :) |
Beta Was this translation helpful? Give feedback.
-
|
I'm completely willing to help out, but would it be better to have one of your names on it rather than an account that I owned? |
Beta Was this translation helpful? Give feedback.
-
|
I have nothing against using a certificate generously provided by @sbscomp or someone else. |
Beta Was this translation helpful? Give feedback.
-
Sure, but I assume that it would require a dedicated developer account for M3? Of course that would be ideal, but someone would have to be willing to set that up and maintain it. If we could use an existing account, the owner would not have extra costs and would therefore be able to support us for longer. What matters to us, is that we receive the necessary resources and that it's maintainable for the person long-term. We don't want to implement this if we have to disable it again within the year. That would be confusing for the non-technical macOS users who are now used to the Terminal commands. |
Beta Was this translation helpful? Give feedback.
-
|
Have you guys considered something like this solution? https://signpath.org/ |
Beta Was this translation helpful? Give feedback.
-
|
If I read their documentation correctly, we'd still need a paid developer account... See https://about.signpath.io/blog/2024/11/29/building-trusted-software-for-macos |
Beta Was this translation helpful? Give feedback.
-
|
@mtdvlpr and @sircharlo I have created a certificate that can be used to sign the application. |
Beta Was this translation helpful? Give feedback.
-
|
I've sent you an encrypted email with the certificate, I'll send you another one with the credentials as soon as I have them set up. |
Beta Was this translation helpful? Give feedback.
-
|
Thank you very much! I'm excited to implement this and provide a significantly better user experience for macOS users. |
Beta Was this translation helpful? Give feedback.
-
|
Encrypted email with credentials has been sent. :) |
Beta Was this translation helpful? Give feedback.
-
|
@sircharlo, could you configure the following secrets in the repo?
|
Beta Was this translation helpful? Give feedback.
-
|
Continued in #3804 |
Beta Was this translation helpful? Give feedback.
Reading this discourages me: How to Release an Electron App on the Mac App Store
The time, equipment and resources required to do this are all out of reach for the moment, unfortunately.