Update / resolution: I re-tested with the entitlement removed from my entitlements file entirely. SHManagedSession().result() against the default Shazam catalog matched a real song cleanly on a physical device, with the app signed against the team wildcard profile carrying only the baseline four entitlements (no com.apple.developer.shazamkit). Confirms what Apple's App Services doc hints at: ShazamKit does not actually require the entitlement in the issued profile for default-catalog matching on iOS. The backend issuance gap is real (and FB22582333 is still filed) but it is not blocking ShazamKit runtime use. Leaving this here in case it saves someone else the signing rabbit hole.

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.