Search results | Apple Developer Forums

Reply to Custom NSMigrationPolicy methods not invoked when NSMappingModel is created in code

I don't think building models at runtime has anything wrong, but that is not quite a common use case because folks typically use model files. Do you have a minimal project that demonstrates the issue? If you can share, I'd find time to take a closer look. Best, —— Ziqiao Chen  Worldwide Developer Relations.

App & System Services iCloud & Data

2w

Reply to Xcode shows alert about unknown com.apple.quicklook.preview extension point when running on Apple Vision Pro Simulator

I did a sanity check and looked in Xcode, in the templates for a new target, I don't see 'Quick Look Preview Extension' in the visionOS' list (I do see 'thumbnails'). Could it not be possible yet? That would explain why no issues when making the app 'designed for iPad'. I suppose the issue disappears if you remove vision as a target for the quick look extension.. but maybe you want the extension in visionOS as well. I read some more and I came to the conclusion that the Quick Look preview extensions are not yet for visionOS, but only someone from Apple can confirm that.

Developer Tools & Services Xcode

2w

Reply to xcodebuild -exportLocalizations Fails Due to Cross-Platform Dependencies

Thank you for the info! This doesn't seem to affect our normal build because the relevant watch packages don't depend on the libraries that aren't compatible. But for some reason when -exportLocalization flag is added, it attempts to build ALL targets for watch since that's declared as a platform at the top. This makes sense to me now. Xcode does indeed attempt to build each target in the package for all platforms listed in that package. The reason changing those build settings didn't work for you is because they would need to be set on the relevant package targets themselves (not the dependencies), but packages do not allow setting arbitrary build settings. Please file a Feedback report requesting that the Export feature avoid building package targets for platforms that their dependencies do not support. A sample project is helpful but not required since we now understand what the problem is.

Developer Tools & Services Xcode

2w

Reply to xcodebuild -exportLocalizations Fails Due to Cross-Platform Dependencies

Just want to confirm those build settings did not change anything. It seems like xcodebuild with the -exportLocalization flag runs every single target, for every platform listed, regardless of whether that target is actually using the target.

Developer Tools & Services Xcode

2w

PHPickerViewController unusable via Mac Catalyst on macOS 26 when interface is "Scaled to Match iPad"

