Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Apple Distribution certificate support

See original GitHub issue

Hi,

It seems Apple Distribution certificates not supported.

https://help.apple.com/xcode/mac/current/#/dev3a05256b8 Apple Distribution Sign your apps for submission to the App Store or for Ad Hoc distribution. For use with Xcode 11 or later.

Issue Analytics

State:
Created 3 years ago
Reactions:1
Comments:5 (3 by maintainers)

Top GitHub Comments

2reactions

sethlucommented, Jul 7, 2020

Sorry about the delay, I took a closer look at the documentation again and it seems that the Apple Development and Apple Distribution certs only apply to apps submitted to the (Mac) App Store.

Apple Development For iOS, tvOS, or watchOS apps, run the app on devices and use app services during development. For macOS apps, use app services during development and testing. Note: Available in Xcode 11.0 and later. For earlier Xcode versions, use an iOS Development or Mac Development certificate.

Apple Distribution For iOS, tvOS, or watchOS apps, run the app on designated devices for testing or submit it to the App Store. For macOS apps, sign an app before distributing it through the Mac App Store. Note: Available in Xcode 11.0 and later. For earlier Xcode versions, use an iOS Distribution or Mac App Distribution certificate.

Ref: https://help.apple.com/xcode/mac/current/#/dev3a05256b8

Here’s an updated version…

Targeting inside the Mac App Store
- For development: Try Apple Development, then Mac Developer
- For distribution: Try Apple Distribution, then 3rd Party Mac Developer Application
Targeting outside the Mac App Store
- Always try Developer ID Application for development/distribution

A PR will be up in a few minutes with this implementation.

1reaction

sethlucommented, May 23, 2020

Oh I see 👌 The new certificates seem to be taking over the existing certificates. How does it sound if we have electron-osx-sign do the following?

For development: Try Apple Development, then Mac Developer
For distribution: Try Apple Distribution, then 3rd Party Mac Developer Application or Developer ID Application depending on the Electron build?

For now, a workaround would be to provide an --identity="Apple Distribution" option to override the default electron-osx-sign behavior.

Currently electron-osx-sign chooses Developer ID Application for signing development builds… Here’s a PR that suggests defaulting all development builds to be signed with Mac Developer identity: https://github.com/electron/electron-osx-sign/pull/183

Top Results From Across the Web

Certificates - Support - Apple Developer

Distribution certificates can be requested only by Account Holders and Admins. For more information on how to use signing certificates, review Xcode Help....

Managing a Distribution Certificate - Apple Developer

Describes how to use the iOS Provisioning Portal for iOS development team agents and team admins. ... Managing a Distribution Certificate.

Your iOS Distribution Certificate will expire in 30 days

Regarding your distribution certificate, once it expires, it simply disappears from the 'Certificates, Identifier & Profiles' section of Member Center. If you ...

Distribute certificates to Apple devices

Install certificates using configuration profiles. iOS, iPadOS, and macOS support these methods to deploy certificate identities with ...

Create enterprise distribution certificates - Account - Help

As a member of the Apple Developer Enterprise Program, you can create multiple enterprise distribution certificates. Required role: Account Holder or Admin.