build disappears

As ray_cai outlined the issue was related to the LaunchImage. @howard_kang this fixed the issue for me. Remove LaunchImage from the Asset catalog. Remove references to LaunchImage from your build settings. Add Launch Screen storyboard to the project. Add parameter Launch screen interface file base name with the name of your storyboard Launch Screen.storyboard to your Info.plist file.

@DTS Engineer I utilized iOS 26.1, the issue @ray_cai outlined above was related to the LaunchImage. The fix is: Remove LaunchImage from the Asset catalog. Remove references to LaunchImage from your build settings. Add Launch Screen storyboard to the project. Add Launch screen interface file base name with the name of your storyboard Launch Screen.storyboard to your Info.plist file. I am not sure why this was causing a hang with the tab bar, maybe the Launch Image is not compatible with iOS 26.1 & iPhone Air, this issue was not occurring on other versions of iPhones.

Uploads to App Store from Xcode 26.2 build 17C52 are working now! I was also seeing the same error 2 hours ago.

The crash issue that @edorphy reported in FB21121092 is resolved when you build the app with the released Xcode 26.2 version that came out today, build number 17C52. This version is not the same build as the Xcode 16.2 Release Candidate, so make sure to update to the final release version. @edorphy, had a follow-up statement to me for a different but related issue: you or others may have already seen this one but just in case you haven't: FB21240249 - DeclaredAgeRange: DeclaredAgeRangeAction symbol unavailable on macOS catalyst apps causing crash - documentation says otherwise I appreciate that! I personally had not seen this report, though others within Apple have. We're looking in to it. — Ed Ford,  DTS Engineer

Even with the new Xcode (not release candidate), I get error when uploading from Xcode: Validation Failed: This bundle is invalid. Apple is not currently accepting applications built with this version of Xcode. This is with Xcode 26.2 which has Released December 12, 2025 and Build 17C52. Also, the file name is Xcode_26.2_Apple_silicon.xip.

I built Dext with a development ID and successfully re-signed and notarized it. This time, I only notarized the Driverkit, and plan to do the installer app later. The flow you've described below won't give you a working build. The build will have the development provisioning profile and entitlement configuration in a Developer ID signed build, which means one of two things will happen: (more likely, best case) The DEXT will not load on any device, since the provisioning profile configuration (development) doesn't match the apps signing configuration. (less likely, worst case) The system will allow the DEXT to load, relying on the development provisioning configuration. That means it will work... but ONLY on the limited set of machines that were embedded in the provisioning profile (this is how development signing works). Note that #2 is particularly dangerous, since you can end up shipping a DEXT that works on your machines but none of your customers. I just put up a How to sign a D

This screenshot is with the Xcode 26.2 (175C2), which supersedes the RC version and was downloaded from the Apple Developer website directly. Not showing at the time of writing on the App Store and seemingly its builds are not accepted (yet).

Is there a guide for macOS on the steps you describe at the end, that is on how to allocate a swapfile, Just to be clear, you're not actually creating a swapfile as such. Your mapping a file into memory which means, assuming the mapping MAP_SHARED, the VM system will then use that file as the backing store for that memory range. That gives you basically the same behavior as swap backed system memory, but it isn't ACTUALLY the same as using true swap (for example, you'll be writing the data directly back to file, so there won't be any compression or VM level encryption). mmap that swapfile into memory, mmap is a standard Unix API, which means we don't really provide specific documentation for it, however, there is an old code snippet here showing how it works. One note I will note is that some of the recommendations there aren't really relevant anymore, particularly any recommendation about limiting mapping size. Those concerns where driven by the limited 32-bit address space, but that's not an issue with 64-b

I also have the same problem on a MacStudio M1Max (and not on a MBP M1Max) after upgrading to Xcode 26.1.1: no MetalToolchain accessible from this application. Running on Tahoe 26.1 Running today xcodebuild -downloadComponent metalToolchain gives: `Beginning asset download... Downloaded asset to: /System/Library/AssetsV2/com_apple_MobileAsset_MetalToolchain/68d8db6212b48d387d071ff7b905df796658e713.asset/AssetData/Restore/022-20369-066.dmg Done downloading: Metal Toolchain 17B54.` Then when I run xcrun metal --version, I got an error message: error: error: cannot execute tool 'metal' due to missing Metal Toolchain; use: xcodebuild -downloadComponent MetalToolchain Last when I run: xcodebuild -showComponent metalToolchain, I got: 2025-12-12 18:34:14.045 xcodebuild[27394:1591467] IDEDownloadableMetalToolchainCoordinator: Failed to remount the Metal Toolchain: The file “com.apple.MobileAsset.MetalToolchain-v17.2.54.0.BttmuJ” couldn’t be opened because you don’t have permission to view it. 2025-12-12 18:34:14.339

No, I am not using Playgrounds. My app was developed with Xojo. I have 2 other apps on the Mac App Store already. This is my first iOS iPad App. Xojo has the ability to build and deploy directly to Apple Connect. I have also tried using Transporter to upload my iOS app (also Mac apps). I am attaching my latests error messages from Xojo and Transporter. Thanks for you help. Frederick Harrison

Do I really need to compile a new build with new version number? Is it possible to create a new build and using just the old build that was uploaded before?