-
Notifications
You must be signed in to change notification settings - Fork 84
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Out of sync entitlements for HealthKit (possibly others as well) #2117
Comments
I am experiencing a similar issue but for NFC capability instead. Capability is enabled in dev portal and entitlements have been set up properly. |
Same here, also with NFC capability. But works with Expo Version 47. Works also with Expo 49.0.15 if you add the React Native code before first build in expo. Tested with react-native-nfc-manager & Expo dev build. This was the error I got: /Users/expo/workingdir/build/ios/xx.xcodeproj: error: Provisioning profile "*[expo] com.xx.xx AdHoc xxxxx" doesn't include the com.apple.developer.nfc.readersession.formats entitlement. Profile qualification is using entitlement definitions that may be out of date. Connect to network to update. (in target 'xxx' from project 'xx') |
Hi, What is the updated date of your provisioning profile if you run the |
Can you check if |
Had a similar issue, upgrading to eas 5.9.1 fixed it - now my development build is building and apple health works |
Build/Submit details page URL
https://expo.dev/accounts/uxapp/projects/uxwellara/builds/10e38241-ab74-4cbe-ad61-1c5e63914071
Summary
It seems like HealthKit capabilities are not properly synced at EAS build. I added necessary entitlements to my app, specifically:
Upon scheduling an EAS build, I can confirm that the capabilities are properly synced on the Apple Developer portal and the provisioning profile is updated to have this new capabilities enabled. However, when the actual app is being built inside EAS build, its almost like EAS is using some "outdated" version of the provisioning profile which doesn't have these capabilities enabled, thereby throwing the following error:
Once again, on the developer portal these capabilities are indeed enabled.
Managed or bare?
Managed
Environment
Error output
No response
Reproducible demo or steps to reproduce from a blank project
The text was updated successfully, but these errors were encountered: