Post

Replies

Boosts

Views

Activity

CPInformationTemplate shows empty bottom action bar on iOS 26.4 even when no buttons are provided
Hi, After updating to iOS 26.4, we noticed a change in the behavior of CPInformationTemplate in CarPlay. Previously, when creating a CPInformationTemplate with an empty array of CPTextButton (no actions), the bottom action bar was not displayed. However, on iOS 26.4, an empty horizontal bar is now always shown at the bottom, even when no buttons are provided. Example: let item = CPInformationItem(title: "Some item...", detail: "") let template = CPInformationTemplate( title: "Bug demo", layout: .twoColumn, items: [item], actions: [] ) Expected behavior: No bottom bar when there are no actions. Actual behavior on iOS 26.4: An empty bottom bar is always visible. Questions: Is this an intentional change in CarPlay UI behavior? Is there any way to hide the action bar when there are no buttons? Are developers now expected to always provide at least one action? This change negatively affects layouts where the template is used for loading or informational states without actions. Thanks.
0
0
14
5h
CPInformationTemplate shows empty bottom action bar on iOS 26.4 even when no buttons are provided
Hi, After updating to iOS 26.4, we noticed a change in the behavior of CPInformationTemplate in CarPlay. Previously, when creating a CPInformationTemplate with an empty array of CPTextButton (no actions), the bottom action bar was not displayed. However, on iOS 26.4, an empty horizontal bar is now always shown at the bottom, even when no buttons are provided. Example: let item = CPInformationItem(title: "Some item...", detail: "") let template = CPInformationTemplate( title: "Bug demo", layout: .twoColumn, items: [item], actions: [] ) Expected behavior: No bottom bar when there are no actions. Actual behavior on iOS 26.4: An empty bottom bar is always visible. Questions: Is this an intentional change in CarPlay UI behavior? Is there any way to hide the action bar when there are no buttons? Are developers now expected to always provide at least one action? This change negatively affects layouts where the template is used for loading or informational states without actions. Thanks.
Replies
0
Boosts
0
Views
14
Activity
5h