[After iPhone migration] Health app permissions for connected app are not shown

Thanks for reporting the issue. I am trying to gather more information before confirming it is an issue or a feature: If you run your app on the new device after the restoration, does the app show the authorization UI to request the permission again?

Best,
——
Ziqiao Chen
 Worldwide Developer Relations.

@DTS Engineer

Thank you for your response. Here are the answers to your questions.

After restoring to the new device and launching the app, the authorization UI (permission dialog) to request Health permissions was shown again. (When requesting Health permissions, the app calls HKHealthStore's requestAuthorization.)

After requesting Health permissions again, when I opened: Settings → Apps → Health → Data Access & Devices → [target app]

the permission toggles appeared, and all permissions were shown as OFF. (The reason they were shown as OFF is that I turned all permissions OFF when the authorization UI was shown again.)

As additional information, when restoring using Quick Start (direct device-to-device migration), the app permissions were restored in the ON state without any additional action.

I hope this information helps with your investigation.

@DTS Engineer

I would like to share some additional findings.

When I performed the following steps, the permission information for all apps was restored:

1. Restore from iCloud backup.
   (At this point, the permission information was not restored.)
2. Launch the Health app.
   (When the Health app is launched, data download from iCloud starts automatically.)
3. Go to: Settings → Apps → Health → Data Access & Devices → [target app]
   and confirm that the permission information has been restored.

Based on this behavior, it seems that when restoring from iCloud, the permission information is not restored until the Health app is launched.

Is this expected behavior of the Health app?
Also, from an app developer’s perspective, how should this case be handled or considered in app implementation?

Thanks for sharing your findings, which indicate that:

• Launching the Health app after the restoration triggers a Cloud synchronization,
• requestAuthorization shows the authorization UI if the synchronization isn't done yet.

This behavior is what I'd expect based on my understanding about Cloud synchronization and HealthKit.

From an app developer’s perspective, you call requestAuthorization as what you should do so the second bullet works. Users may need to authorize the permission once again before the Cloud synchronization is done, and that seems to be fine to me as a user.

Best,
——
Ziqiao Chen
 Worldwide Developer Relations.