1.App build using xCode 26 beta 4 crashing on run time on iOS device with iOS < 26.0 but works fine on iOS 26 beta devices. 2. Works fine if build using xCode 16.2 Runtime Crash Dump 
dyld[67519]: Symbol not found: _NSUserActivityTypeBrowsingWeb Referenced from: /private/var/containers/Bundle/Application/2D4B24D6-CEA5-4682-B549-9CCB6A56BAB9/Foreground Camera.app/Foreground Camera.debug.dylib Expected in: <050203DD-7488-307D-A999-E587314B041A> /System/Library/Frameworks/CoreServices.framework/CoreServices Symbol not found: _NSUserActivityTypeBrowsingWeb Referenced from: /private/var/containers/Bundle/Application/2D4B24D6-CEA5-4682-B549-9CCB6A56BAB9/Foreground Camera.app/Foreground Camera.debug.dylib Expected in: <050203DD-7488-307D-A999-E587314B041A> /System/Library/Frameworks/CoreServices.framework/CoreServices dyld config: DYLD_LIBRARY_PATH=/usr/lib/system/introspection DYLD_INSERT_LIBRARIES=/usr/lib/libLogRedirect.dylib:/usr/lib/libBacktraceRecording.dylib:/usr/lib/libMainThreadChecker.dylib:/usr/lib/libRPAC.dylib:/usr/lib/libViewDebuggerSupport.dylib:/System/Library/PrivateFrameworks/GPUToolsCapture.framework/GPUToolsCapture Symbol not found: _NSUserActivityTypeBrowsingWeb Referenced from: /private/var/containers/Bundle/Application/2D4B24D6-CEA5-4682-B549-9CCB6A56BAB9/Foreground Camera.app/Foreground Camera.debug.dylib Expected in: <050203DD-7488-307D-A999-E587314B041A> /System/Library/Frameworks/CoreServices.framework/CoreServices dyld config: DYLD_LIBRARY_PATH=/usr/lib/system/introspection DYLD_INSERT_LIBRARIES=/usr/lib/libLogRedirect.dylib:/usr/lib/libBacktraceRecording.dylib:/usr/lib/libMainThreadChecker.dylib:/usr/lib/libRPAC.dylib:/usr/lib/libViewDebuggerSupport.dylib:/System/Library/PrivateFrameworks/GPUToolsCapture.framework/GPUToolsCapture

In our project, we defined a CustomTabBar that inherits UITabBar, and we add some subviews and these subviews' frame is beyond UITabBar, see below picture(a beyond area button, this button is a subview of UITabBar, but frame is out of UITabBar's area): and in order to let this button response to click action, we override the UITabBar's hitTest method, this works well below OS 26 with Xcode version below 26: override public func hitTest(_ point: CGPoint, with event: UIEvent?) -> UIView? { let pointInCollectionView = self.beyondAreaButton.convert(point, from: self) if self.beyondAreaButton.bounds.contains(pointInCollectionView) { return self.beyondAreaButton.hitTest(pointInCollectionView, with: event) } return super.hitTest(point, with: event) } but when using Xcode26 build app on OS 26, I noticed the UITabBar is wrapped by a UIKit._UITabBarContainerView and UIKit._UITabBarContainerWrapperView, and it can not trigger the hitTest method. since the hitTest is not triggered, so the button action is no chance to trigger too. Any suggestions to solve this problem, thank you~ And I have file a feedback assistant: FB19252973

Using the #Playground macro in beta 3 worked fine, but the Playgrounds package appears to be missing in beta 4. import Playgrounds #Playground { print("🚀 Playground is active") } Canvas error message: Cannot find playgrounds Check whether the playground is compiled for the current scheme and OS of the selected device. There could be compile time checks filtering playgrounds out. Check for dead code stripping or other settings that could exclude playgrounds from the final binary.

I’ve noticed that Xcode keeps automatically adding unnecessary inputPaths and outputPaths entries to my project.pbxproj file. These outputPaths don’t seem to serve any real purpose in my project and clutter the project file, sometimes causing unnecessary merge conflicts in version control. I’ve already checked I didn't change my project.pbxproj file, but Xcode still occasionally generates these outputPaths. I’m not using any custom build tools or plugins that should be modifying this. One thing I’ve observed is that this issue only occurs when Xcode is open. If I close Xcode, the problem does not happen. This makes me think it might be related to how Xcode manages or updates the project file in the background. My questions: Is there a way to completely disable Xcode from generating these outputPaths automatically? Are there any hidden settings, project configurations, or best practices to prevent this behavior? Has anyone else experienced this issue, and how did you resolve it? Any advice or insight would be greatly appreciated. Thank you!

This bundle is invalid. The IPA format requires a top-level directory named Payload, containing only a .app bundle and optional plugins in a Plugins directory. (ID: df59dbe4-17e5-4bc6-9c69-8645672320(4))

During regular use, RealityKit generates an excessive amount of internal logging that is not actionable by third party developers. When developing an iOS RealityKit/ARKit app, this makes the Xcode console challenging to use for regular work. (FB19173812) See screenshots below. Xcode does have an option for filtering out logging from specific SDKs, but enabling this feature to suppress the logging of RealityKit and related SDKs like PHASE is something developers have to do dozens of times each day. After a year of developing a RealityKit app, this process becomes frustrating. If SDKs like Foundation, UIKit, and SwiftUI generated as much logging as RealityKit and related SDKs, Xcode's console would be unusable. Is there any way to disable the logging of RealityKit and PHASE permanently? Thank you for any help you provide.

Hi everyone, I’m currently unable to view crash logs in Xcode Organizer for any of the apps in my account. When I try to access crash reports, I receive the following error: "An error occurred preventing Xcode from downloading version information from App Store Connect. An unexpected error occurred: [<__NSDictionaryM> valueForUndefinedKey:]: this class is not key value coding-compliant for the key [App Name] [Version] (iOS App)." The error message references an app name and version that were previously used. Notably, the original app name included an @ symbol (e.g., @ExampleApp). We suspected this might be contributing to the issue, so we updated the app name to remove the symbol. However, the error persists and still references the old name. Has anyone experienced something similar or found a workaround? Any guidance would be greatly appreciated! Thanks in advance.

