Search results for

build disappears

49,420 results found

Post

Replies

Boosts

Views

Activity

Error accessing backing data on deleted item in detached task
I have been working on an app for the past few months, and one issue that I have encountered a few times is an error where quick subsequent deletions cause issues with detached tasks that are triggered from some user actions. Inside a Task.detached, I am building an isolated model context, querying for LineItems, then iterating over those items. The crash happens when accessing a Transaction property through a relationship. var byTransactionId: [UUID: [LineItem]] { return Dictionary(grouping: self) { item in item.transaction?.id ?? UUID() } } In this case, the transaction has been deleted, but the relationship existed when the fetch occurred, so the transaction value is non-nil. The crash occurs when accessing the id. This is the error. SwiftData/BackingData.swift:1035: Fatal error: This model instance was invalidated because its backing data could no longer be found the store. PersistentIdentifier(id: SwiftData.PersistentIdentifier.ID(backing: SwiftData.PersistentIdentifier.PersistentIdentifierBacki
1
0
141
4w
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.
4w
xcodebuild -exportLocalizations Fails Due to Cross-Platform Dependencies
I'm working on a large multi-platform iOS project (iOS, iPadOS, watchOS, tvOS, visionOS) and have successfully migrated from legacy .strings files to modern String Catalogs (.xcstrings). However, I'm unable to export localizations using xcodebuild -exportLocalizations due to cross-platform framework dependency issues. (Note: I did have AI help me write this question, so apologies in advance for any errors) Project Structure Main iOS/iPad app with multiple extensions watchOS companion app tvOS app visionOS app 49 .xcstrings files successfully migrated across all targets Uses Swift Package Manager for modularization The Problem When attempting to export localizations using xcodebuild -exportLocalizations, the build fails because it tries to build all targets across all platforms, including watchOS targets that depend on third-party xcframeworks that don't include watchOS slices: xcodebuild -exportLocalizations -project MyProject.xcodeproj -scheme MyApp -localizationPath ./export -configura
5
0
186
4w
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.
4w
Password AutoFill doesn't work - help needed
I have a project with a single app target that serves two environments, and two schemes, one for each env, using xcconfig files for defining environment-specific stuff. I'm trying to figure this out for months, so I've tried multiple approaches throughout this period: Have a single domain in Associated domains in Xcode, defined as webcredentials:X where X gets replaced using a value from xcconfig. Have two domain entries in Associated domains webcredentials:PROD_DOMAIN and webcredentials:STAGING_DOMAIN. Have a different order of domains Results are very interesting: whatever I do, whatever approach I take, password autofill works on staging, but doesn't work on production. I'm aware that we need to test production on Test Flight and AppStore builds. That's how we're testing it, and it's not working. Tested on multiple devices, on multiple networks (wifi + mobile data), in multiple countries.. you name it. The server side team has checked their implementation a dozen times; it's all configured properl
1
0
498
4w
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)
4w
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
4w
Build upload API not yet available?
Dear community, in order to modernize our build pipelines, I wanted to try out the new App Store Connect build upload API that was introduced in the WWDC video Automate your development process with the App Store Connect API. However, when POSTing to https://api.appstoreconnect.apple.com/v1/buildUploads, I receive the following error message: { errors: [ { id: 9fb916ea-4d26-4712-8c55-d1d4b5320bf2, status: 404, code: PATH_ERROR, title: The URL path is not valid, detail: The resource 'v1/buildUploads' does not exist } ] } Is this API not yet available or am I doing something wrong? If it is not yet available, is there an ETA? Thanks in advance & best regards, Yannik
2
0
421
4w
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
4w
XCode 26: is it possible to remove the preinstalled iOS Platform via xcodebuild?
Hi, as described by the subject, I'm trying to find a way to remove the preinstalled iOS support via command line tool. I need to do that because I need to use the universal architectureVariant in order to build on old Intel-based iOS Simulators, but on iOS 26. As described in this page, I can use this command to download the architecture I need xcodebuild -downloadPlatform iOS -architectureVariant universal however, launching this command I receive this error iOS is already downloaded as arm64Only. To replace with universal, first delete the existing one. Is there any way to remove the current installed iOS platform via command line? In particular I'm serching for a way to do what the button Delete in the attached screen does. Thank you
1
0
125
4w
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.
4w
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
4w