There is a serious usability issue with PHPickerViewController in a UIKit app running on macOS 26 via Mac Catalyst when the Mac Catalyst interface is set to “Scaled to Match iPad”. Mouse click and other pointer interactions do not take place in the correct position. This means you have to click in the wrong position to select a photo and to close the picker. This basically makes it unusable. To demonstrate, use Xcode 26 on macOS 26 to create a new iOS app project based on Swift/Storyboard. Then update ViewController.swift with the following code: import UIKit import PhotosUI class ViewController: UIViewController { override func viewDidLoad() { super.viewDidLoad() var cfg = UIButton.Configuration.plain() cfg.title = Photo Picker let button = UIButton(configuration: cfg, primaryAction: UIAction(handler: { _ in self.showPicker() })) button.translatesAutoresizingMaskIntoConstraints = false view.addSubview(button) NSLayoutConstraint.activate([ button.centerXAnchor.constraint(equalTo: view.safeAreaLayoutGuide.cent

UI Frameworks UIKit macOS Mac Catalyst PhotoKit

11

0

468

2w

Reply to Metal is not installed on Xcode 26 on Xcode Cloud

We're seeing very inconsistent results with Xcode 26.0.1. Have this in our pre-build script: if xcodebuild -showComponent metalToolchain >/dev/null 2>&1; then echo Metal toolchain is installed Which reports that the toolchain is installed, but then ~50% of the time we get this error when building a metal file in our of our local Swift Packages: error: error: cannot execute tool 'metal' due to missing Metal Toolchain; use: xcodebuild -downloadComponent MetalToolchain Command CompileMetalFile failed with a nonzero exit code It was working fine every time with Xcode 26.0 but that was just deprecated last night so we can no longer use it. Xcode 26.0.1 (17A400) macOS Tahoe 26 (25A354)

Developer Tools & Services Xcode Cloud

2w

Reply to Stage Manager app icon in Xcode 26 macOS apps

Replying to my own post here. After further testing here is what I found to work on Xcode 26 with a macOS app project: Create a brand new project name/app. Add desired custom AppIcon.icon from Icon Composer to the Project/Target (pick well you won't be able to change it later) Peform the first compile/build/run of the app ever. Paradoxically, the custom icon will show in Stage Manager but not in the Dock or app switcher (Ctrl+Tab). Select “Include all app icon assets” in the project/target settings and Clean Build Folder/ReBuild/Run/Quit. Unset the “Include all app icon assets” and again Clean/Build/Run. The custom icon should now show in Stage Manager, Dock, and App Switcher. If you replace the AppIcon.icon file in the project it will show in Dock and App Switcher but not in Stage Manager. Further, replacing back the original custom AppIcon.icon in the project will not bring back the custom icon to Stage Manager, only to Dock and App Switcher, with just a generic blank icon in Stag

Developer Tools & Services Xcode

2w

The tunnel connection failed while the system tried to connect to the device.

Hello, I’m new to macOS after many years on iPhone, and I’m trying to run a simple app on my iPhone directly from Xcode. The app builds fine in the simulator, but deploying to a real device fails with this error: The tunnel connection failed while the system tried to connect to the device. Domain: com.apple.dt.CoreDeviceError Code: 4 Failure Reason: The tunnel connection failed while the system tried to connect to the device. User Info: { DVTErrorCreationDateKey = 2025-10-02 16:55:53 +0000; com.apple.dt.DVTCoreDevice.operationName = connect; } -- The tunnel connection failed while the system tried to connect to the device. Domain: com.apple.dt.RemotePairingError Code: 4 -- I get the same error via command line, e.g. for xcrun devicectl device info apps --device ... My setup: macOS Version 26.0.1 (Build 25A362) Xcode 26.0.1 (Build 17A400) iPhone 13 on iOS 26.0.1 iPhone is paired with the Mac (I can see it in Finder and in Xcode alongside the simulator). Developer Mode is enabled on t

Developer Tools & Services Xcode

0

111

2w

Reply to Build upload API not yet available?

@yanniks , it’s been available since the 4.1 release earlier this week https://developer.apple.com/documentation/appstoreconnectapi/build-uploads. The OpenAPI specification has also been updated with the new endpoints. https://developer.apple.com/documentation/appstoreconnectapi

App Store Distribution & Marketing App Store Connect API

2w

VNDocumentCameraViewController UI issues in iOS 26

We're observing several UI issues with VNDocumentCameraViewController on devices running iOS 26. These screens were functioning correctly in earlier iOS versions. Issue 1 - On the edge correction screen, the top bar now appears as a gray strip beneath the status bar, whereas in previous iOS versions, it was positioned at the bottom of the screen. Do we have any workarounds to address this issue? Issue2 - The edit buttons and their labels are not clearly visible, affecting usability. Im using XCode 16.4 to build to iOS26 and the usage is like below: `let scanner = VNDocumentCameraViewController() scanner.delegate = self self.present(scanner, animated: true)`

UI Frameworks UIKit iOS VisionKit

0

62

2w

Reply to DeclaredAgeRange import error in Mac Catalyst app

I’m not sure what you’re trying to convey with your latest reply. I’ve already: Explained that this is a bug. Recommend that you file a bug about it. Suggested a workaround that will at least allow your code to build. What else are you looking for? Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

App & System Services General

2w

Reply to Xcode shows alert about unknown com.apple.quicklook.preview extension point when running on Apple Vision Pro Simulator

Can you try deleting the phyical one and rely only on the info.tab? I don't see how, since the NSExtension plist key contains a nested structure. Inversely, can you de select from build settings the 'generate info.plist' and handle that fully manually? Not sure what that should change. Should I simply copy the generated contents into the Info.plist file? The error doesn't happen at compile time, but at installation time. What happens if you deliberately make the NSExtensionPointIdentifier 'wrong' like making a typo - do you get same error message? Same error message, now mentioning the updated NSExtensionPointIdentifier value.

Developer Tools & Services Xcode

2w

Reply to Embed/Do Not Embed & Mach-O type

Ah, I thought might be the case. The simulator works a bit like macOS, where Xcode sets things up so that your app can load a framework from the build products directory. That won’t work on a real device, where the framework must be embedded in the app’s bundle. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

Developer Tools & Services General

2w

Reply to Endpoint Security Frameworks SDK - Not foudn for download

It looks like you’re using Xcode to build an Endpoint Security system extension. If so, the following should work: In Xcode, create a new app project by choosing File > New > Project and selecting the macOS > App template. Once that’s set up, create a new Endpoint Security system extension target by choosing File > New > Target and selecting the macOS > Endpoint Security Extension template. Then do this: In the Project navigator on the left, select your project. In the Project editor — the middle pane of the Xcode window — select your Endpoint Security system extension target on the left. At the top, select the General tab. In the Frameworks and Libraries list, you’ll see libEndpointSecurity.tbd. That’s the stub library necessary to resolve the linker error you’re reporting. If you’re not familiar with the concept of a stub library, I explain that in An Apple Library Primer. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + ap

App & System Services Core OS

2w

Reply to TV A1625 Using 3× More CPU After tvOS 26 Update

Hi, yes your fully correct, its an app for tvOS We are media streaming VOD and live content. and only on the AppleTV A1625, we see thats there is an effect to the stream quality, and the only diffrent i can spot is the larger cpu usage(Other processes) and we have tried build on both the 26 and the 16.4. And we are using the AvPlayer to stream the content.

Media Technologies Streaming

2w

build disappears

Post

Replies

Boosts

Views

Activity