Hey everyone, Just wanted to share a critical issue we’ve encountered while testing our app on iOS 18 simulators and devices using Xcode 26 Beta 3: Crash Details We're seeing the following fatal exception during launch: NSInvalidUnarchiveOperationException Could not instantiate class named _TtGC5UIKit17UICoreHostingViewVCS_21ToolbarVisualProvider8RootView_ because no class named _TtGC5UIKit17UICoreHostingViewVCS_21ToolbarVisualProvider8RootView_ was found... The crash originates from Storyboards/XIBs that include a UIToolbar. It appears UIKit is referencing an internal SwiftUI-related class (UICoreHostingView), which isn't present at runtime — leading to immediate crashes. Affected: Apps using UIToolbar in Storyboards or XIBs Running on iOS 18 (Simulators or Devices) and below Built using Xcode 26 Beta 3 CrashLog: Fatal Exception: NSInvalidUnarchiveOperationException 0 CoreFoundation 0x11a21c __exceptionPreprocess 1 libobjc.A.dylib 0x31abc objc_exception_throw 2 CoreFoundation 0x178ea0 -[NSException initWithCoder:] 3 UIFoundation 0x28774 UINibDecoderDecodeObjectForValue 4 UIFoundation 0x28a18 UINibDecoderDecodeObjectForValue 5 UIFoundation 0x28cac -[UINibDecoder decodeObjectForKey:] 6 UIKitCore 0x21e680 -[UIView initWithCoder:] 7 UIKitCore 0x9b4784 -[UIToolbar initWithCoder:] 8 UIFoundation 0x28890 UINibDecoderDecodeObjectForValue 9 UIFoundation 0x28cac -[UINibDecoder decodeObjectForKey:] 10 UIKitCore 0x1e3a80 -[UIRuntimeConnection initWithCoder:] 11 UIFoundation 0x28890 UINibDecoderDecodeObjectForValue 12 UIFoundation 0x28a18 UINibDecoderDecodeObjectForValue 13 UIFoundation 0x28cac -[UINibDecoder decodeObjectForKey:] 14 UIKitCore 0x1e87dc -[NSCoder(UIIBDependencyInjectionInternal) _decodeObjectsWithSourceSegueTemplate:creator:sender:forKey:] 15 UIKitCore 0x1e2ea4 -[UINib instantiateWithOwner:options:] 16 UIKitCore 0x9f96c -[UIViewController loadView] 17 UIKitCore 0x75da8 -[UIViewController loadViewIfRequired] 18 UIKitCore 0x14430 -[UIViewController view] 19 UIKitCore 0x4237bc -[UINavigationController _preferredContentSizeForcingLoad:] 20 UIKitCore 0x116b15c -[_UISheetPresentationMetrics formSheetSizeForViewController:windowSize:screenSize:] 21 UIKitCore 0xb5c60c -[UIViewController _formSheetSizeForWindowWithSize:screenSize:] 22 UIKitCore 0x546ebc -[_UISheetLayoutInfo _preferredSize] 23 UIKitCore 0x18da60 -[_UISheetLayoutInfo _isEdgeAttached] 24 UIKitCore 0x19d428 -[_UISheetLayoutInfo _margins] 25 UIKitCore 0x19ce88 -[_UISheetLayoutInfo _stackAlignmentFrame] 26 UIKitCore 0x211018 -[_UISheetLayoutInfo _fullHeightUntransformedFrame] 27 UIKitCore 0x18f39c -[_UISheetLayoutInfo _untransformedFrame] 28 UIKitCore 0x188350 -[UISheetPresentationController _containerViewLayoutSubviews] 29 UIKitCore 0x18f1fc -[UITransitionView layoutSubviews] 30 UIKitCore 0x26070 -[UIView(CALayerDelegate) layoutSublayersOfLayer:] 31 QuartzCore 0x14c14 CA::Layer::layout_if_needed(CA::Transaction*) 32 UIKitCore 0x16b78 -[UIView(Hierarchy) layoutBelowIfNeeded] 33 UIKitCore 0x186f4c -[UISheetPresentationController presentationTransitionWillBegin] 34 UIKitCore 0x3187b4 -[_UIFormSheetPresentationController presentationTransitionWillBegin] 35 UIKitCore 0x185dd0 __80-[UIPresentationController _initViewHierarchyForPresentationSuperview:inWindow:]_block_invoke 36 UIKitCore 0x1874f8 __77-[UIPresentationController runTransitionForCurrentStateAnimated:handoffData:]_block_invoke_3 37 UIKitCore 0x8584c -[_UIAfterCACommitBlock run] 38 UIKitCore 0x85784 -[_UIAfterCACommitQueue flush] 39 UIKitCore 0xa254 _runAfterCACommitDeferredBlocks 40 UIKitCore 0x9f74 _cleanUpAfterCAFlushAndRunDeferredBlocks 41 UIKitCore 0x9e84 _UIApplicationFlushCATransaction 42 UIKitCore 0x9e0c __setupUpdateSequence_block_invoke_2 43 UIKitCore 0x9404 _UIUpdateSequenceRun 44 UIKitCore 0x8ab4 schedulerStepScheduledMainSection 45 UIKitCore 0x41e4 runloopSourceCallback 46 CoreFoundation 0xfa8c __CFRUNLOOP_IS_CALLING_OUT_TO_A_SOURCE0_PERFORM_FUNCTION__ 47 CoreFoundation 0xf8a4 __CFRunLoopDoSource0 48 CoreFoundation 0xf700 __CFRunLoopDoSources0 49 CoreFoundation 0x10080 __CFRunLoopRun 50 CoreFoundation 0x11c3c CFRunLoopRunSpecific 51 GraphicsServices 0x1454 GSEventRunModal 52 UIKitCore 0x135274 -[UIApplication _run] 53 UIKitCore 0x100a28 UIApplicationMain 54 Saleslink DEV 0x1f9ea8 main + 17 (AppDelegate.swift:17) 55 ??? 0x1af61bf08 (Missing) Would love to know if anyone else has encountered this, or if there’s an official radar or feedback ID we can follow. Hoping this gets resolved before the GM release of Xcode 26. Thanks!

After updating to Xcode 26 Beta 4, I can no longer upload my app to App Store Connect due to a WatchKit icon validation error. The error states: Invalid Icon. The watch application 'YourApp.app/Watch/YourWatchApp.app' contains an icon file 'Icon Image-AppIcon-watch-1024x1024 @1x.png' with an alpha channel. Icons should not have an alpha channel. • This file name doesn’t exist in the asset catalog or project source. • All icon assets used in the Watch App’s AppIcon set, including the required 1024x1024 icon, were checked with sips -g hasAlpha and confirmed to not contain an alpha channel. • Project was cleaned, derived data cleared, and archive recreated multiple times. • This issue only began after updating to Xcode 26 Beta 4. In the previous versions, everything was ok. Is anyone else experiencing this after upgrading Xcode to Beta 4? Any idea/workaround on how to solve this would be appreciated.

Hello guys, I’ve been recently trying to learn how to implement in app purchases and in every tutorial they create store kit configuration file but in my Xcode there is no such option - I even uninstalled my Xcode and installed 16.4 release version - still missing And when I try to create this file manually, naming it something.storekit I get “The operation couldn’t be completed. (IDEStoreKitEditor.IDEStoreKitEditorConfigurationError error 0)” but such error isn’t documented anywhere :( Few people mentioned that restarting Xcode fixes the problem for them, but that is not the case for me, I'm having this problem on both Xcode 16.3 and 16.4 and nothing seems to fix it - it's really frustrating Any help is greatly appreciated

In the last three betas of Xcode 26, opening XIB files that rely on the older struts-and-springs setup (rather than Auto Layout) has exposed a new problem: Xcode 26 ignore the difference between a view’s frame and alignment rectangle. If you had arranged views using their frame rectangle (the default for the old method) this causes two problems: All UI widgets are both larger and no longer aligned. Switching between frame and alignment rectangles while configuring any NSView (through the inspector setting) has no effect. Is anyone else seeing this? It’s one thing to convert a few smaller views to Auto-layout (its reliance on alignment rectangles makes it immune to the "death" of frame rectangle-based layout) it is a rather different task to re-layout thousands of UI widgets as a result of this one bug. Filed as FB18835363

I'm not seeing the Accessibility or Attributes Inspectors in Xcode 26. Were these features removed? Xcode 16 Xcode 26

Has anyone else discovered that Xcode 26 will not open any files that aren’t code? None of my project’s Storyboard, Launch Screen, Assets, built targets, Info plist will open when I click them in the Project Navigator… I just get a blank white screen in the main pane. They still exist, however: I can build my project just fine, using the pre-existing configurations and Storyboard.

 I’ve discovered a workaround, such as it is: I can open my project back in Xcode 16 to edit my Storyboard, and then open it once again in Xcode 26 to build the project. This works, but as you can imagine, it’s a PITA. I’m also not able to access any Xcode 26 improvements to the Interface Builder, if there are any.

 Has anyone else experienced this? Or even fixed it? I can report it as a bug but I'm surprised that I haven't even found anyone else encountering this yet.

Does anyone have this issue of Xcode 26 Beta 4 crashing on closing of their project? Currently running on macOS 26 Beta 4 on a MacBook Air M2 with 16GB of ram. Each time i close a project, Xcode 26 Beta 4 will crash. The window pops up to send a report. Opening Xcode 26 Beta 4 will reopen the previous project. If you have multiple projects opened, all these projects will always reopen.

I run otool from a script (actually from a program) and find it annoying that otool fails if I need to agree to a new version of the Xcode and SDKs license. Is there a way to test ahead of time whether this will happen, or detect when this problem occurs, so that I can display a dialog to tell me what I need to do? This happened after upgrading from macOS Tahoe beta 1 to beta 3.

When I build the app, a block symbol appears on the app icon in the Debug Area at the bottom. What is the reason for this?

I've been messing around with converting my app icons to use Icon Composer. My app has multiple app icons, but I've noticed that I cant seem to set .icon files using the alternate app icon api. I believe this is due to the requirement that alternate app icons live in the Assets Catalogue but .icon files go anywhere in your project. Is there any plan to support this? Or am i missing something? I was able to successfully set a .icon file for the primary app icon.

I am missing device support for IOS 18.5 in xcode. I tried installing xcode 16.4, xcode 16.4 beta and xcode 26 beta 2 but none of them generated folder for 18.5. Is this happening only for me or everyone. Please provide me 18.5 folder if anyone has it. I would appreciate a lot.

Tap to Pay capabilities are enable and I can use in development profile but I cannot make build that I can upload on TestFlight using the distribution profile because during create build I am getting "Provisioning profile doesn't support the Tap to Pay on iPhone capability." this should be working because I checked twice that distribution profile and certificate have this capability and added in Xcode. how can I resolve this mismatched profile issue I am using Xcode - 15.0.1

Hi everyone, I’m testing our SwiftUI app on both Xcode simulator and a real iPhone. On the simulator, everything looks clean and aligned. But when I run it on an actual iPhone (same build, iOS 18), the layout looks broken—fonts overlap, spacing is off, and elements are misaligned. Both screenshots are from the exact same screen and time. First is simulator, second is iPhone. Any idea why this difference happens? Is there something I should check in terms of rendering or layout settings? Thanks in advance!