It seams that I have also solved the second problem. I use a view modifier to start the initially query. I started it in onAppear which seams to be to fast. Some log messages pointed to problems with the presentation of the authorization controller, out of view hierarchy and such things. I changed to task and now it works without problem so far.
Nankea
Users receive reputation points by contributing quality content to the forums.
Posts include post and replies published on the forums.
Post authors can mark replies as Accepted to indicate successful solutions.
Apple Developer Forums admins can mark replies as Apple Recommended to indicate an approved solution
Last seen
User for
Post
Replies
Boosts
Views
Activity
Hello, Framework Engineer, could we please get an easy initializer to HKDeletedObject for unit tests? See FB12903177. Sorry for posting in this thread, but this feedback is nearly three months old and I did not get any feedback from apple to this proposal.
For the first problem: Yes, I have this info.plist key. I removed it and it works now with Testflight. For the second problem: I will check it out, thanks for the link. AND: This is the fastest response time of an apple engineer I have ever had. You really helped me! Really very much thank you! 👍 This is a magic forum thread. 😉
I have a second and rare problem. If an app request authorization first time to access health data, sometimes the request will never be shown to the user. It mostly appears if the health app was never started before, e. g. on an simulator. But it also appears on real devices. Maybe there has a data base to be initialized first and the request gets lost on some timing issues.
I have an app that uses HealthKit. In Testflight it is possible to install it on iPhone but not on iPad (17.0.3). But I can install it from Xcode on iPad. In app store it offers to install on iPad, but if you do, there comes an alert saying that this is not compatible. It looks like there is in Testflight and in the installation process from app store some code that checks only if this is an iPad and says no and not if this is an device that can run apps that require HealthKit.
I have some of these strange HealthKit incompatibility issues with iPad with iPadOS 17.0.3, too.
EdwardKoetsjarjans solution worked for me. This seems to be the normal way if a version was rejected or if your version was approved, but not published as you wanted to manually do that.
👍