I removed com.apple.developer.healthkit.access and fixed it.
I also removed healthkit.access fragment from entitlements and it uploaded fine. This must've been some very recent silent change in AppStore Connect validation policies
I had the same issue today starting at 3PM eastern time (jan 13) I opened a ticket at Apple, but they send me back to Xcode documentation and WWDC videos on automatic signing. I had also uploaded 1 or 2 builds earlier this morning on TestFlight without any issues.
I deleted the entry (the empty array com.apple.developer.healthkit.access), but after upload, I received the message : ITMS-90000: This bundle is invalid - $message. very weird
also, this empty array is generated by Xcode as soon as you add/remove health kit.
I got the same error :( It was fine yesterday...
After removing com.apple.developer.healthkit.access,
the upload is success, but the build does not appear on TestFlight. (Uploaded 2 build and it won't show)
Mega frustrating. For me, like simonguertin, if you remove the entry, you can upload, but the bundle is still invalid and cannot be used as a build. Everything worked just like before, so it must be an Apple issue. Will send them a ticket.
Same issue, app uploaded fine to TestFlight just yesterday, but I'm getting that error today. I tried all of the below:
Cleaning my project.
Re-enabling automatic app signing in XCODE.
Deleting my provisioning files from ~/Library/MobileDevice/Provisioning\ Profiles/
Disabling automatic signing in xcode and creating my own provisioning profile via the Apple Developer site
None of that worked so don't waste your time.
This issue is suddenly happening to us. By removing com.apple.developer.healthkit.access cause invalid bundle when the archive is uploaded, it will cause your app not listed on a test flight. So this is not a proper solution. How we can solve this? Should we just wait?
Worked yesterday, not working today with same build. Removing the fragment blocks me from getting Apple Health permissions... Hopefully this is fixed soon.
Same here, removed com.apple.developer.healthkit.access and fixed it.
Same Problem Here. How this can be possible