iOS 17.5: Permission Required for Barometer Data

Released on May 13th, iOS 17.5 now includes new criteria for applications using Barometer data as part of the ‘Relative Altitude updates’ section of iOS Motion data.

The Zendrive SDK uses barometer data as a part of the collision detection algorithm to detect airbag deployment. While the collision detection functionality does not stop working if barometer data is not available, there may be a marginal drop in ability to detect collisions accurately.

Any app built for iOS 17.5 must include the NSMotionUsageDescription flag in its Plist file upon submission. If this flag is present, the OS will display a pop-up seeking user permission the first time the SDK queries barometer data.

Refer to the snapshot below:

Following are the scenarios to consider:

• If an existing app already has the NSMotionUsageDescription flag in the info.plist file There is no change since users would have already encountered and approved or denied the permission.

• If an existing app does not have the NSMotionUsageDescription flag in the info.plist file When the end user upgrades to iOS 17.5, the SDK stops receiving barometer data without causing an app crash. Collision detection performance may slightly degrade but remains functional. Update: The apple app store has been rejecting apps that have code to read the Barometer data but do not have NSMotionUsageDescription flag set. So this scenario will not occur in the field.

• If a new app is build for iOS 17.5 with Zendrive SDK and does not include the flag in the info.plist file The app will crash. Update: Apple play store will reject the app.

• If a new app is build for iOS 17.5 with Zendrive SDK and includes the NSMotionUsageDescription flag in the info.plist file, but the user denies permission There will be no app crash. Collision detection performance may slightly degrade but remains functional.

Zendrive Recommends:

1. Customers with the NSMotionUsageDescription flag in their info.plist file do not have to make any changes. However, users using the SDK's collision detection feature might experience performance impacts if they deny the 'Motion and Activity' permission. The Zendrive SDK already includes checks for this permission in both the SDK settings change callback and API. We recommend that developers check for this permission and address accordingly.

2. Customers that do not have the NSMotionUsageDescription flag in the info.plist file have the following options: - Customers not using collision detection and prefer not to request for ‘Motion and Activity’ permission must not update their app to iOS 17.5 until they integrate Zendrive's new SDK 10.1, slated for release in June. - Customers using collision detection and are willing to obtain the Motion and Activity permission can proceed with their current integration and build the app for iOS 17.5. However, they must include the NSMotionUsageDescription flag with the appropriate notification text in the info.plist file. For further details, refer to the iOS integration page.

Please see SDK 10.1 release notes for more details on how this is handled.