On iOS 27, CPListItem.text and CPListImageRowItem.text` are rendered as single-line with ellipsis truncation, regardless of the available vertical space. On iOS 26 and earlier, these properties wrapped to 2 lines before truncating. There is no public API (numberOfLines, lineLimit, or similar) on CPListItem, CPListImageRowItem, or CPListSection to control the number of text lines. The change appears to be a platform-level rendering default with no app-side opt-out. Steps to Reproduce Create a CPListTemplate with sections containing CPListItem or CPListImageRowItem items. Set the text property to a string long enough to require wrapping. Present the template via CPInterfaceController. Run on iOS 27. Expected Results The text property should wrap to multiple lines (2-3 lines) before truncating with an ellipsis, consistent with iOS 26 behavior. Row height should adjust dynamically to accommodate the wrapped text. Actual Results The text property is truncated to a single line with ellipsis. Row height remains fixed at a larger size, creating excessive vertical spacing between items. Environment iOS 27.0 (CarPlay) - issue present Xcode 27.0 beta 4 (27A5218g) Tested on physical CarPlay head unit and CarPlay Simulator

Under Xcode 27 beta (27A5194q) the built-in CarPlay external screen from iOS simulator can be launched but shows an empty black screen every time on iOS27 device configurations. I have tested many different simulated devices (iPhone 17, 17 pro, 17 pro max) and different screen resolutions. Under iOS26.3 it works as expected. Is this a known issue? Is there any workaround or fix?

When using the new list section headers that include an image, title, subtitle, and action button (e.g., on playlist entity pages), the header remains fixed while the underlying content scrolls. This results in visual overlap between the header and list items, creating readability issues that can appear visually broken during interaction. Is this a known issue, and is there a workaround or fix planned?

I have questions about how the Video Now Playing experience for music apps is configured and what controls are available: Subtitles / Closed Captions — Does the Video NPV support subtitle or closed caption selection? Playback Speed — Is playback speed control surfaced in the CarPlay Video NPV UI? Playback Controls — Beyond play/pause and seek, what controls are available on the Video NPV? Fallback Behavior — When CPSessionConfiguration.supportsVideoPlayback becomes false mid-session (e.g., vehicle starts moving), how does the transition from video to audio-only Now Playing work? Is there a delegate callback, or should we observe supportsVideoPlayback via KVO? Configuration Scope — Is the video playback surface fully driven by AirPlay streaming + CPPlaybackConfiguration, or are there additional configuration points we should be aware of for controlling the video NPV experience?

Condensed grid items and circular grid images with transparent backgrounds render with a subtle border around their edges, creating unintended visual artifacts. Is this a known issue, and is there a workaround or fix planned?

The CPNowPlayingTemplate.upNextButtonEnabled property does not consistently hide the Up Next (queue) button when set to false at runtime. We can reproduce this reliably: Start playback of a playlist (queue is available, upNextButtonEnabled = true). Switch to AI DJ playback (queue is not applicable, set upNextButtonEnabled = false). The Up Next button remains visible on the Now Playing screen. The button only disappears after the user navigates away from and back to the Now Playing view. This appears to be a state refresh issue where the template does not re-render when the property is toggled during an active session. Is this a known issue? Is there a recommended workaround to force the Now Playing template to refresh its button visibility without requiring the user to navigate away? Should we be using a different mechanism to dynamically control the visibility of the Up Next button based on playback context?

Is there support (current or planned) for multiple navigation buttons in the top-right corner of CPNowPlayingTemplate? If multiple buttons are supported, what is the maximum number, and can they use icons instead of (or in addition to) text labels?

Is there a comprehensive list of all CarPlay framework changes in iOS 27 beyond what appears in the public release notes? Are there any new or updated CarPlay components in iOS 27 that are not yet reflected in the SDK headers or documentation?

CPListTemplateDetailsHeader supports action buttons for entity pages (e.g., playlist or album detail views). Currently, it appears that the header supports a limited number of trailing action buttons. What is the officially supported maximum number of action buttons on CPListTemplateDetailsHeader? If currently limited to one, is there a plan to support two action buttons to cover common media patterns like Play + Shuffle? Are there alternative patterns the team recommends for presenting multiple primary actions on entity pages within the current template constraints?

We've observed inconsistent behavior when users interact with CarPlay via physical hardware controls (rotary knobs, d-pads, and physical buttons) on various head units: Focus navigation through grid and list items can behave unpredictably when using the rotary encoder, particularly when scrolling through sections with mixed item types or transitioning between sections. Selection via the physical button/knob press sometimes does not register on the expected item, especially after rapid scrolling. Hardware back/menu button behavior doesn't always align with the template navigation stack in certain edge cases. Are there known issues with hardware control input handling in the current CarPlay SDK, particularly with grid templates? Are there best practices we should be implementing to improve hardware control responsiveness?

The current limit of 24 items per grid section forces us to split large collections (e.g., user playlists) across multiple sections, leading to layout inconsistencies across different screen sizes. List templates allow up to 200 items. Is there a plan to increase the grid item limit, or is there a recommended pattern for presenting larger collections in grid layouts?

Condensed grid sections currently use a fixed two-column layout. On larger or higher-resolution head units, this underutilizes the available screen real estate. Is there support (or planned support) for adaptive breakpoints that expand to three or more columns on wider displays?

When using trailing scroll arrows in grid layouts with multi-row sections, scrolling does not consistently behave as expected. In some cases, scrolling becomes stuck or moves in the reverse direction. We've been able to reproduce this across multiple apps. Has this been addressed or is a fix planned?