Xcode 13 RC AutoFill Credential Provider capability not available for Developer ID provisioning profile

Question

billymeltdown OP

Created Sep ’21

Replies 1

Boosts 0

Views 1.3k

Participants 2

Hello,

Our macOS app includes a Password AutoFill extension and both the host app and extension have the entitlement for AutoFill Credential Provider. We have found that in Xcode 13 RC, when we attempt to archive our app using xcodebuild we receive this error:

Cannot create Developer ID provisioning profile for "our.app.ID" The AutoFill Credential Provider capability is not available for Developer ID provisioning profiles. Disable this feature and try again.

And a similar message for our extension's app id.

We believe this to be a bug as building/archiving/submitting using Xcode 12 worked fine with this same entitlement.

Otherwise, are non-Mac App Store apps now being excluded from including Password AutoFill capability? We've been shipping this feature to our customers in our Developer ID signed app since it first became available in macOS Big Sur.

We'd appreciate it if someone could look into this right away, we have filed a feedback report: FB9634952.

Boost

Answer 1

DTS Engineer OP

Apple

Sep ’21

We have found that in Xcode 13 RC

Is this new in Xcode 13.0 RC? Or did you have similar problems with the previous Xcode 13 beta seed (13.0b5)?

are non-Mac App Store apps now being excluded from including Password AutoFill capability?

AFAICT that’s not the case. Specifically:

It’s still listed as available in Developer Account Help > Supported capabilities (macOS).
I can manually create a Developer ID profile with that capability:

% security cms -D -i Test690381_Dev_ID.provisionprofile 
<dict>
  …
  <key>Entitlements</key>
  <dict>
        
    <key>com.apple.developer.authentication-services.autofill-credential-provider</key>
    <true/>
    …         
  </dict>
  …
  <key>ProvisionsAllDevices</key>
  <true/>
  …
</dict>
</plist>

That suggests that this is a problem with the Xcode side of things.

we have filed a feedback report: FB9634952.

Thanks. I’ve confirmed that this has [1] landed in the right place.

Have you tried working around this by switching to manual signing? I suspect that that’ll work.

Share and Enjoy
—
Quinn “The Eskimo!” @ Developer Technical Support @ Apple
let myEmail = "eskimo" + "1" + "@" + "apple.com"

[1] Well, will, once the folks get to work in Cupertino (-:

0