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
In the current implementation of the health data fetching function, the returned results are limited to a maximum of 1000 data points, even when the actual number of data points is much higher.
This issue occurs when fetching health data from the last 7 days using the getHealthDataFromTypes function.
The expected behavior is that the function should return all available data points within the specified date range.
// fetch health data from the last 7 days
List<HealthDataPoint> healthData = await health.getHealthDataFromTypes(now.subtract(Duration(days: 7)), now, types);
print("Health data length: ${healthData.length}");
In the above code snippet, healthData.length returns 1000, even when the actual number of data points is higher.
Device / Emulator and OS
Please complete the following information for each phone and/or emulator you're experiencing this bug on:
Device: POCO F3
OS: Android 13
The text was updated successfully, but these errors were encountered:
Hey @simplayy, we faced the same issue and figured out that there was a missing implementation at the Health Connect level. This has been addressed in the following pull request: #862.
In the current implementation of the health data fetching function, the returned results are limited to a maximum of 1000 data points, even when the actual number of data points is much higher.
This issue occurs when fetching health data from the last 7 days using the getHealthDataFromTypes function.
The expected behavior is that the function should return all available data points within the specified date range.
In the above code snippet, healthData.length returns 1000, even when the actual number of data points is higher.
Device / Emulator and OS
Please complete the following information for each phone and/or emulator you're experiencing this bug on:
The text was updated successfully, but these errors were encountered: