Apple released the fifth developer beta of iOS 27 on Friday and broke turn-by-turn guidance for every third-party navigation app on CarPlay. Google Maps, Waze, TomTom, and Sygic all fail to render the guidance template, showing a blank map panel with audio directions continuing. Apple Maps works. The cause appears to be a change in how CarPlay allocates rendering surfaces between the instrument cluster and the center display, part of the groundwork for the next generation CarPlay experience that ships in a handful of 2026 vehicles. Developers found out by installing the beta, because the release notes describe the underlying change in a single sentence that mentions no behavioral difference.
What changed technically
CarPlay apps render through a template system rather than drawing arbitrary content, which is why the interface looks consistent across apps and why Apple controls what is possible. Navigation apps use CPMapTemplate, which the system composites onto the vehicle display. In beta 5, the compositor moved to a model where the map surface is allocated per display rather than per app, and an app that does not declare which displays it targets receives none.
The declaration is a new entitlement key that appeared in beta 5 without documentation. Developers found it by inspecting the system frameworks, and adding it to an app's configuration restores the previous behavior on internal builds. The problem is that shipping apps in the App Store cannot add an entitlement key without a new submission, and a submission targeting an undocumented key will not pass review. So the fix exists and nobody can deploy it.
Why developers are frustrated beyond this bug
The specific breakage will be fixed. What developers described to us, repeatedly and with more heat than the situation alone justifies, is a pattern where CarPlay changes arrive in beta with no advance notice, no documentation, and no channel to raise concerns other than a feedback form that returns nothing. A senior engineer at one navigation company said his team learns about CarPlay changes the same way journalists do, and that planning around a platform that behaves this way is impossible.
The contrast with Apple's other platforms is stark. iOS API changes appear in the developer documentation at WWDC with migration guides and months of lead time. CarPlay gets a paragraph. The explanation most developers assume is that CarPlay's roadmap is tied to automaker agreements Apple cannot discuss, which makes advance disclosure genuinely difficult and does not explain the missing documentation once a beta ships.
The story is rarely the launch. It is what breaks, what ships, and who owns the mess at 2 a.m.
The next generation CarPlay context
Apple announced a deeper CarPlay integration in 2022 that takes over the instrument cluster and climate controls, and it has shipped in almost nothing. Aston Martin and Porsche implemented it in limited models. Most large automakers have declined, either because they want the dashboard for their own software and data or because the engineering integration is substantial and Apple's requirements are strict.
The display allocation change in beta 5 is consistent with that architecture, where multiple surfaces across multiple screens need coordination. Building it properly requires the changes Apple is making. The question is whether third-party apps get first-class treatment in the new model or whether the instrument cluster becomes Apple Maps territory. Apple has said navigation apps will be supported. Developers point out that the same was said about several CarPlay capabilities that never materialized.
What it means for drivers
Nothing immediately, since this is a developer beta that no ordinary user should be running. The public beta is expected in mid-August and Apple will almost certainly resolve this before then, either by restoring the previous behavior or by documenting the entitlement and letting apps update. iOS 27 releases in September alongside the new iPhones.
The longer-term concern for drivers is fragmentation. Android Auto and CarPlay have made phone-based navigation the default in most vehicles, and a growing set of automakers, including Tesla, Rivian, and increasingly GM, refuse to support either. GM's decision to drop CarPlay from its electric vehicles produced sustained customer complaints and the company has not reversed it. If Apple's platform becomes harder for third parties to support, the argument that automakers should build their own gets stronger.
How to track this
Developers with affected apps should file feedback with the beta build number and watch the release notes for beta 6, expected in about two weeks. Several have opened a coordinated thread on the Apple developer forums, which occasionally produces a response from a framework engineer and usually does not. Filing through a paid developer technical support incident has produced faster answers historically for issues this specific.
For anyone building on CarPlay, the operational lesson is to test every beta from the first one rather than waiting for release candidates. That is expensive and it is the only way to catch changes that arrive without documentation. Teams that maintain a dedicated test vehicle or a CarPlay simulator rig catch these in days. Teams that test at the end of the beta cycle find out when users do. The cost of that rig is a used vehicle head unit and a weekend of wiring, or about $400 for one of the commercial CarPlay development boxes, which is trivial against the support volume a broken navigation release generates. Several of the affected companies have one and did not have it powered on this week.
Skarvonix will keep following this beat with reporting grounded in how systems behave outside the launch keynote.
