After providing all write and read permissions, Samsung Health can sometimes take more than a day to start sending data to Health Connect.
This is very often reported by our customers.
Some people never have any data sent from Samsung Health.
Are you aware of any bugs or decisions why this might be happening?
Is there anything that can be tried to reliably fix it and trigger a sync?
We’ve tried uninstalling and reinstalling Samsung Health and Health Connect, removing and re-adding permissions.
Also could you elaborate whether the “Sync with Samsung Cloud” toggle makes any difference and why?
Please contact with the related team directly via Samsung Developer Support.
Here is the link: Dev Support | Samsung Developer
Attach the dumpstate log, reproduction route, and demo video/screenshot with the problem details while reporting.
Follow the below steps to collect dumpstate log:
->Make sure you watch is connected to your phone
->Reproduce the problem on a watch - in this case - start a sample app and perform a measurement, where frequency other than expected occurs.
->Go to Galaxy Wearable App on yourPhone
->Select > More (Ξ) > About Galaxy Wearable > Touch “Galaxy Wearable” heading 10 times > select [Run Watch Dump]
->Wait (may take a few minutes)
->Open app: MyFiles > Internal Storage > Download > log > GearLog > bundled-bugreport-xx.zip.
->Select “Share” to copy the file to your desktop
->Attach the bundled-bugreport-xx.zip file to the ticket