ShazamKit enabled on App ID but provisioning profiles do not include com.apple.developer.shazamkit entitlement

Question

Tomh5 OP

Created Feb ’26

Replies 2

Boosts 2

Participants 3

Hi,

I’m a paid Apple Developer Program member and I’m seeing an entitlement issuance issue with ShazamKit.

ShazamKit is enabled for my App ID (com.tomharris.dnbidfinder) in Certificates, Identifiers & Profiles.

However, every iOS Development provisioning profile I generate does not include the entitlement:

com.apple.developer.shazamkit

verified this by decoding the downloaded .mobileprovision file:

security cms -D -i <profile>.mobileprovision | /usr/libexec/PlistBuddy -c "Print :Entitlements" /dev/stdin

The entitlement dictionary does not contain the ShazamKit key.

Because of this: • The signed .app does not contain the Shazam entitlement • SHSession.match(signature) fails on device • I receive ShazamKit runtime error 201 / 212

I’ve already: • Toggled ShazamKit off and back on for the App ID • Created new provisioning profiles • Created a brand new App ID to test • Refreshed profiles in Xcode

The portal UI shows ShazamKit as enabled, but the entitlement is not being issued into provisioning profiles.

Has anyone experienced this before? Is there an additional approval step required for ShazamKit, or could this be a backend entitlement propagation issue?

Thanks.

Boost

Answer 1

miketocco OP

1d

Same symptom on a different Team ID (MCN4U9B2K4, bundle com.michaeltocco.Sanbox, Xcode 17, iOS 18.5, Automatic signing). ShazamKit ticked in App Services and persisting across portal reloads; Xcode fails with "Entitlement com.apple.developer.shazamkit not found and could not be included in profile." The profile Apple just issued (2026-04-22) for my App ID carries only application-identifier, keychain-access-groups, get-task-allow, and com.apple.developer.team-identifier — no com.apple.developer.shazamkit.

Already tried: deleting + recreating the App ID from scratch, the uncheck/save/wait/re-check/save capability-toggle trick, purging cached profiles between every attempt, -allowProvisioningUpdates, device target (not Simulator). Same issuance pathology persists.

Runtime (when forced against a team wildcard profile for testing) returns com.apple.ShazamKit Code=202 "Missing entitlements" → AMS 306 → HTTP 401 from api.shazam.apple.com/v1/catalog/US/match, which is consistent with the entitlement never having been included in the profile.

Feedback Assistant: FB22582333 (filed 2026-04-22).

Would be good to get Apple engagement on this — looks like the issuance-pipeline bug is not specific to your team.

0

Answer 2

DTS Engineer OP

Apple

11h

I’m just dropping a link to miketocco’s thread about this, which has more details.

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

0