-
-
Notifications
You must be signed in to change notification settings - Fork 1.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
"3rd Party Mac Developer ____" naming conventions are no longer accurate #5320
Comments
I think this only affects Mac App Store builds, but would be great to have this updated. Just donated for priority. Thank you! |
Investigating further, when you request the certificate through the Apple developer console, it is named 3rd Party Mac Developer ..., when you request it through XCode, it is named "Apple Distribution". Electron builder should probably fall back onto the other, but I assume that's why not that many people run into this issue. |
Is this still relevant? If so, what is blocking it? Is there anything you can do to help move it forward? This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. |
This is still an issue. Certificates provisioned through the developer portal instead of XCode are named “Apple Distribution” instead of “3rd party developer”. The check should look for both kinds of labels. |
Is this still relevant? If so, what is blocking it? Is there anything you can do to help move it forward? This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. |
We have a CI build process which builds ZIP and DMG for "Mac" and PKG for "Mas". It was working consistently until our certificates expired and we are working through updating them and running into trouble because it seems that apple's naming conventions have changed as of "Xcode 11".
Another signing project has some info: electron/osx-sign#227 electron/osx-sign#230
Looks like this issue was raised back in november but auto-closed: #4410
I'm not really sure why more people haven't encountered this?
The text was updated successfully, but these errors were encountered: