Post not yet marked as solved
Same issue here on iOS 16. Have you ever found a reason and/or solution?
Post not yet marked as solved
I'm facing the same issue: The entitlement is available in the provisioning profiles for development and ad-hoc distribution, but not for App Store distribution, despite it is listed under "Enabled Capabilities". See this thread: https://developer.apple.com/forums/thread/721772
The issue doesn't seem to be related to the cloud managed profiles / certificates: I've just manually created a new provisioning profile with type "App Store", and despite "User Assigned Device Name" is listed in the "Enabled Capabilities", the .mobileprovision file doesn't contain the entitlement. A provisioning profile with type "Ad Hoc" contains the entitlement.
I've got the same issue with our cloud managed certificates. The entitlement is included in the provisioning profile for development ("iOS Team Provisioning Profile"), but not in the profile for distribution ("iOS Team Store Provisioning Profile"), despite "App Store" is listed in the capability's distribution restrictions.
As I'm finding here several threads about this topic, is there a general issue with the handling of this entitlement for cloud managed profiles / certificates?
Yesterday, I've written an email to developer (at) email.apple.com, but haven't received an answer yet (honestly, I don't know if this address is supposed to receive mails... I've just answered to the entitlement confirmation mail)
Post not yet marked as solved
I can confirm this issue. There is no option in the Web-UI to enable "Access to Cloud Managed Distribution Certificate" for an API-Key.
Post not yet marked as solved
Any other confirmations regarding iOS 13.1.3?
Post not yet marked as solved
It isn't mentioned in the release notes, but I can't reproduce this bug in iOS 13.1.3 (17A878). Can you?
Post not yet marked as solved
I can confirm this bug still exists in iOS 13.1 (17A844) and iOS 13.1.1 (17A854).Calling SecItemCopyMatchig is affected by this bug, too.A physical shake leads the Touch-ID-prompt to show up. Unfortunatly, a simulated shake event (I've written a FakeShaker, which provokes a UIMotionEvent) doesn't work.
