Any ideas on how to resolve this issue?

Do you even need to specify a provisioning profile when you notarize? I don't.

When using Automatically handle signing in an app that requires provisioning -- apparently not all do -- one is provided for you.

After several hours of playing I finally found the issue. This is the first time I’d tried to have an app notarized after renewing my developer account. I had to go to the devices section and “renew” my list of devices for the account. Once I did that everything worked.

I don’t remember having to do that in the past. Perhaps it is a requirement of using the latest version of X code.

Marc

On Dec 1, 2021, at 12:56 PM, Marco S Hyman <marc@...> wrote:

Happy December Xcode users,

I updated a Mac app and uploaded it to the Mac App Store. No problems. It is in review. I also make the app available for download for those who don’t want to use the app store. Problems.

When trying to upload the app to be notarized I’m getting a certificate error: Profile doesn’t include the selected signing cert. I’ve always used the “Automatically Handle Signing” option. It has, up to this point, always worked. Needless to say I’m clueless as to what might be wrong.

The only thing that looks interesting to my untrained eye is that my Signing Certification has always been team A3U.... That is also what I see when I check certificates at appstoreconnect.apple.com. Xcode, however, says my signing cert is WPD....

I suspect that is the issue as the profile references the A3U... cert. Even a freshly downloaded cert.

Any ideas on how to resolve this issue?

Do you even need to specify a provisioning profile when you notarize? I don't.

Happy December Xcode users,

I updated a Mac app and uploaded it to the Mac App Store. No problems. It is in review. I also make the app available for download for those who don’t want to use the app store. Problems.

When trying to upload the app to be notarized I’m getting a certificate error: Profile doesn’t include the selected signing cert. I’ve always used the “Automatically Handle Signing” option. It has, up to this point, always worked. Needless to say I’m clueless as to what might be wrong.

The only thing that looks interesting to my untrained eye is that my Signing Certification has always been team A3U.... That is also what I see when I check certificates at appstoreconnect.apple.com. Xcode, however, says my signing cert is WPD....

I suspect that is the issue as the profile references the A3U... cert. Even a freshly downloaded cert.

Any ideas on how to resolve this issue?

Thanks,

Marc