App Store Distribution fails on valid com.apple.developer.healthkit.access value

The error trying to distrubute to the store
Code Block 
According to the provisioning profile, the bundle contains a key value that is not allowed: '[]' for the key 'com.apple.developer.healthkit.access' in 'Payload/<app>.app/<app>'

Looking at the docs, this is a valid value:
https://developer.apple.com/documentation/bundleresources/entitlements/com_apple_developer_healthkit_access

Similarly, I had no issue until this appeared randomly....

Entitlement File
Code Block 
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>
	<key>com.apple.developer.healthkit.access</key>
	<array/>
	<key>aps-environment</key>
	<string>development</string>
	<key>com.apple.developer.associated-domains</key>
	<array>
		<string>webcredentials:invoy.com</string>
		<string>webcredentials:invoy.dev</string>
		<string>webcredentials:invoydev.com</string>
		<string>webcredentials:invoystage.com</string>
		<string>applinks:invoy.com</string>
		<string>applinks:www.invoy.com</string>
		<string>applinks:invoy.dev</string>
		<string>applinks:www.invoy.dev</string>
		<string>applinks:invoydev.com</string>
		<string>applinks:www.invoydev.com</string>
		<string>applinks:invoystage.com</string>
		<string>applinks:www.invoystage.com</string>
	</array>
	<key>com.apple.developer.healthkit</key>
	<true/>
</dict>
</plist>


HealthKit is enabled as a capability in Apple Profile as well as for the product.

Does anyone have an idea of what could be going wrong? Seems like I am correctly following the practices.
Up vote post of bricepollock1 Down vote post of bricepollock1
15k views
Posted by
bricepollock1
Reply
Add a Comment

Accepted Reply

I removed com.apple.developer.healthkit.access and fixed it.
Posted by
bricepollock1
Up vote reply of bricepollock1 Down vote reply of bricepollock1
Post marked as solved
Add a Comment

Replies

Check your App ID Configuration under 'Certificates, Identifiers & Profiles' in your Developer account.

If you have anything checked that you're not actually using then you need to uncheck it or configure it correctly. In my case I had iCloud checked but didn't have a container attached.

Using Expo I had to clear out my provisioning profile and rebuild as well.

Hope that helps!
Posted by
joshConfigur
Up vote reply of joshConfigur Down vote reply of joshConfigur
Add a Comment
Still not resolved, but if you're here you already knew that
Posted by
arbor apps
Up vote reply of arbor apps Down vote reply of arbor apps
Add a Comment
Any help / explanation from apple why builds suddenly fail?
Posted by
digitech
Up vote reply of digitech Down vote reply of digitech
Add a Comment
Same problem.
Posted by
Tmarafon
Up vote reply of Tmarafon Down vote reply of Tmarafon
Add a Comment
Kindly update if you see any fix without removing the healthkit.
Posted by
jja
Post not yet marked as solved Up vote reply of jja Down vote reply of jja
Add a Comment
I have the same issue.

You can't just remove the key com.apple.developer.healthkit.access because then the general entitlement for HealthKit will also disappear from Signing & Capabilities.

I have also submitted multiple tickets to Apple since I've hit this brick wall.

Perhaps enabling "clinical health records" may bypass the error, but Apple says if you include this entitlement but don't use clinical data, then you will be rejected.

Also, Xcode creates and populates this file, so manually editing this file should not be necessary.

Apple developers, please fix this ASAP
Posted by
Doogles1
Post not yet marked as solved Up vote reply of Doogles1 Down vote reply of Doogles1
Add a Comment 
Code Block language
<key>com.apple.developer.healthkit.access</key>
<array/>


Since the message complains about passing an empty array I removed only the <array/> and all worked fine.
HealthKit still listed in XCode capabilities and archive successfully uploaded to TestFlight.
Posted by
nitor
Post not yet marked as solved Up vote reply of nitor Down vote reply of nitor
Add a Comment
Same issue for me regarding HealthKit — I don't want health record access, but I cannot remove the key from my entitlements file without removing the HealthKit entitlement entirely. Uploads to TestFlight worked fine with an empty array for com.apple.developer.healthkit.access on 12 January, 2021, but started failing for me yesterday.

I've filed FB8972571.
Posted by
Angelo
Post not yet marked as solved Up vote reply of Angelo Down vote reply of Angelo
Add a Comment
NONE of these hacks of the .entitlements file are "fixes." @Apple fix this yesterday.
Posted by
arbor apps
Post not yet marked as solved Up vote reply of arbor apps Down vote reply of arbor apps
Add a Comment
I have the same issue with my code and since it's complaining about an empty array I have added <array> to the beginning of the list.

Code Block Language swift
<dict>
    <array>
	<key>com.apple.developer.healthkit</key>
	<true/>
    <key>com.apple.developer.healthkit.access</key>
    <array/>
</dict>

I have submitted it to TestFlight

Posted by
PetterBraka
Up vote reply of PetterBraka Down vote reply of PetterBraka
Add a Comment
Having the same issue, it's not fixed yet, unfortunately
Posted by
semty
Post not yet marked as solved Up vote reply of semty Down vote reply of semty
Add a Comment
The fourth day can't upload the app. Still waiting for a fix on the Apple side.
Removing line with access removes Apple Health Kit capability from the capabilities list, so I'm unsure about this solution...

Within build from Testflight — Apple Health is working. Brrr...
Posted by
skopanev
Post not yet marked as solved Up vote reply of skopanev Down vote reply of skopanev
Add a Comment
I am still waiting.
Posted by
sheldonlin
Post not yet marked as solved Up vote reply of sheldonlin Down vote reply of sheldonlin
Add a Comment
I'm surprised Apple hasn't addressed this yet. Does anyone have an open ticket with them?
Posted by
jbailey
Post not yet marked as solved Up vote reply of jbailey Down vote reply of jbailey
Add a Comment
Also have the same issue. Hopefully a fix is imminent.
Posted by
radox1
Post not yet marked as solved Up vote reply of radox1 Down vote reply of radox1
Add a Comment