here is the simple sample code yielding constraint errors : UIBarButtonItem *button2 = [[UIBarButtonItem alloc] initWithImage:[UIImage systemImageNamed:@"heart"] style:UIBarButtonItemStylePlain target:self action:@selector(heartTapped:)]; self.navigationItem.rightBarButtonItem = button2; nothing crazy. FB20787440

this looks to be fixed in B4 !, thanks UIKit Devs!

Still an issue in beta 3

still an issue in ios 26.1 b2

still an issue in ios 26.1 b2

i should mention this is with a UITableView line separator

this looks to be fixed in beta 5! dont have xcode beta 5 yet to confirm that apps built against beta 5 look good, but apps built against beta 4 running on a device on beta 5 work as expected

bumping this, still an issue with Interface builder segmented controls in beta 4, I would prefer not to rewrite all my views to programmatically add a segmented control :)

i would submit a feedback! seems like it would be a bug to me, and i do see them same thing.

ive run into this same issue i think its an actual issue with the segment control in interface builder, ive submitted a feedback but you should as well! If you create the segmented control programmatically it functions fine.

submitted feedback with attached code snippet and system error popup: 15155625

same thing has been happening to me on the simulator, but device is fine

if you click the little +, you can edit your deployment target, by hand, both debug and release, granted looks like they removed the dropdown, but it can still be edited. Also if you goto target - build settings-> deployment you can see your value there and there is a dropdown for ios versions (but only whole version numbers) i suppose if you want to do something like 17.3 or something you'll need to type it in.

i would submit some Feedbacks we are seeing this with other SDK's the more feedbacks / info they have the more they can investigate, i have a feeling this is a xcode validation issue, for now im just ignoring them, i can still upload apps / deploy so its not a stopper, just annoying getting warnings

submitted a FB with same 'warning's' using SPM for a SDK. attached as much info as i could FB-15144843