I have added an App Intents Extension target to my main application in macOS. This generated the below two files: TWAppIntent.swift import AppIntents struct TWAppIntent: AppIntent { static var title: LocalizedStringResource = TWAppIntentExtension static var parameterSummary: some ParameterSummary { Summary(Get information on (.$TWType)) } //launch app on running action static var openAppWhenRun: Bool = true // we can have multiple parameter of diff types @Parameter(title: TWType) var TWType: String func perform() async throws -> some IntentResult & ReturnsValue & ProvidesDialog { return .result(value: TWType, dialog: Logged break.) } } TWAppIntentExtension.swift import AppIntents @main struct TWAppIntentExtension: AppIntentsExtension { } I m able to build the extension target and I my intent action is available in the shortcuts app. However, on launching a shortcut with the above created intent action. I m getting the below popups: I have identified what is causing this error. Setting the
Search results for
build disappears
49,243 results found
Selecting any option will automatically load the page
Post
Replies
Boosts
Views
Activity
I have an iOS app with a QuickLook extension. I also added Apple Vision Pro in the target's General > Supported Destinations section. About one year ago, I was able to run the app on iPhone, iPad and Apple Vision Pro Simulators. Today I tried running it again on Apple Vision Pro with Xcode 26.0.1, but Xcode shows this error: Try again later. Appex bundle at ~/Library/Developer/CoreSimulator/Devices/F6B3CCA8-82FA-485F-A306-CF85FF589096/data/Library/Caches/com.apple.mobile.installd.staging/temp.PWLT59/extracted/problem.app/PlugIns/problemQuickLook.appex with id org.example.problem.problemQuickLook specifies a value (com.apple.quicklook.preview) for the NSExtensionPointIdentifier key in the NSExtension dictionary in its Info.plist that does not correspond to a known extension point. I tried again later a couple times, even after running Clean Build Folder Immediately, without any change. I can reproduce this with a fresh Xcode project to which I add a Quick Look Preview Extension and Apple Vision Pro
I wanted to remove AdMob from my iOS app, so I remove all traces of AdMob, and make sure that info.plist does not have NSUserTrackingUsageDescription, no external framework used, and no traces of NSUserTrackingUsageDescription in my codes (global search in Xcode not found). However, previous version has setup App Privacy in AppStore Connect. Uploading a new build I can remove all entries in App Privacy except for one (?): Data Types - 1 data type collected from this app: Product Interaction And I cannot remove this one: when selecting not collecting info, I got this error message: Your app contains NSUserTrackingUsageDescription, indicating that you will request permission to track users. You must indicate which data types are tracking users. If this is incorrect, update your app binary and upload a new build to App Store Connect. What shall I do? And what is this Product Interaction tracking? (The rest can all be reset to not tracking except this one.)
@xcc-developer I filed a feedback request and attached the Xcode Cloud diagnostics that contain the build logs. The feedback request number is FB20676007
Topic:
Developer Tools & Services
SubTopic:
Xcode Cloud
Tags:
Hello! Could you file a feedback report in Feedback Assistant and attach the built app products? You can find the built products in Xcode’s Derived Data folder, to which you can navigate by selecting Product > Show Build Folder in Finder from Xcode’s menu bar. Please include details about the specific target device or simulator that’s experiencing the issue and reply to this thread with the feedback ID so that we can follow up. Thanks!
Topic:
App Store Distribution & Marketing
SubTopic:
General
Tags:
Hello. I need to develop for iOS 18. I've recently updated Xcode and it says I have to download ios 26 platform. I don't need it, but I can no longer build my existing projects against ios 18, even though Xcode says it's still installed and used 13 days ago. How to I remedy this?
I’m integrating the Declared Age Range feature to tailor our app’s experience based on a user’s age range. I’m currently in the testing phase and would like to repeatedly test the consent flow and different outcomes from AgeRangeService.shared.requestAgeRange(...). However, once I go through the consent flow and choose to share, the age-range sharing sheet no longer appears on subsequent attempts—so it’s hard to validate edge cases (e.g., changed gates, declined flow, re-prompt behavior). Could you advise on the recommended way to reset or re-prompt during development? In particular: Is there a supported way to clear per-app consent so the system prompts again? Under what conditions should the “Share Age Range Again” control appear in Settings, and is there an equivalent way to trigger it for testing? Are there best practices for QA (e.g., using Ask First at the system level, testing on real devices vs. Simulator, using a separate bundle ID for dev builds, or other steps)? Any other guidance for vali
Is there a supported way to clear per-app consent so the system prompts again? There is no supported way to achieve the desired functionality given the currently shipping system configurations. If you would like for Apple to consider adding support for such features, please submit your suggestion request via Feedback Assistant. For more information on Feedback Assistant, please visit https://developer.apple.com/bug-reporting. Under what conditions should the “Share Age Range Again” control appear in Settings, and is there an equivalent way to trigger it for testing? It appears prior to the anniversary of the original request, and when a user previously declined or a user has aged out of a current age range. Are there best practices for QA (e.g., using Ask First at the system level, testing on real devices vs. Simulator, using a separate bundle ID for dev builds, or other steps)? Testing in the Simulator is unsupported. If you use a separate bundle ID, the system treats it as a different app. Any othe
Topic:
App & System Services
SubTopic:
General
Tags:
Part 2... That leads to here: and how can I make sure my app will be allowed to update when I need it too. The first thing I'd do here is shift the way you're thinking about this issue from how do I remove/bypass quarantine to how do I make sure my update process always works. You've focussed on quarantine because it's a fairly common edge case; however, the problem with focussing on solving it is: The system’s behavior is opaque and undocumented. This means, as you're already experiencing, it's hard to make this work right at all, and even if you succeed, it's very likely that something will change in the future, leaving you back with the same problem. Quarantine is only one failure source of many. For example, what if the actual problem is that the app is being run from a read-only location like a network share? That second point is what makes this problem so tricky. The full range of valid macOS configuration is so large that it's effectively impossible to fully test or predict. This means you end up trapp
Topic:
Safari & Web
SubTopic:
General
I have 2 app store connect apps: .beta This is necessary for our usecase as we are building an iOS blockchain wallet, for a chain that updates itself every ~3 months adding new features/changing. We need the communities input, and can't have them uninstalling/re-installing the production app constantly, having to re-import private keys, etc. So we use 1 app store connect app for production releases, and another for public facing long running beta, where we experiment with new features before pulling them into production. Allowing users to have both installed at the same time Last week my CI (without any changes to scripts, project, profiles, etc), started failing for the production build with the error: [altool.105176BE0] Validation failed (409) This bundle is invalid. The bundle identifier cannot be changed from the current value, '.beta'. If you want to change your bundle identifier, you will need to create a new application in App Store Connect. (ID: ae60bab4-0c01-4b2e-9ea9-91a73adccc14)
Hello Apple Team, We’re building a CloudKit-enabled Core Data app and would like clarification on the behavior and performance characteristics of Binary Data attributes with “Allows External Storage” enabled when used with NSPersistentCloudKitContainer. Initially, we tried storing image files manually on disk and only saving the metadata (file URLs, dimensions, etc.) in Core Data. While this approach reduced the size of the Core Data store, it introduced instability after app updates and broke sync between devices. We would prefer to use the official Apple-recommended method and have Core Data manage image storage and CloudKit syncing natively. Specifically, we’d appreciate guidance on the following: When a Binary Data attribute is marked as “Allows External Storage”, large image files are stored as separate files on device rather than inline in the SQLite store. How effective is this mechanism in keeping the Core Data store size small on device? Are there any recommended size thresholds or known lim
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
I have an AppleTV app which I released in 2016. I've updated it and released a new version every year without much hassle. This year, with tvOS 17.2, the layered app icon isn't working right. This is a two-layer image made with PNGs. When it's selected, it looks right and the layers move correctly: But when it's not selected, the background layer disappears: Screenshots are from the simulator but it also happens on the device. It's inconsistent; sometimes it's the front layer that disappears. Occasionally both layers work, but I can't tell why. I've spent a day trying everything. Very frustrated. The icon previews correctly in Xcode and in Parallax Viewer. The image sizes are correct: 400 x 240 for Small, 800 x 480 for Small@2x, 1280 x 768 for Large. The back layer is a non-transparent PNG. I tried adding a Large@2x set. Didn't help. Originally I had a three-layer image with no middle layer PNG. I deleted the empty middle layer, but that didn't help. All the PNG files are from GnuIMP. Same c
Hello everyone, I’m a new developer still learning as I go. I’m building a simple watchOS app that tracks Apple Watch battery consumption, records hourly usage data, and uses that information to predict battery life in hours. I’ve run into an issue where background refresh completely stalls after charging and never recovers, regardless of what I do. The only way to restore normal behavior is to restart the watch. Background refresh can work fine for days, but if the watch is charging and a scheduled background refresh tries to run during that period, it appears to be deferred—and then remains in that deferred state indefinitely. Even reopening the app or scheduling new refreshes doesn’t recover it. Has anyone else encountered this behavior? Is there a reliable workaround? I’ve seen a few reports suggesting that there may be a regression in scheduleBackgroundRefresh() on watchOS 26, where tasks are never delivered after certain states. Any insights or confirmations would be greatly appreciated. Thank
Under iPadsOS 26.0 and 26.1, if a view controller is presented with a presentation style of fullScreen or pageSheet, and the view controller is setup with a UISearchController that has obscuresBackgroundDuringPresentation set to true, then when cancelling the search the view controller is being dismissed when it should not be. To replicate, create a new iOS project based on Swift/Storyboard using Xcode 26.0 or Xcode 26.1. Update ViewController.swift with the following code: import UIKit class ViewController: UIViewController { override func viewDidLoad() { super.viewDidLoad() view.backgroundColor = .systemBackground title = Root navigationItem.rightBarButtonItems = [ UIBarButtonItem(title: Full, primaryAction: .init(handler: { _ in self.showModal(with: .fullScreen) })), UIBarButtonItem(title: Page, primaryAction: .init(handler: { _ in self.showModal(with: .pageSheet) })), UIBarButtonItem(title: Form, primaryAction: .init(handler: { _ in self.showModal(with: .formSheet) })), ] } private func showModal(with sty