Can an iOS CarPlay app reliably identify the active head unit to enable features on approved units only?

We’re developing, an iOS navigation app with CarPlay support, for a managed vehicle fleet. We want to enable certain in-app features only when the application is running on an approved physical CarPlay head unit. The allowlist needs to distinguish individual units, including several units of the same make and model. The same iPhone may be used in both approved and unapproved vehicles.

This application already uses CPTemplateApplicationSceneDelegate to detect when its CarPlay scene connects or disconnects. The scene’s persistentIdentifier is scoped to the UIKit scene session. We’re looking for a stable identity that we can reliably associate with the head unit hosting the current CarPlay session.

  • Is there a supported iOS API or Apple-approved entitlement that lets a third-party navigation app identify the currently active physical CarPlay head unit? Ideally, the identifier would persist across reconnects and be available over both wired and wireless CarPlay.

  • If this requires manufacturer cooperation, is an iAP2 protocol exposed through ExternalAccessory and EASession the recommended approach? Can the app reliably determine that the EAAccessory it is communicating with is the same head unit hosting the current CarPlay session, or would the manufacturer need to provide that binding in firmware?

  • Can an existing third-party navigation app use this integration with an OEM partner, or is it reserved for apps published by the vehicle manufacturer? Which entitlement or Apple program would apply?

The use case is to gate specific features inside this application while keeping the standard CarPlay experience available. We can request the required entitlements and work with the hardware vendor if needed. Any guidance on the supported integration path or the appropriate Apple team to contact would be appreciated.

If this requires manufacturer cooperation, is an iAP2 protocol exposed through ExternalAccessory and EASession the recommended approach? Can the app reliably determine that the EAAccessory it is communicating with is the same head unit hosting the current CarPlay session, or would the manufacturer need to provide that binding in firmware?

Yes, using ExternalAccessory framework is the way to achieve this, and requires cooperation with the vehicle's manufacturer. Although your app cannot directly associate the provided EAAccessory instance with the CarPlay session, because only a single CarPlay session is supported by iOS at a time, the presence of an EAAccessory that matches your expected vehicle criteria (manufacturer, model, supported ExternalAccessory protocol names) is a very strong indicator that it is associated with the current CarPlay session. If you need additional authentication, you can build that over a custom ExternalAccessory protocol with the vehicle. You also can file a feedback for an enhancement request that CarPlay framework provides an API to retrieve the associated EAAccessory for that CarPlay session.

Can an existing third-party navigation app use this integration with an OEM partner, or is it reserved for apps published by the vehicle manufacturer? Which entitlement or Apple program would apply?

Yes, this can be supported by apps not from the vehicle's manufacturer, with approval by that manufacturer. Work with the vehicle's manufacturer to check the MFi program for guidance.