How do I "clearly identify the HealthKit functionality in app's user interface to avoid confusion"?

I've submitted an app to the app store, but it keeps being rejected, and I'm not sure what I need to do. I actually have a very similar app which was accepted with no problems, so I'm not sure why this one has caused problems.


My app uses the Apple HealthKit to read heart rate data for the user. This is then saved to my database and displayed in a chart within the app.


In my app description I have:


"MyApp integrates with your iPhone's Health app to read heart rate data - this allows you to monitor your health".


In the screen which asks for permission to read Heart Rate data, the "App Explanation" is:

"Allow MyApp to read and store your heart rate data, to help you monitor your health".


When I submit it for review, I get the following feedback (I've now had this about 6 times!):


"Your app uses the HealthKit or CareKit APIs but does not indicate integration with the Health app in your app description and clearly identify the HealthKit and CareKit functionality in your app's user interface.


Next Steps


To resolve this issue, please clearly identify the HealthKit functionality in app's user interface to avoid confusion."


I don't know what else I can do. I've stated it in the app description, and I've listed it in the UI when it asks for permission. What else can I do to get past this?

Mac mini, macOS 11.6

Posted on Dec 10, 2021 2:44 AM

Reply
Question marked as Top-ranking reply

Posted on Dec 10, 2021 10:59 AM

SharonGilmore wrote:

I don't know what else I can do. I've stated it in the app description, and I've listed it in the UI when it asks for permission. What else can I do to get past this?

I don't know what else to tell you. Review what Apple said, "Your app uses the HealthKit or CareKit APIs but does not indicate integration with the Health app in your app description and clearly identify the HealthKit and CareKit functionality in your app's user interface." Let's break that apart...


"Your app uses the HealthKit or CareKit APIs"

This is not under dispute. You have added a description to satisfy the API-level access. Without this description in the Info.plist, your app may be automatically rejected or crash. But this is not sufficient to pass app review.


"but does not indicate integration with the Health app in your app description and clearly identify the HealthKit and CareKit functionality in your app's user interface."

two parts here...


"but does not indicate integration with the Health app in your app description"

Technically speaking, you did say this with, "MyApp integrates with your iPhone's Health app to read heart rate data - this allows you to monitor your health". But this is the nice part about app review. For all of its faults, it is human run, not automated. You can just satisfy a requirement to "integrate" by saying the word "integrate". That's not sufficient. You actually have to do that.


Integration can work two ways. Either you can read data from the system or provide data to the system. Your description, even though you use the word "integrate" clearly says you are reading data from the system. You even explain why you do this, "to monitor your health". What you need to explain is how that happens, specifically. That is what the next part is about.


"clearly identify the HealthKit and CareKit functionality in your app's user interface."

You have to explain where the heart rate data is used in your app. The app reviewer has be able to navigate to that screen and see the data being meaningfully integrated into your app's functionality.


There is a big field at the bottom of the App Store connect page for notes that you provide to Apple. These notes will only be seen by Apple. They are not the same as the description for the end user. You need to use this field to clearly explain to Apple where to find the heart rate data (Apple's data) in your app and what you are using it for. This is a technical and regulatory field. Don't use marketing lingo or anything here. Explain what you are doing.


You may still need to add additional text to your description explaining how heart rate data is used in your app. In the public-facing description, you can use more marketing talk to explain why your app provides functionality that isn't already provided by the operating system or by other apps.


You might want to review recent Apple Developer videos. There is even a video titled, "Tips for preventing common review issues" released just the other day. You might also want to review the recent Tech Talks. There are a couple of upcoming sessions (in Chinese) for App Review. There are still some English Office Hour appointments available for App Review. But to be honest, those appointments are sure to be in high demand. You can request one, but there is no guarantee you will get it. And App Review is going to tell you the same thing that I just did above - I guarantee.

2 replies
Question marked as Top-ranking reply

Dec 10, 2021 10:59 AM in response to SharonGilmore

SharonGilmore wrote:

I don't know what else I can do. I've stated it in the app description, and I've listed it in the UI when it asks for permission. What else can I do to get past this?

I don't know what else to tell you. Review what Apple said, "Your app uses the HealthKit or CareKit APIs but does not indicate integration with the Health app in your app description and clearly identify the HealthKit and CareKit functionality in your app's user interface." Let's break that apart...


"Your app uses the HealthKit or CareKit APIs"

This is not under dispute. You have added a description to satisfy the API-level access. Without this description in the Info.plist, your app may be automatically rejected or crash. But this is not sufficient to pass app review.


"but does not indicate integration with the Health app in your app description and clearly identify the HealthKit and CareKit functionality in your app's user interface."

two parts here...


"but does not indicate integration with the Health app in your app description"

Technically speaking, you did say this with, "MyApp integrates with your iPhone's Health app to read heart rate data - this allows you to monitor your health". But this is the nice part about app review. For all of its faults, it is human run, not automated. You can just satisfy a requirement to "integrate" by saying the word "integrate". That's not sufficient. You actually have to do that.


Integration can work two ways. Either you can read data from the system or provide data to the system. Your description, even though you use the word "integrate" clearly says you are reading data from the system. You even explain why you do this, "to monitor your health". What you need to explain is how that happens, specifically. That is what the next part is about.


"clearly identify the HealthKit and CareKit functionality in your app's user interface."

You have to explain where the heart rate data is used in your app. The app reviewer has be able to navigate to that screen and see the data being meaningfully integrated into your app's functionality.


There is a big field at the bottom of the App Store connect page for notes that you provide to Apple. These notes will only be seen by Apple. They are not the same as the description for the end user. You need to use this field to clearly explain to Apple where to find the heart rate data (Apple's data) in your app and what you are using it for. This is a technical and regulatory field. Don't use marketing lingo or anything here. Explain what you are doing.


You may still need to add additional text to your description explaining how heart rate data is used in your app. In the public-facing description, you can use more marketing talk to explain why your app provides functionality that isn't already provided by the operating system or by other apps.


You might want to review recent Apple Developer videos. There is even a video titled, "Tips for preventing common review issues" released just the other day. You might also want to review the recent Tech Talks. There are a couple of upcoming sessions (in Chinese) for App Review. There are still some English Office Hour appointments available for App Review. But to be honest, those appointments are sure to be in high demand. You can request one, but there is no guarantee you will get it. And App Review is going to tell you the same thing that I just did above - I guarantee.

This thread has been closed by the system or the community team. You may vote for any posts you find helpful, or search the Community for additional answers.

How do I "clearly identify the HealthKit functionality in app's user interface to avoid confusion"?

Welcome to Apple Support Community
A forum where Apple customers help each other with their products. Get started with your Apple Account.