You’re not alone—this type of Health and HealthKit iCloud sync issue has been appearing for many users after migrating to a new iPhone and following recent iOS updates. In most cases, there isn’t a single switch that fixes the problem. Instead, the issue is usually caused by a stalled background sync queue, a corrupted Health iCloud index, or a third-party app creating a sync deadlock. This also explains why syncing may briefly work after toggling iCloud settings, why it initially worked on your iPad and then stopped, and why companion apps such as Fitness or Condition stopped syncing at the same time.
One of the most commonly missed fixes is forcing HealthKit to re-index in the background. Turning on “Share iPhone Analytics” under Privacy & Security → Analytics & Improvements triggers a background reprocessing cycle. After enabling this setting, restarting the iPhone and leaving it plugged in on Wi-Fi overnight often allows the stalled Health data to resume syncing without deleting any data.
If the issue persists, resetting the Health iCloud connection must be done carefully. Turning Health off in iCloud, restarting the phone, waiting at least 30 to 60 minutes, and then turning Health back on gives iOS enough time to clear the previous sync state. After re-enabling Health, the phone should be left plugged in and on Wi-Fi for several hours without repeatedly opening the Health app, as doing so can interrupt the initial re-sync process.
Another frequent cause is a third-party Health app blocking the entire HealthKit sync pipeline. Temporarily disabling all third-party Health app access, restarting the phone, and allowing a couple of hours for syncing to resume can help identify whether this is the problem. If syncing starts working again, re-enabling apps one at a time will usually reveal which app is causing the deadlock.
Because you mentioned that the Condition app is also affected, the issue may involve Motion and Fitness permissions. Turning Fitness Tracking off, restarting the phone, and then turning it back on often restores communication between Fitness-related apps and Health. After doing this, it’s best to open the Fitness app once and then leave it alone to allow background syncing to proceed.
It’s also important to confirm that iCloud storage is not nearly full and that all devices are using the same region settings. Health data syncing can silently fail when available iCloud storage is too low or when region mismatches exist between devices, even though other iCloud services appear to function normally.
If none of these steps work, the most reliable last-resort solution is signing out of iCloud entirely on the affected iPhone, restarting the device, and then signing back in and re-enabling Health syncing. This does not delete Health data, but it is disruptive and should only be done if other methods fail.
Apple has not fully resolved this issue because HealthKit syncing is encrypted, device-indexed, and heavily dependent on background processes. When the Health index breaks, iOS often does not recognize the failure, and system updates typically do not rebuild the index automatically. As a result, the problem can persist across multiple iOS versions.
If the issue continues after all of the above steps, further troubleshooting may require Apple Support escalation to force a backend HealthKit reset. To determine whether that option is appropriate, it helps to know whether the iPhone was set up using Quick Start or an iCloud restore, whether an Apple Watch is involved, and which third-party health apps are installed.
