I noticed something weird yesterday in beta 6, (it could have been in earlier betas) but if you kill an app, then immediately try to open it, (sometimes it takes a few times) the app will crash. I can duplicate it on pretty much every app, including the feedback app, Chase etc. Its as if killing it doesnt fully kill it and causing sometime of network crash. I cant duplicate it in iOS14 at all so im thinking its something on how apps are "killed" (or not killed) in ios 15. I also cant get it to happen on iPadOS15 just iOS15. Weirdness.

Is anyone having 'oddness' with ios 17.4 b1 either not calling delegate - (UIInterfaceOrientationMask)supportedInterfaceOrientations or simply ignoring it. For example apps that are locked in portrait (but do have to support rotation at different parts of the app) seem to be freely be able to rotate even on places it shoudnt. Im freely allowed to rotate the youtube app for example in landscape, at the main screen, not just on the video player. Im seeing this in other apps to that are locked portrait. But if you kill the app, and restart the app then it will not rotate. something funky was changed or a bug. ive never seen this before in ios 17.0 - 17.3

After hitting the Red (X) to close simulators in xcode b3 , ios 15 simulators is anyone else getting crashes related to the "AppleAccount.framework" I submitted a feedback just curious if its just me. I thought maybe in the "re" release of b3 it might be fixed, but still seems to be crashing. The simulator itself is perfectly fine, just crashes when closing.

Im not sure if its just my comp (2019 iMac 16gb of ram) but opening the simulator takes about 10 min, then to just open an app on the simulator takes about 6 min, im curious if its just me, but this is crazy.

hey all today for some reason im getting Unsupported SDK or Xcode version valdation failure when uploading to app store connect. I haven't changed anything and i was able to upload jsut a few days ago with same version of xcode. Its xcode 16.0 anyone else getting this? Maybe its a server side issue?

Hey all wondering if anyone has seen this new in xcode 26 beta 2 it seems any NIBS with a UISwitch will 'error' saying please submit a feed back and attach the log, i did submite a feedback but looking at the log it simply says : the tool closed the connection (IBAgent-iOS) then if you just build again it builds fine and runs fine, but if you switch from simulator to device and build the error will happen again, but same thing build again and it works. I opened my NIBS with the switch and they open just fine, no errors or anything so im wondering if its something in the build system. For any xcode engineers here: here is my feedback number 18348463

Hey all when building my app on xcode 26 beta 3 im getting a new warning about a [APPNAME]-primary-bridging-header.pch no file or directory found, this warning is new to beta 3 for me, obviously if i turn precompile headers off in build settings the warning goes away so there is a work around, but figured ide let the xcode engineers know ! (maybe its just me, but i wouldnt think so) Again this is just a warning and not stopping the build but wanted to see if this is a new warning anyone else is getting. Thanks ! FB18710327 Ps - ive tried the usuals .. clean build, delete derived data get same warning :)

Hey All, Curious if you guys are seeing the same thing for those who are using Interface Builder Files (Xib) i set the line seperator to none and on my app (built against ios 18 on the app store, but doesnt matter if i build it against ios 26, or ios 26.1) when running on iOS 26.1 the line seperator will show even when i set it to None. Funny enough if i just play around with the XIB file and set it to single line and maybe RED color the IB file will show it but when running it its the same old default dark greyish color. BUT if i set the line seperator in CODE either to be none or with single line + red it looks good when running on sim / device. So it seems to be an issue with XIB files not being respected in iOS 26.1 (only) i have submitted a feed back FB20466783, hope this helps any xcode devs / uikit devs. thank you !

I know we can usually ignore these but was curious if any others are getting the same 'warnings' when simply pushing a new view controller from the navigationcontroller: UINavigationBar not configured causing _hasInlineSearchBar to return NO even if an inline search bar is present. Using the UISearchController's traitCollection instead. navigationBar = (null) 2022-09-14 15:45:31.203252-0400 TestingApp[32429:1274680] [Assert] UINavigationBar not configured causing _hasInlineSearchBar to return NO even if an inline search bar is present. Using the UISearchController's traitCollection instead. navigationBar = (null)  find it odd i dont use a search bar / controller at all. I submitted a feedback, but i dont think i can set _hasinlinesearchbar, i think that is private api. Ill just ignore them for now :)

