Why are there two provider enums for Google?
Google Fit reports two different provider enum values depending on the connection path
Google Fit reports two different provider enum values depending on the connection path:
GOOGLEFITfor connections made through the mobile SDK (only wheninitConnectionis called with Google as the connection type).GOOGLEfor connections made via the web API or widget.
Update your mapper to accept both values.
PreviousWhy do I get multiple Garmin sleep sessions for one night, or a sleep payload that looks incomplete?
NextIs planned_workout a valid webhook type?
Last updated
Was this helpful?