Tesla is considering adding support for Apple Wallet car keys in the near future.
Analysis of the most recent Tesla App version (v4.52.0) uncovered code hinting at a forthcoming feature: Harmony Wallet Key Cards. This development suggests a possible integration with Apple Wallet keys, indicating a significant advancement in Tesla's capabilities.
A recent analysis of the latest Tesla App version 4.52.0 has unveiled coding that alludes to a potential forthcoming feature: Harmony Wallet Key Cards.
While initially suggesting a move towards supporting Apple Wallet keys, the focus seems to be directed specifically towards the Chinese market, leveraging Huawei's HarmonyOS ecosystem. Tesla traditionally introduces features in the Chinese market first, indicating a possibility of native support being extended to Apple and Android in the future.
The Findings
Specific code segments in version 4.52.0 explicitly mention a Harmony Wallet Key Card. This indicates a potential integration with the Huawei Wallet, allowing HarmonyOS device users to directly incorporate their Tesla keycard into their phone's system-level wallet.
This functionality, known as a "native" car key, enables a smartphone to function as a secure key card (NFC) or proximity key (Bluetooth/UWB) without the Tesla app needing to run continuously in the background. It also provides additional functionalities such as Tap-to-Unlock and deeper system-level integration.
While Tap-to-Unlock is currently available on Android devices, it operates only when the device is powered on. System-level integration could facilitate key usage on iOS devices even when the phone is powered off.
Considering Huawei's prominent position in China and the recent emphasis on NearLink in the country's automotive sector, as seen in vehicles like the Huawei/Seres AITO M9, this strategic move aligns with Tesla's focus on its largest international market.
Keeping Pace
The timing of this discovery is significant as it contrasts sharply with Tesla's competitors in North America. In a recent development, Rivian introduced its 2025 Holiday Update (2025.46), integrating native digital key support for Apple Wallet and Google Wallet.
Rivian's implementation adheres to the Car Connectivity Consortium (CCC) standard, offering various advantages over a conventional app-based Bluetooth key. These benefits include functionality for up to 5 hours after the battery dies, secure sharing via iMessage, WhatsApp, and Airdrop, and native watch support without requiring a dedicated watch app.
Demand for Apple & Google Integration
Tesla owners have long requested native Apple and Google Wallet support. While Tesla's proprietary Phone Key is generally dependable, it depends on the app continuously running in the background, which can occasionally be disrupted or halted by the phone's operating system to conserve battery life.
A native wallet key is considered the optimal solution for digital vehicle access as it resides in a phone's secure elements and operates independently of the app's status.
The presence of Harmony Wallet code in the app indicates Tesla's capability and willingness to develop these integrations. The question that remains is whether this focus is exclusively on China or if it signals forthcoming Apple and Google Wallet support on the horizon.
While initially suggesting a move towards supporting Apple Wallet keys, the focus seems to be directed specifically towards the Chinese market, leveraging Huawei's HarmonyOS ecosystem. Tesla traditionally introduces features in the Chinese market first, indicating a possibility of native support being extended to Apple and Android in the future.
The Findings
Specific code segments in version 4.52.0 explicitly mention a Harmony Wallet Key Card. This indicates a potential integration with the Huawei Wallet, allowing HarmonyOS device users to directly incorporate their Tesla keycard into their phone's system-level wallet.
This functionality, known as a "native" car key, enables a smartphone to function as a secure key card (NFC) or proximity key (Bluetooth/UWB) without the Tesla app needing to run continuously in the background. It also provides additional functionalities such as Tap-to-Unlock and deeper system-level integration.
While Tap-to-Unlock is currently available on Android devices, it operates only when the device is powered on. System-level integration could facilitate key usage on iOS devices even when the phone is powered off.
Considering Huawei's prominent position in China and the recent emphasis on NearLink in the country's automotive sector, as seen in vehicles like the Huawei/Seres AITO M9, this strategic move aligns with Tesla's focus on its largest international market.
Keeping Pace
The timing of this discovery is significant as it contrasts sharply with Tesla's competitors in North America. In a recent development, Rivian introduced its 2025 Holiday Update (2025.46), integrating native digital key support for Apple Wallet and Google Wallet.
Rivian's implementation adheres to the Car Connectivity Consortium (CCC) standard, offering various advantages over a conventional app-based Bluetooth key. These benefits include functionality for up to 5 hours after the battery dies, secure sharing via iMessage, WhatsApp, and Airdrop, and native watch support without requiring a dedicated watch app.
Demand for Apple & Google Integration
Tesla owners have long requested native Apple and Google Wallet support. While Tesla's proprietary Phone Key is generally dependable, it depends on the app continuously running in the background, which can occasionally be disrupted or halted by the phone's operating system to conserve battery life.
A native wallet key is considered the optimal solution for digital vehicle access as it resides in a phone's secure elements and operates independently of the app's status.
The presence of Harmony Wallet code in the app indicates Tesla's capability and willingness to develop these integrations. The question that remains is whether this focus is exclusively on China or if it signals forthcoming Apple and Google Wallet support on the horizon.