there seems to be an issue with transparency in the simulator present in beta 5, didnt see this in the other betas, anyone else having this issue? im on a Intel Mac.

Trying to download the latest's SDKS (iOS and WatchOS) DVTDownloadableErrorDomain Code:41 Has anyone been able to download the new sdk's for xcode?

Hey all in iOS26.1 i seem to be getting a bunch of Constraint errors when setting the rightBarButtonItem leftBarButtonItem. Unable to simultaneously satisfy constraints. Probably at least one of the constraints in the following list is one you don't want. Try this: (1) look at each constraint and try to figure out which you don't expect; (2) find the code that added the unwanted constraint or constraints and fix it. (Note: If you're seeing NSAutoresizingMaskLayoutConstraints that you don't understand, refer to the documentation for the UIView property translatesAutoresizingMaskIntoConstraints) ( "<NSAutoresizingMaskLayoutConstraint:0x6000021a2a30 h=--& v=--& _TtCC5UIKit19NavigationButtonBar15ItemWrapperView:0x13d84c080.width == 0 (active)>", "<NSLayoutConstraint:0x6000021a1cc0 _TtCC5UIKit19NavigationButtonBar15ItemWrapperView:0x13d84c080.leading == _UIButtonBarButton:0x106cd3ed0.leading (active)>", "<NSLayoutConstraint:0x6000021a1d10 H:[_UIButtonBarButton:0x106cd3ed0]-(0)-| (active, names: '|':_TtCC5UIKit19NavigationButtonBar15ItemWrapperView:0x13d84c080 )>", "<NSLayoutConstraint:0x6000021a19f0 'IB_Leading_Leading' H:|-(2)-[_UIModernBarButton:0x106cc80b0] (active, names: '|':_UIButtonBarButton:0x106cd3ed0 )>", "<NSLayoutConstraint:0x6000021a1a40 'IB_Trailing_Trailing' H:[_UIModernBarButton:0x106cc80b0]-(2)-| (active, names: '|':_UIButtonBarButton:0x106cd3ed0 )>" ) Will attempt to recover by breaking constraint <NSLayoutConstraint:0x6000021a1a40 'IB_Trailing_Trailing' H:[_UIModernBarButton:0x106cc80b0]-(2)-| (active, names: '|':_UIButtonBarButton:0x106cd3ed0 )> Make a symbolic breakpoint at UIViewAlertForUnsatisfiableConstraints to catch this in the debugger. The methods in the UIConstraintBasedLayoutDebugging category on UIView listed in <UIKitCore/UIView.h> may also be helpful. Curious if im setting something wrong, or maybe i can just ignore these (granted they are annoying in my logs) This wasnt happening in iOS 26.0

Im thinking maybe there was a internal flag not removed or something. Not only do i have the version number on the icon (which is new to me, and i kinda like it). But within XCode it says Apple Internal. is it just me?.

when presenting an uialertviewcontroller either an actionsheet or alert it seems to have some weird interaction with my tableview cells. For example, i have custom font sizes a user can set so when im loading my cell i set the font size. It looks good on load but the second i preset a uialertviewcontroller it 'reset's all the cells to the default interface builder set fontsize. Some cells i use attributed text programmatically and that all gets reset as well to 'default' interface builder label settings. Its very odd. this is in iOS 18 b1. Funny enough it seems like every beta 1 (if i recall maybe in iOS 17 or iOS 16) it did the same thing there attributed text would like 'reset' its very odd. I have a hunch this is a bug and filed a feedback, but curious if there are any workarounds, or simply just wait until its fixed :D . Thanks all !

Hey All,i noticed something in my app using iOS 13.4 B2, this was not occuring on iOS 13.4 b1 or any previous iOS versions . The delegate methodtextFieldShouldBeginEditing is being called twice now when i return NO after giving focus to the textfield (i dont want the keyboard to appear over my action sheet). Normally this is only called once so showActionSheet is only called once, but now its called twice and calls showactionsheet twice, which is obviously not what we want. as 2 action sheets will show up one after the other. Anyone else seeing anything similiar with double delegate calls? Thanks !- (BOOL)textFieldShouldBeginEditing:(UITextField *)textField{ if(textField==myTextField2){ [myTextField1 resignFirstResponder]; [self showActionSheet]; return NO; } return YES; }