You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am facing an issue while using the react-native-health-connect SDK to retrieve calorie data from Samsung Health. The problem is specific to Samsung Health integration and works as follows:
When I perform an exercise and record it, I can retrieve calorie data accurately through the SDK.
However, if I do not enable exercise and simply burn calories through steps, the SDK does not return the calorie data for the steps, except for resting calories.
This issue makes it impossible to track calories burned through everyday activities like walking or general movement unless the user explicitly starts and records an exercise.
To summarize:
Expected Behavior: Calories burned through steps (excluding resting calories and without an exercise session) should also be available in the calorie data fetched via the SDK.
Current Behavior: Calories are only available if an exercise session is started and recorded, while calories from steps are not included.
Can you please confirm:
Is this behavior a known limitation or issue with Samsung Health’s data integration through react-native-health-connect?
Are there any specific permissions or settings required to fetch calories burned through steps without starting an exercise, excluding resting calories?
Is there any workaround or fix to address this issue?
Hello,
I am facing an issue while using the react-native-health-connect SDK to retrieve calorie data from Samsung Health. The problem is specific to Samsung Health integration and works as follows:
This issue makes it impossible to track calories burned through everyday activities like walking or general movement unless the user explicitly starts and records an exercise.
To summarize:
Can you please confirm:
I integrated this package through the reference -> https://matinzd.github.io/react-native-health-connect/docs/permissions
The text was updated successfully, but these errors were encountered: