Hi,
When launching my app on the iOS 18 simulator using Xcode 26 beta, the app crashes immediately with a missing symbol error:
dyld[23801]: Symbol not found: _NSUserActivityTypeBrowsingWeb
Referenced from: <DDBF5C50-BD0E-34C7-B202-888033A93840> /Users/username/Library/Developer/CoreSimulator/Devices/058F6615-9288-4164-8736-53CBC962FFD4/data/Containers/Bundle/Application/95B984C9-3197-423C-860C-E714BA34ACCB/MyApp.app/MyApp.debug.dylib
Expected in: <443671DB-41AE-3963-8403-E4A484837405> /Library/Developer/CoreSimulator/Volumes/iOS_22A3351/Library/Developer/CoreSimulator/Profiles/Runtimes/iOS 18.0.simruntime/Contents/Resources/RuntimeRoot/System/Library/Frameworks/CoreServices.framework/CoreServices
Symbol not found: _NSUserActivityTypeBrowsingWeb
Referenced from: <DDBF5C50-BD0E-34C7-B202-888033A93840> /Users/username/Library/Developer/CoreSimulator/Devices/058F6615-9288-4164-8736-53CBC962FFD4/data/Containers/Bundle/Application/95B984C9-3197-423C-860C-E714BA34ACCB/MyApp.app/MyApp.debug.dylib
Expected in: <443671DB-41AE-3963-8403-E4A484837405> /Library/Developer/CoreSimulator/Volumes/iOS_22A3351/Library/Developer/CoreSimulator/Profiles/Runtimes/iOS 18.0.simruntime/Contents/Resources/RuntimeRoot/System/Library/Frameworks/CoreServices.framework/CoreServices
dyld config: DYLD_SHARED_CACHE_DIR=/Library/Developer/CoreSimulator/Caches/dyld/24F74/com.apple.CoreSimulator.SimRuntime.iOS-18-0.22A3351/ DYLD_ROOT_PATH=/Library/Developer/CoreSimulator/Volumes/iOS_22A3351/Library/Developer/CoreSimulator/Profiles/Runtimes/iOS 18.0.simruntime/Contents/Resources/RuntimeRoot DYLD_LIBRARY_PATH=/Users/username/Library/Developer/Xcode/DerivedData/MyApp-dqwvveywparbascmmycuqktsiopv/Build/Products/Debug-iphonesimulator:/Library/Developer/CoreSimulator/Volumes/iOS_22A3351/Library/Developer/CoreSimulator/Profiles/Runtimes/iOS 18.0.simruntime/Contents/Resources/RuntimeRoot/usr/lib/system/introspection DYLD_INSERT_LIBRARIES=/Library/Developer/CoreSimulator/Volumes/iOS_22A3351/Library/Developer/CoreSimulator/Profiles/Runtimes/iOS 18.0.simruntime/Contents/Resources/RuntimeRoot/usr/lib/libLogRedirect.dylib:/Library/Developer/CoreSimulator/Volumes/iOS_22A3351/Library/Developer/CoreSimulator/Profiles/Runtimes/iOS 18.0.simruntime/Contents/Resources/RuntimeRoot/usr/lib/libBacktraceRecording.dylib:/Library/Developer/CoreSimulator/Volumes/iOS_22A3351/Library/Developer/CoreSimulator/Profiles/Runtimes/iOS 18.0.simruntime/Contents/Resources/RuntimeRoot/usr/lib/libMainThreadChecker.dylib:/usr/lib/libRPAC.dylib:/Library/Developer/CoreSimulator/Volumes/iOS_22A3351/Library/Developer/CoreSimulator/Profiles/Runtimes/iOS 18.0.simruntime/Contents/Resources/RuntimeRoot/usr/lib/libViewDebuggerSupport.dylib:/System/Library/PrivateFrameworks/GPUToolsCapture.framework/GPUToolsCapture DYLD_FRAMEWORK_PATH=/Users/username/Library/Developer/Xcode/DerivedData/MyApp-dqwvveywparbascmmycuqktsiopv/Build/Products/Debug-iphonesimulator DYLD_FALLBACK_FRAMEWORK_PATH=/Library/Developer/CoreSimulator/Volumes/iOS_22A3351/Library/Developer/CoreSimulator/Profiles/Runtimes/iOS 18.0.simruntime/Contents/Resources/RuntimeRoot/System/Library/Frameworks DYLD_FALLBACK_LIBRARY_PATH=/Library/Developer/CoreSimulator/Volumes/iOS_22A3351/Library/Developer/CoreSimulator/Profiles/Runtimes/iOS 18.0.simruntime/Contents/Resources/
Notes:
I have only tested on the iOS 18 simulator so far.
I have not yet tested on earlier iOS versions or physical devices.
The app runs fine on iOS 26 simulator using Xcode 26, so the crash seems specific to the iOS 18 simulator.
This looks like a system symbol that may not be linked properly in the iOS 18 simruntime.
Is this a known issue with the iOS 18 SDK or simulator runtime in Xcode 26 beta?
Thanks!
Xcode
RSS for tagBuild, test, and submit your app using Xcode, Apple's integrated development environment.
Selecting any option will automatically load the page
Post
Replies
Boosts
Views
Activity
I have been working on a project before this year's new OSX and Xcode update and I was able to build the project with little trouble. But since updating to any of the beta software, including the latest version of Tahoe 26.0 and Xcode26-beta4 I have not been able to build this same project. I have tried reseting package cache and updating to the latest package versions. As well I have deleted the derived data and cleaning the build folder. The following error output is one of 55 errors I am getting. It seems like the modules for the XRSimulator are redefinitions from those for MacOSX. I don't know how to limit or redirect the definition of the modules to just those for the XRSimulator (this is a VisionOS project). I also tried all of this on different betas of Xcode with all the same result. This bug is causing a problem with the 16.4 version of Xcode as well. I would really really appreciate anybody's help on this.
in file included from /Applications/Xcode.app/Contents/Developer/Platforms/XRSimulator.platform/Developer/SDKs/XRSimulator26.0.sdk/usr/include/module.modulemap:2:
Previously defined here : CommandLineTools/SDKs/MacOSX26.0.sdk/usr/include/AppleTextureEncoder.modulemap
Topic:
Developer Tools & Services
SubTopic:
Xcode
After upgrading to Xcode 16.4, the navigation arrow icon in the Report Navigator is no longer appearing for failed test cases within XCResult bundles. This icon, which allows developers to directly navigate to the specific line of code that caused a test failure, is now missing. This significantly hinders the debugging process for test automation engineers.
Details:
Xcode Version: 16.4 (issue started after upgrade)
Test Framework: XCTest
Test Environment: iOS simulators
Execution Method: The tests are executed on a Jenkins CI/CD server
XCResult Analysis: The generated .xcresult bundle is downloaded from the Jenkins server and opened locally on a Mac also running Xcode 16.4.
Observed Behavior:
The navigation arrow icon is missing, and there is no direct way to jump to the failure line from the report.
This issue appears to be a regression introduced in Xcode 16.4, as the navigation arrow was consistently present in previous versions. Any insights or workarounds would be greatly appreciated.
When the Icon Composer file is imported into the project folder, and after building, there is a warning that says:
Failed to parse icontool JSON output.
Parts of the warnings show this:
Entity: line 1: parser error : Start tag expected, '<' not found
\211PNG
^
Entity: line 1: parser error : Start tag expected, '<' not found
\211PNG
^
Entity: line 1: parser error : Start tag expected, '<' not found
\211PNG
^
/* com.apple.actool.notices */
warning: Failed to parse icontool JSON output.
Underlying Errors:
Description: The data couldn’t be read because it isn’t in the correct format.
Failure Reason: The data is not in the correct format.
Debug Description: Garbage at end around line 6, column 0.
/* com.apple.actool.compilation-results */
I have created the icon with png files in each layer group in icon composer.
However the project is able to compile, and running shows the correct icon.
What is the issue with this?
Getting a weird build failure with Xcode 26 beta 5 that I haven't seen before. Build works fine locally but fails in CI when building with xcodebuild with this error:
build description signature: 7cb0bf47dd6decc14090f5ae23d66594
Build description path: /Users/user/Library/Developer/Xcode/DerivedData/ProjectName-dpklhpaqruhpwdbkihszqtqogzfb/Build/Intermediates.noindex/XCBuildData/7cb0bf47dd6decc14090f5ae23d66594.xcbuilddata
error: Failed to decode version info for '/Applications/Xcode-beta.app/Contents/Developer/usr/bin/actool': The data couldn’t be read because it is missing. (stdout: '<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>
<key>com.apple.ibtool.version</key>
<dict>
<key>bundle-version</key>
<string>24118.1</string>
<key>short-bundle-version</key>
<string>26.0</string>
</dict>
</dict>
</plist>
', stderr: ''
The thing is, the data is definitely there - actool is outputting valid XML:
<key>com.apple.ibtool.version</key>
<dict>
<key>bundle-version</key>
<string>24118.1</string>
<key>short-bundle-version</key>
<string>26.0</string>
</dict>
But xcodebuild keeps saying it's missing. This error repeats like 15 times in the build log.
Build command:
set -o pipefail && xcodebuild -workspace "ProjectName/ProjectName.xcworkspace" -scheme "ProjectNameDeviceTests" -configuration "Debug" -destination "generic/platform=iOS" -resultBundlePath "Build for device/result_bundle.xcresult" -verbose TREAT_WARNINGS_AS_ERRORS=YES
COMPILER_INDEX_STORE_ENABLE=NO -IDEBuildLocationStyle=Custom -IDECustomBuildLocationType=Absolute -IDECustomBuildProductsPath="$PWD/test_package" OTHER_SWIFT_FLAGS='${inherited} -Xfrontend -debug-time-function-bodies -Xfrontend -debug-time-expression-type-checking'
SWIFT_COMPILATION_MODE=wholemodule clean build-for-testing
The issue seems to come and go, sometimes cleaning the derived data and/or reset helps, sometimes it doesn't.
Anyone else hitting this? Seems like a parsing bug in the beta where it can't read its own version info properly.
Topic:
Developer Tools & Services
SubTopic:
Xcode
I am trying to solve an issue when converting an existing project to use Buildable Folders:
Our current project have some custom file types that have specialized build rules, as described here:
https://developer.apple.com/documentation/xcode/creating-build-rules-for-custom-file-types
We previously added each of these file types, to the target's Compile Sources phase and everything was running well.
Now we wish to move these files into a Buildable Folder, but I cannot find a way to make it work ... as only files with a specific file extensions are ever built in a Buildable Folder, and despite having a custom rule for this file type, it seems like Xcode never runs the rule.
Is there some way to tell Xcode to treat specific extensions in a Buildable Folder as source extension?
Topic:
Developer Tools & Services
SubTopic:
Xcode
I'm having a problem with Xcode 26 where a symbol bug is causing my app to crash at launch if they are running iOS 17.X
This has to do with a HealthKit API that was introduced in iOS 18.1 HKQuantityType(.appleSleepingBreathingDisturbances), I use availability clauses to ensure I only support it in that version. This all worked fine with Xcode 16.4 but breaks in Xcode 26.
This means ALL my users running iOS 17 will get at launch crashes if this isn't resolved in the Xcode GM seed.
I'll post the code here in case I'm doing anything wrong. This, the HealthKit capability, the "HealthKit Privacy - Health Share Usage Description" and "Privacy - Health Update Usage Description", and device/simulator on iOS 17.X are all you need to reproduce the issue.
I've made a feedback too as I'm 95% sure it's a bug: FB19727966
import SwiftUI
import HealthKit
struct ContentView: View {
var body: some View {
VStack {
Image(systemName: "globe")
.imageScale(.large)
.foregroundStyle(.tint)
Text("Hello, world!")
}
.padding()
.task {
print(await requestPermission())
}
}
}
#Preview {
ContentView()
}
func requestPermission() async -> Bool {
if #available(iOS 18.0, *) {
let healthTypes = [HKQuantityType(.appleSleepingBreathingDisturbances)]
var readTypes = healthTypes.map({$0})
let write: Set<HKSampleType> = []
let res: ()? = try? await HKHealthStore().requestAuthorization(toShare: write, read: Set(readTypes))
guard res != nil else {
print("requestPermission returned nil")
return false
}
return true
}
else { return false}
}
We are trying to track down some build failures that started happening only in our Jenkins CI environment.
error: Failed to decode version info for '/Applications/Xcode.app/Contents/Developer/usr/bin/actool': The data couldn’t be read because it is missing.
(stdout: '<?xml version="1.0" encoding="UTF-8"?>
[2025-07-30T19:21:18.479Z] <!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
[2025-07-30T19:21:18.479Z] <plist version="1.0">
[2025-07-30T19:21:18.479Z] <dict>
[2025-07-30T19:21:18.479Z] <key>com.apple.ibtool.version</key>
[2025-07-30T19:21:18.479Z] <dict>
[2025-07-30T19:21:18.479Z] <key>bundle-version</key>
[2025-07-30T19:21:18.479Z] <string>24112</string>
[2025-07-30T19:21:18.479Z] <key>short-bundle-version</key>
[2025-07-30T19:21:18.479Z] <string>26.0</string>
[2025-07-30T19:21:18.479Z] </dict>
[2025-07-30T19:21:18.479Z] </dict>
[2025-07-30T19:21:18.479Z] </plist>
[2025-07-30T19:21:18.479Z] ', stderr: ''
Key facts we've noted:
Locally I cannot reproduce the problem
We did not see this problem with previous Xcode 26 betas
If I remote into the machine and run build commands from the command line I cannot reproduce the problem
The very first build succeeds, every build after that on this machine fails from jenkins
actool --version is spitting out the version information for ibtool, but only in the context of running from a jenkins agent. If I run this locally or if I remote into the CI machine and run this from the terminal I cannot reproduce this behavior.
Command line tools appear to be installed, xcode-select --install fails if I try to do it from the command line.
We've tried to recreate the build agents for this jenkins environment exactly as they were for all previous betas and xcode versions, and still get this behavior.
Xcode 26 Beta 5 XIB Compiler outputs NIBs with dependency on class that isn't available pre-macOS 26
When Xcode 26 Beta 5 compiles my XIBs into NIBs, it spits out a dependency on a class that isn't available pre-macOS 26, named _TtCC6AppKit14NSScrollPocketP33_EC3F85FAB7755D56E669206D2B17725B12BackdropView.
All XIBs have a deployment target of macOS 12, so in theory this should be avoided. Even if this is a new (internal) class to macOS 26, the dependency is a problem when the developer is asking to deploy to prior versions.
Has anyone else run into this regression? What could possibly be causing the XIB compiler to inject this dependency? The resulting NIBs don't load on anything prior to macOS 26.
Hi there, can anyone help here. I think somewhere along the way I ***** certificates or don't have the right one, anyway long story short when building product I get this error: Embedded binary is not signed with the same certificate as the parent app. Verify the embedded binary target's code sign settings match the parent app's.
Hi All,
I'm new to IOS development/Xcode and would appreciate any/all advice/guidance on this unexplainable issue. Please excuse my potential usage of wrong terms.
I have a project that was handed to me in a near completed state and there is a UI bug in the program that I am trying to fix. It is opening multiple instances of a View Controller Scene in the wrong dimensions, causing instanced layers that act independently of each other rather than a simple "page re-routing" like regular front end development.
Upon investigating the codebase I have noticed the following potential source:
The storyboard was originally modeled after an IPhone 16 Pro Max, however the main device we will be creating the app for is an iPad 11 mini. Upon changing the simulated device, the view models for most of my XXXViewControllerScenes are not rendering the correct size.
Here are some examples:
Image1 ) When selecting the RootNavController (scene 1) > all storyboard scenes render the correct size (at least thats what it visually looks like). When clicking on the "Type Select View Controller" or the View within the "Type Select View Controller Scene" (scene 2) the view models remain the correct size.
Image2) However when clicking into the View for "Order Start View Controller Scene" - this causes the View and SafeArea renders for all scenes(except the RootNav)to shrink and not be the correct size equal to the simulated device:
This also persists, where previosly my Scene 2 which was the correct size, is now the incorrect size no matter what I do. The only way I have found to work around this is to re-select my RootNavController to render all scenes the proper size, then individually click the components I'm trying to edit in the Document Outline panel and tweak them manually on the Attribute Editor. Not to mention this makes setting constraints extremely hard as the elements render "off screen"
What I have checked so far:
Ensure all my ViewControllerScene's Attribute Editor > Simulated Metric > Size = Inferred
Unchecked "Use Preferred Explicit Size" for all ViewControllerScene's Attribute Editor > Simulated Metric > Content Size - 1 thing to note here is some of them have a set size of 744x1133 (when they render the full size) but it changes to 580x640 (when it shrinks) even though the option is UNCHECKED?
Circling back to the UI Bug in my app, when I segue to the next Scene, the pages end up loading in the shrinked dimension.
Please help me identify what is causing this issue and how to fix it or refer me to some guides that can assist.
I'm using IB to create an NSOutlineView.
I configure it:
[_outlineView setStyle:NSTableViewStyleSourceList]
I put it in an NSSplitView.
What I get is an old-style sidebar with a VisualEffect background and no rounded rect border.
My company's app has a few widgets and a couple of them we do not want to show up on CarPlay due to safety concerns when iOS 26 releases. I understand Apple's recommended way to prevent users from using your widget in CarPlay is to use the .disfavoredLocations([.carPlay], for: [.systemSmall]), and this puts your widget in the 'Other' section of the widgets.
https://developer.apple.com/download/files/CarPlay-Developer-Guide.pdf
However, this .carPlay widget location is only available in Xcode 26, and our app cannot be built on Xcode 26 yet due to some build errors. We are able to fix those build errors in a separate branch, but we won't be doing our official release builds on Xcode 26 until it is out of beta, which is usually right before iOS 26 officially releases to general audiences. We release our app versions on a monthly cadence, so the version that will be out when iOS 26 comes out is already in testing.
Is there any existing way we can disable this widget on CarPlay so it does not appear to work when tapped? Currently, it opens our CarPlay app, but the CarPlay app does nothing with it. On the iPhone, when you tap the widget it opens our app and performs a function.
We don't wan't to disable it on the iPhone, just when it's on CarPlay. We don't have time before the app release to implement the same functionality on our CarPlay app. I haven't found any reliable way to detect if the widget is running in the CarPlay location versus the iPhone home screen.
Thanks in advance for any assistance.
I'm unable to download the Metal toolchain with Xcode. When trying to do it via the command line, I get the following:
> xcodebuild -downloadComponent metalToolchain -exportPath /tmp/MyMetalExport/
Beginning asset download...
2025-08-06 19:46:19.983 xcodebuild[1395:22024] Writing error result bundle to /var/folders/48/1k1jfsxn56zcs4qr_719rc1w0000gn/T/ResultBundle_2025-06-08_19-46-0019.xcresult
xcodebuild: error: Failed fetching catalog for assetType (com.apple.MobileAsset.MetalToolchain), serverParameters ({
RequestedBuild = 17A5295f;
})
From Console.app:
DVTDownloadsFetchAssetCatalog() complete assetType (com.apple.MobileAsset.MetalToolchain), options: (MADownloadOptions allowsCellular: 0 resourceTimeout: 60 canUseCacheServer: 0 discretionary: 0 disableUI: 0 sessionId: (null) additionalServerParams:{ RequestedBuild = 17A5295f; } allowsExpensiveAccess:1 requiresPowerPluggedIn: 0 prefersInfraWiFi: 1 liveServerOnly: -1 DownloadAuthorizationHeader: not present analyticsData: not present allowDaemonConnectionRetries: 0), result: (59), catalogError: (Download failed due to not being able to find the host. (Catalog download for com.apple.MobileAsset.MetalToolchain))
Note that I am online. I've tried restarting my computer and Xcode and using a different network.
How to configure the Imported Type Identifiers of a document based app so that it can open any possible UTType? (i.e. it is a generic tool like a text editor or a hex editor that is supposed to be able to open any file).
Thank you!
Topic:
Developer Tools & Services
SubTopic:
Xcode
The Apple documentation is from the 10.6 era and appears to be not correct for the modern OS. I have the help book prepared as a html document. What needs to be done to take this html document (html text and in the same directory a directory with all the image files. In Firefox the html document displays correctly. What modifications are necessary for the html document? And where do I lace this in the application bundle?
Topic:
Developer Tools & Services
SubTopic:
Xcode
I use Carthage to build a set of dependencies. I generate .xcframework files with code for both macOS and iOS. This works through Xcode 26 beta 4. With Xcode 26 beta 5, the resulting .xcframework files seem to have code only for iOS, not macOS. Each framework has a ios-arm64 directory and a ios-arm64_x86_64-simulator directory, but no macos-arm64_x86_64 directory.
This is affecting 3 of my 7 cross-platform dependencies that I compile with Carthage. What those 3 seem to have in common is that each has one target and scheme for the shared library – instead of one for iOS and another for macOS.
I may have to create a second scheme and target in each of these dependencies, or move to SPM. But I am wondering if anyone has another suggestion.
Thank you.
John
I'm experiencing an issue here on my Xcode 16.4, where i can't download the supported iOS 18.6 runtime because it stays stuck on the 'preparing' state. I have also tried getting it manually from the dev site but they only have 18.2. The only runtime that would download easily via Xcode was 17.5 but I can't build my project with that.
I have tried using curl to even get a download url, nothing worked.
All my terminal approach didn't work also.
Any help or guidance to sort this out?
Thank you.
Hi everybody!
I am pretty new to app development.
I started by creating an app and linking it to Firebase as DB. I had added them directly on Xcode (File>Add Package Dependencies>...). Then I needed one specific package that was not there, so I started using cocoapods (all from the terminal), but it didn't work. When I deleted the ones from cocoapods (I am not 100% sure I deleted everything I had to), I started using the packages in the first way, but now it doesn't even build with the packages I have. I checked many times and I actually have those packages, but it does not work at all.
Any suggestions on how to solve it or who I could contact?
Thanks.
Topic:
Developer Tools & Services
SubTopic:
Xcode
why xcode has no option to fold all
Topic:
Developer Tools & Services
SubTopic:
Xcode