Provisioning Profile Missing com.apple.developer.alarmkit Entitlement – No AlarmKit Capability in Developer Portal

Question

slaughters85j OP

Created 2d

Replies 3

Boosts 0

Participants 3

Hello everyone,

I’m working with AlarmKit (iOS/iPadOS 26) and encountering a critical blocker. On the simulator, after adding NSAlarmKitUsageDescription to Info.plist, AlarmKit functions as expected—no entitlement issues. However, when building to a physical device, Xcode fails with:

“Provisioning profile … doesn’t include the com.apple.developer.alarmkit entitlement.”

The core issue: there is no AlarmKit capability visible under App ID settings or provisioning profiles in the Developer Portal. Thus, this entitlement cannot be enabled or included in a profile.

Steps taken so far:

Reviewed WWDC25 AlarmKit session and documentation.
Reviewed Apple Developer documentation on entitlements and provisioning.
Verified there's no AlarmKit toggle or capability in the Developer Portal (Certificates, Identifiers & Profiles > Identifiers).
Submitted multiple Feedback requests via Feedback Assistant, but received no technical resolution.

Questions:

Is there meant to be a separate AlarmKit entitlement (distinct from Critical Alerts)?
If so, when will the com.apple.developer.alarmkit entitlement option be available in the Developer Portal?
In the meantime, how can developers test AlarmKit-based features on physical devices?
Could an Apple Engineer advise on whether an internal entitlement workflow or workaround exists for testing?

Thank you in advance for any clarity anyone can provide. I'm stuck at a total impasse until this is resolved.

—John

Current Project Configuration Relevant Parts:

info.plist:

<key>NSAlarmKitUsageDescription</key> <string>Schedules system-level alarms that break through Do Not Disturb and Focus modes to ensure alarms trigger reliably.</string>

<key>UIBackgroundModes</key> <array> <string>audio</string> <string>background-app-refresh</string> <string>location</string> <string>remote-notification</string> </array>

entitlements.plist

<key>aps-environment</key> <string>development</string>

<key>com.apple.developer.icloud-services</key> <array> <string>CloudKit</string> </array>

<key>com.apple.developer.alarmkit</key> <true/>

<key>com.apple.developer.usernotifications.time-sensitive</key> <true/>

Answered by kthchew in 855201022

Did some LLM/AI put com.apple.developer.alarmkit there for you? I searched that entitlement on the web and the only result I got was this very forums post. If some made-up entitlement is applied then you might get an issue like that.

What happens if you just remove that entitlement?

Boost

Answer 1

kthchew OP

2d

Accepted Answer

Did some LLM/AI put com.apple.developer.alarmkit there for you? I searched that entitlement on the web and the only result I got was this very forums post. If some made-up entitlement is applied then you might get an issue like that.

What happens if you just remove that entitlement?

1

Answer 2

slaughters85j OP

2d

@kthchew First off, I'd like to say thank you very much for your timely reply. Second, I'd like to just say Wow!

Yes, an LLM slid that in and I didn't even think to question its authenticity. I would have thought that Xcode would have told me something wasn't right and the error it did report reinforced to me that there was a legitimate entitlement missing.

I removed that entitlement from the entitlements file and the error went away immediately and the app built to my device.

Again, thank you so much. Who knows how much longer I would have battled this fake entitlement.

Lesson learned.

0

Answer 3

Engineer OP

Apple

4h

And I just want to add to this discussion that we are seeing an increase in LLMs making up non-existent entitlements causing similar problems - it has become a common occurrence.

Additionally LLMs don't seem to understand the difference between declared entitlements, special entitlements that you need to apply for, and Info.plist entries, calling everything an "entitlement", causing these errors, "Provisioning Profile Missing xxx entitlement".

So, if anyone else runs into the same problem and found this thread, please consult the official documentation before - and if you run into issues with entitlements - after to make sure that the entitlement mentioned is not made up.

0