Declare appropriate permissions

Health Services on Wear OS uses the following distinct permissions:

• ACTIVITY_RECOGNITION
• BODY_SENSORS
• BODY_SENSORS_BACKGROUND on Wear OS 4 (API level 33) and higher
• ACCESS_FINE_LOCATION

Consult the table below to determine which permissions are necessary for your app, based on the types of fitness data that you want to present to users. Make sure to follow the basic principles for requesting permissions, including asking for permissions in context.

If your app targets API level 33 or higher and uses PassiveMonitoringClient to access body sensor information in the background, request both the BODY_SENSORS and BODY_SENSORS_BACKGROUND permissions.

Note: If you specify isGpsEnabled = true in your ExerciseConfig, Health Services also uses GNSS to improve the accuracy of metrics like distance, speed, and pace, but requires the user to grant the ACCESS_FINE_LOCATION permission to your app.

Data type	Permission
CALORIES CALORIES_DAILY DISTANCE_DAILY DECLINE_DISTANCE DISTANCE ELEVATION_GAIN ELEVATION_LOSS FLAT_GROUND_DISTANCE FLOORS FLOORS_DAILY GOLF_SHOT_COUNT INCLINE_DISTANCE PACE REP_COUNT RUNNING_STEPS SPEED STEPS STEPS_DAILY STEPS_PER_MINUTE SWIMMING_LAP_COUNT SWIMMING_STROKES CALORIES_TOTAL WALKING_STEPS UserActivityInfo UserActivityState	ACTIVITY_RECOGNITION
HEART_RATE_BPM VO2_MAX	BODY_SENSORS BODY_SENSORS_BACKGROUND (on API level 33 and higher)
ABSOLUTE_ELEVATION LOCATION	ACCESS_FINE_LOCATION