iOS Permissions

Zendrive SDK needs the following permissions for its products to function smoothly on iOS devices:

Product	Location	Motion and Fitness	Bluetooth
Automatic Trip Detection (Trip Start)	Vital		Not required.
Automatic Trip Detection (Trip End)	Vital	Good to have.	Not required.
Trip Mileage	Vital	Good to have.	Not required.
Collision Detection	Vital	Not required.	Not required.
Driving Behavior - Hard Brake	Vital	Not required.	Not required.
Driving Behavior - Hard Turns	Vital	Not required.	Not required.
Driving Behavior - Rapid Acceleration	Vital	Not required.	Not required.
Driving Behavior - Over-speeding	Vital	Not required.	Not required.
Driving Behavior - Phone Use	Vital	Not required.	Not required.
Vehicle Tagging	Not required.	Not required.	Vital

• Many SDK features are dependent on trip detection; therefore Location Permission is vital for every feature.

• The location permission must be granted for precise location. Once users give permission, the operating system provides precise location access. However, users can manually switch to 'approximate location.' In such cases, the SDK will not function, and an associated error is generated.

SDK Errors

Zendrive SDK provides the following permission errors to indicate high-priority permission needs:

Error	Description
'Always' Location Access	kZendriveSettingsErrorTypeLocationPermissionNotAuthorized
Precise Location	kZendriveSettingsErrorTypeLocationAccuracyAuthorizationReduced
Low Power Mode	The iOS SDK is generally not affected when the phone is in low power mode. However, there is a possibility of missing or terminating trips when the battery level becomes critical and the phone is turned off due to low battery.
Background App Refresh Disabled	This error does not affect Zendrive services but must be mandatorily provided.
Activity Permission	kZendriveSettingsErrorTypeActivityPermissionNotAuthorized

Handling Errors

We recommend acquiring permissions during the onboarding process that clearly explains why those permissions are needed.

If an error is thrown after the in-boarding process, a notification can indicate to the user that a specific permission is needed. Use that notification to direct them to the correct permission screen or a screen describing why the permission is needed.