An app with a UIToolbar pinned to the bottom of a view controllers view extends to the screen edge (behind the safe area) when run on iOS 18.X but not iOS 26. This UIToolbar is set as constrained to the safeAreaLayoutGuide with the following constraints. self.view.addConstraints([ bottomToolbar.leadingAnchor.constraint(equalTo: self.view.leadingAnchor), bottomToolbar.trailingAnchor.constraint(equalTo: self.view.trailingAnchor), bottomToolbar.bottomAnchor.constraint(equalTo: self.view.safeAreaLayoutGuide.bottomAnchor), bottomToolbar.heightAnchor.constraint(greaterThanOrEqualToConstant: 44.0) ]) This is especially noticeable when the UIToolbar background color differs from the view background color. This occurs on iOS 26 beta 6, app built with Xcode 26 beta 5. I've posted a Feedback FB19664903 including a minimal Xcode workspace that reproduces this issue. Anyone suggestions would be appreciated ... this definitely seems like a regression.

An iOS app has a UINavigationController with a UINavigationBar that is non-translucent (e.g. black). When performing a push (or pop) to navigate to or from another UIViewController the UIBarButtonItems on the navigation bar are flashing a white background. With a dark navigation bar this is very noticeable and not desirable. This only occurs when run on iOS 26 and is related to Liquid Glass I've created FB19660024 with a minimal Xcode workspace to reproduce, along with a video showing the behavior. This is a cosmetic bug, not affecting functionality, but is a very undesirable effect on apps with dark and non-translucent navigation bars. Has anyone else seen this and found a workaround?

An app built on Xcode 26 (beta4) presents various UIViewCOntrollers. Presentation of any UIViewController that contains a UIToolbar leads to a UIKit crash when run on an iOS 18.5 device, it does not crash when run on iOS 26. The exception logged: *** Terminating app due to uncaught exception 'NSInvalidUnarchiveOperationException', reason: 'Could not instantiate class named TtGC5UIKit17UICoreHostingViewVCS_21ToolbarVisualProvider8RootView because no class named TtGC5UIKit17UICoreHostingViewVCS_21ToolbarVisualProvider8RootView was found; the class needs to be defined in source code or linked in from a library (ensure the class is part of the correct target)' Anyone else seen this? I've submitted a bug report via Feedback Assistant, including a minimal Xcode workspace that reproduces the crash, hoping this will get some attention.

A UISegmentedControl as a UIBarButtonItem (customView) is ignoring selectedSegmentTintColor on iOS 26, works fine on prior versions I've submitted FB19660941 with a minimal Xcode workspace to reproduce the issue. Has anyone else seen this and identified a workaround?

Hello, I'm creating a widget to display some data for a selected account (from a larger list of accounts). A dynamic intent allows the user to select the account to display in the widget from this list. I have this working just fine. I'd like to allow the Medium version of this widget to display 2 selected accounts, and a Large widget to display 4 selected accounts. From WWDC video I thought I could enable the Array (Supports multiple values) property of the parameter in the intent definition, with Fixed Sizes set to Small=1, Medium=2, Large=4. For example, the user could configure the 2 accounts to display on a Medium widget, the 4 accounts to display on the Large widget, etc THE PROBLEM: Whenever I specify an Array type for the single account selection parameter, it appears Springboard crashes when the user goes to add an initial instance of the widget to the Home screen, i.e. I can long-press and click + to get to the widget gallery ... but within moments this screen goes blank (with a spinner) and resets back to lock screen. As soon as I turn off the Array property of the parameter, it goes back to working correctly but without the desired configurability. QUESTION: Are Array parameters supposed to work with WidgetKit?