Hi,
I am in the last step "preparing for submission" and everything excepts "age rating" is fine. How can I fix this?
I have two apps and on neither i can edit "age rating" :(
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
As subject, after update to Xcode 26.0.1, none of the simulator able to download, tried click the Get button, tried run command in terminal, all failed.
Error from terminal:
xcodebuild -downloadPlatform iOS
Finding content...
Automatically resolved architecture variant for platform iOS as 'universal'.
2025-10-09 06:21:24.423 xcodebuild[1789:30064] DVTDownloadable: Download Failed. Downloadable: {
architectures = (
arm64,
"x86_64"
);
authentication = none;
category = simulator;
contentType = cryptexDiskImage;
dictionaryVersion = 2;
downloadMethod = mobileAsset;
fileSize = 10066611438;
identifier = "com.apple.dmg.iPhoneSimulatorSDK26_0";
isInternalContent = 0;
isUserInitiated = 1;
name = "iOS 26.0 Universal Simulator (23A343)";
patchableFrom = (
);
platform = "com.apple.platform.iphoneos";
simulatorVersion = {
buildUpdate = 23A343;
version = "26.0";
};
version = "26.0.0.0";
}. Download failed.
Any idea how to resolve this?
iMac with Intel processor
I've created a new project in Xcode. I'm running the Xcode 16.4 and MacOS 15.5.
I'm trying to run my barebones project on my iPhone 16 (I'm just getting started). I turned on developer mode on my iPhone and went through the whole process. But in the Signing & Capabilities of my project under status I see two errors...
There is a problem with the request entity
A device with number 'XXXX8801C' already exists on this team.
Provisioning profile "iOS Team Provisioning Profile: [MyBundleID]" doesn't include the currently selected device "My iPhone" (identifier XXXX8801C).
I noticed in the devices on the developer portal that my device is showing as "Processing." I feel ike it's stuck. But I can't figure out how to clear it all out and try again. It's been 24 hours since this error came up.
I've tried to clear trusted computers on the iPhone. I've deleted the "Derived Data" folder. I've removed my developer account from Xcode and added it again. I've restarted both my Mac and my iPhone multiple times.
I've noticed it asked to authorize my computer twice. When I clear the authorized computers and then plug the phone back in it asks twice again. So I'm not sure if this is the issue? No idea why it asks twice but I'm only ever able to respond to the second request as the first request gets blocked in the UI by the second requests if that makes sense?
I'm also not able to turn off developer mode on my iPhone. The switch isn't there as the docs state it should be. So again, I feel like this is the phone and the developer portal stuck causing the problem.
Note: I saw someone else had encountered this problem and I replied to it and boosted it. But it looks like it was posted in 2017? Hence this new post.
Topic:
Developer Tools & Services
SubTopic:
Xcode
Tags:
Developer Tools
Provisioning Profiles
Signing Certificates
Good afternoon,
I have the latest version of Xcode. I am trying to debug why I am not able to Sign in with Apple Sign In on my app. After days of trying everything I just noticed today that the TeamID Xcode is using to automatically sign the app is not my current Team Id. I had a years hiatus and my code login expired. When I recreated my account I got a new Team Id and that is what is on all my certificates, profiles, etc. Old team id: Z82SJZ64R6 Current team id: 22649D52Q5. I take off automatically signing and select my Mac app bistro and iOS app distro and the app fully builds then Xcode crashes with an error that mentions security - Error code 5.
Is there a way for me to change the old team id in Xcode? I've already tried logging out and back in through settings.
I want to use a ci_script to change the CI_BUILD_NUMBER to a new value.
But in XCODE CLOUD there seems to be no programmatic way to change it?
I am having similar problems to this guy on Stack Overflow over a year ago:
https://stackoverflow.com/questions/77627852/functions-of-iouserscsiperipheraldevicetype00-class-in-scsiperipheralsdriverkit
There are also a few questions on this forum about this object, none of which have answers.
I can get my driver to match and instantiate, but
nobody calls my UserDetermineDeviceCharacteristics (which does nothing, just returns kIOReturnSuccess)
I can attempt to call UserSuspendServices(), UserResumeServices() or UserReportMediumBlockSize() and all of them return kIOReturnUnsupported. It doesn't matter if I've unmounted the disk or not.
Is the custom driver supposed to be instantiated beside the kernel's IOSCSIPeripheralDeviceType00, or should it replace it?
What should its IOProviderClass be?
What should its IOClass be - IOUserService, or something else?
see FB19678139 and FB19677920
Beginning April 24 releasing on the App Store requires using Xcode 16, iOS 18 SDK. https://developer.apple.com/news/upcoming-requirements/?id=02212025a
Xcode only offers simulators for iOS 15. I had not been able to install and use previous versions. Does it imply iOS 15 is the minimum target allowed?
Topic:
Developer Tools & Services
SubTopic:
Xcode
Everytime when iOS simulator is launched I het a lot of repeated "*** quit unexpectedly" alerts.
Where "***" is a mix of "managedappdistributiond","healthappd", and "findmylocated"
Even after the simulator is launched I still het random "*** quit unexpectedly" alerts.
Very annoying because the alerts deactivates the active window
This is on an MacBook Pro M3 Max,, Xcode 15.2, Sonoma 14.2.1, it also happens with Xcode 15.1
A co developer (MacBook Pro M1 Max,Xcode 15.2, Sonoma 14.2.1) does not have the issue
Any idea how I can prevent this from happening?
Update
Every mentioned service crash happens in libswiftCore.dylib at
0x1929f3938 assertionFailure(:_:file:line:flags:) + 248
Like so many, i am getting
The operation couldn’t be completed. (ModelCatalog.CatalogErrors.AssetErrors error 1.)
Domain: ModelCatalog.CatalogErrors.AssetErrors
Code: 1
User Info: {
DVTErrorCreationDateKey = "2025-06-25 12:50:18 +0000";
}
Failed to find asset: com.apple.fm.code.generate_small_v1.tokenizer.generic - no asset
Domain: ModelCatalog.CatalogErrors.AssetErrors
Code: 1
System Information
macOS Version 16.0 (Build 25A5295e)
Xcode 16.4 (23792) (Build 16F6)
Timestamp: 2025-06-25T08:50:18-04:00
error when trying to download the AI extension in XCODE
running Tahoe Beta 2; latest Xcode version
Topic:
Developer Tools & Services
SubTopic:
Xcode
With Xcode 14, the device selection on the bottom of the storyboard canvas has changed, and the iPhone 12 and 13 mini screens are no longer there, as well as there only being one model of iPad. Is there a way to add more devices to this section?
I have simulators installed for these devices, and this is the way I've been checking compatibility so far, but this is not sustainable.
I appreciate any help that you can give me.
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 as a supported destination. The error doesn't happen when running on Apple Vision Pro (Designed for iPad) or iPad Pro 13-inch (M4) destinations. What is the problem?
I created FB20448815.
The Files app in the iOS 18 beta simulator appears to be read-only. I am unable to:
create folders
copy files into it by dragging them from macOS
safe files from safari
I have been unsuccessful at finding a way to popular any file or folder in the Files app which is preventing me from testing some scenarios in my app where I import files using the files sheet.
The earliest I tried was beta 3 and it still persists in beta 7. The iOS 17 simulator works fine in comparison.
My mac is a 2019 macbook pro running Sonoma 14.5.
To reproduce:
New folder
Launch Files app in iOS simulator
Tap into "On my phone"
From the top menu tap "New Folder"
(nothing happens)
Download a file
Launch safari
Find a file like a PDF to download
Tap on the down arrow in the toolbar
Files opens up with the filename in the textfield at the bottom
The "Save" button is grayed out.
Copy from macOS
Open the Files app in iOS and browse to a local folder
drag a file from the macbook onto the simulator
the sheet appears with the filename in the text field
The "Save" button is grayed out
Hi everyone,
I’ve run into a strange issue while building my app with Xcode 26 beta 6 (targeting iOS 26). When I include an app icon created using Icon Composer, the build time jumps to over 5 minutes. During this time, I noticed that a utility called AssetCatalogSimulatorAgent is consuming a significant amount of CPU.
If I remove the Icon Composer-generated icon from my target, the build completes in about 40 seconds. This behavior is consistent across multiple builds.
Has anyone else experienced this? Is there a known workaround or optimization for icons created with Icon Composer? I’d love to keep using the new icon format, but the build time is becoming a real bottleneck.
Thanks in advance!
Build succeed,but app startup failed.
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
Is anyone else having trouble with the Documentation in the latest Xcode beta? I can't get any UIKit documentation to appear. UIKit is completely missing from the table of contents too. I've tried deleting the documentation caches but it isn't helping.
Topic:
Developer Tools & Services
SubTopic:
Xcode
After updating to Xcode 16.3, getting the error - Symbol not found: ___cxa_current_primary_exception
It didn't happen with Xcode 16.2 that I used before, but after updating to 16.3, when I build the app, the following error is output to the console and the app doesn't run.
dyld[2150]: Symbol not found: ___cxa_current_primary_exception
Referenced from: <6B00A4F2-B208-3FDB-BA38-B7095AF0034A> /private/var/containers/Bundle/Application/B590DB18-9C66-4C9E-8330-104943419E60/Mubeat DEV.app/Mubeat DEV.debug.dylib
Expected in: <7F51CB08-A0CA-386E-BB62-4B8BFB0CED9F> /usr/lib/libc++.1.dylib
Symbol not found: ___cxa_current_primary_exception
Referenced from: <6B00A4F2-B208-3FDB-BA38-B7095AF0034A> /private/var/containers/Bundle/Application/B590DB18-9C66-4C9E-8330-104943419E60/Mubeat DEV.app/Mubeat DEV.debug.dylib
Expected in: <7F51CB08-A0CA-386E-BB62-4B8BFB0CED9F> /usr/lib/libc++.1.dylib
dyld config: DYLD_LIBRARY_PATH=/usr/lib/system/introspection DYLD_INSERT_LIBRARIES=/usr/lib/libBacktraceRecording.dylib:/usr/lib/libMainThreadChecker.dylib:/usr/lib/libRPAC.dylib:/Developer/Library/PrivateFrameworks/DTDDISupport.framework/libViewDebuggerSupport.dylib
After looking for another solution, I found a way to remove the -Objc option in Other Linker Flags, but this method only works on iOS 18.4 and doesn't work on other versions.
Is there another solution?
Ok, I'm going crazy here. I have a static library for iOS that I want to build for the simulator. I use xcodebuild -destination="iOS Simulator" and then check the library using otool which tells me the platform is 6, which is Mac Catalyst.
When I look at the output of xcodebuild, it says
--- xcodebuild: WARNING: Using the first of multiple matching destinations:
{ platform:macOS, arch:arm64, variant:Mac Catalyst, id:00006041-0008492E3AA1801C, name:My Mac } ...
It has the simulator listed too, way down the list:
{ platform:iOS Simulator, arch:x86_64, id:AB7A99B3-8D24-4F73-A42D-9BB45321928D, OS:18.6, name:iPad (A16) }
When I put all of that into xcodebuild for the platform, it still says there are multiple matching destinations and chooses Mac Catalyst. Why? How? What? Does platform="iOS Simulator" mean nothing? How in the world does "Mac Catalyst" match "iOS Simulator"?????
I don't want Mac Catalyst, I don't need Mac Catalyst, and I can't get rid of Mac Catalyst. Nothing I specify in xcodebuild results in anything I can build that will compile for the simulator.
What the heck am I doing wrong?
Anyone else notice that Xcode 16.1 seems to have stopped building universal binaries for both debug and release builds even though under "Build Settings-Build Active Architecture" both Debug and Release are set to NO. We had been using the universal binary builds out of Debug for preliminary tests on Intel based machines. The Architectures setting is set to: Standard Architectures (Apple Silicon, Intel) - $(ARCHS_STANDARD).
I started a brand new empty app and it does the same thing.
A workaround is to set the Destination in Xcode's menu bar to "Build on Any Mac" and then find the binary and drag it to the Intel computer. You can't run that one though from Xcode. Another workaround is to build an Archive and drag that one.
I am trying to run Xcode 15 on macOS 15.4.
As we need to build framework with older versions of Xcode.
Any work around for it?