I have an iOS app that also has a Mac Catalyst version that I distribute on the Mac App Store. I upload builds to App Store Connect and use the "Manage version and build number" setting introduced in the past couple of years. This always works without a problem for the iOS version of the app. However, on the Mac, I often get a validation error like this: This bundle is invalid. The value for key CBundleVersion [2958] in the Info.plist file must contain a higher version than that of the previously uploaded version [2959]. Please find more information about CFBundleVersion at https://developer.apple.com/documentation/bundleresources/information_property_list/cfbundleversion (ID: 44cc3c93-a563-45bd-8e10-884444207eae) This is all without making any changes to the code or info plist. The exact same code will build, archive, and upload with no problems whatsoever. I often end up having to manually update the bundle version in order to get an upload to succeed. Once I do, both the iOS and Mac versions will upload and validate successfully, but the problem inevitably returns in future releases. All in all, it seems to defeat the purpose of the Xcode automatic build management feature. Am I missing a step somewhere? Why would this happen with the Mac build but not iOS?

I'm trying to add a swift package using Xcode 26 Beta but I keep getting the spinning loader. I tried to remove and re-add my github account, clear history and running plutil -remove IDESwiftPackageAdditionAssistantRecentlyUsedPackages ~/Library/Preferences/com.apple.dt.Xcode.plist in the terminal.

When upgrading to a new version of Xcode, normally we look in the "Toolchain version history" table of the Xcode wikipedia page. But for Xcode 16.2, it lists git tag swift-6.0.3-RELEASE, which fails to compile with a known error. There was a fix for this error way back on July 4, 2024, but for some reason this fix does not appear in swift-6.0.3-RELEASE (as confirmed with git log, even though the tag occurred on December 2, 2024). So it turns out the minimum tag is swift-6.1-RELEASE for building LLVM with Xcode 16.2 (there are no other release tags between these two). Is it possible that the wikipedia table is simply incorrect in this case? If not, is there a workaround to build swift-6.0.3-RELEASE using Xcode 16.2, as published by Apple?

When I build the app, a block symbol appears on the app icon in the Debug Area at the bottom. What is the reason for this?

We have started facing an issue after updating Xcode from version 15.2 to 16, we have a voip application with webview and call kit, and we have the Background Modes capabilities: Voip, Audio, Background fetch, and Background processing. We had no problem on Xcode 15, but ever since updating Xcode 16 and sdk 18, when app goes into the background during an active call, the app is suspended and no events are triggered UNTIL the app is resumed to the foreground.

Dear Apple Developer Support, We are experiencing a critical issue after upgrading our development environment from Xcode 15 to Xcode 16 (beta). Our iOS application integrates Flutter via CocoaPods (install_all_flutter_pods and flutter_post_install) and uses plugins like webview_flutter. After the upgrade, our project started failing at the linking stage with the following errors: Undefined symbol: _XPluginsGetDataFuncOrAbort Undefined symbol: _XPluginsGetFunctionPtrFromID Undefined symbol: Plugins::SocketThreadLocalScope::SocketThreadLocalScope(int) Undefined symbol: Plugins::SocketThreadLocalScope::~SocketThreadLocalScope() Linker command failed with exit code 1 These symbols seem to originate from Flutter’s new native C++ plugin architecture (possibly via webview_flutter_wkwebview), and were previously resolving fine with Xcode 15. We have ensured the following: Added -lc++ and -ObjC to OTHER_LDFLAGS Cleaned and rebuilt Flutter module via flutter build ios --release Re-installed CocoaPods with pod install Verified Flutter.xcframework and plugin xcframeworks are present Despite this, the linker fails to resolve the mentioned symbols under Xcode 16. This suggests a stricter linker behavior or a compatibility issue with the new C++ plugin system Flutter uses. Can you confirm: If Xcode 16 introduces stricter C++/Objective-C++ linker constraints? Is there an official workaround or updated documentation for dealing with Plugins::SocketThreadLocalScope and related symbol resolution? Should these symbols be declared explicitly or provided in .xcframework format from plugin developers? We would appreciate guidance or clarification on how to proceed with Flutter plugin compatibility under Xcode 16. Thank you.

Xcode is stuck on sign-in window of adding a new Apple Account. Returns "unknown error occurred" after couple of hours

Hello, I am getting crash with following details. Crash occurs on only iOS 18.5. Many times the crash occurs in same library i.e. libsystem_malloc.dylib. Can someone guide me to debug this crash and resolve the issue? ————————————————————————————————— Crash sample got by a thirdparty framework: 0x00000001048cc000 Caused by:Applicationreceived signal 5 0 libsystem_malloc.dylib 0x000000019771a020 0x0000000197718000 + 8224 1 libdispatch.dylib 0x000000018ee88a1c 0x000000018ee87000 + 6684 2 libdispatch.dylib 0x000000018ee88a1c 0x000000018ee87000 + 6684 3 libdispatch.dylib 0x000000018ee90258 0x000000018ee87000 + 37464 4 CoreMedia 0x000000019439d704 0x00000001942cc000 + 857860 5 CoreMedia 0x00000001943a3bb4 0x00000001942cc000 + 883636 6 CoreMedia 0x00000001943a3688 0x00000001942cc000 + 882312 7 CoreMedia 0x00000001943a32f8 0x00000001942cc000 + 881400 8 MediaToolbox 0x0000000198736d0c 0x0000000198469000 + 2940172 9 libsystem_pthread.dylib 0x0000000211624d98 0x0000000211624000 + 3480 10 libsystem_platform.dylib 0x0000000211579d98 0x0000000211579000 + 3480 11 libsystem_platform.dylib 0x00000002115798d0 0x0000000211579000 + 2256 12 libsystem_pthread.dylib 0x0000000211628bfc 0x0000000211624000 + 19452 13 MediaToolbox 0x00000001987366dc 0x0000000198469000 + 2938588 14 AVFCore 0x0000000199078f98 0x0000000198fc1000 + 753560 15 AVFCore 0x000000019907825c 0x0000000198fc1000 + 750172 16 AVFCore 0x0000000199076de0 0x0000000198fc1000 + 744928 17 ICBCBankTest 0x0000000108ca5fc4 -[YTVideoRecorder startWith:withWidth:withHeight:withCodecSetting:withAudioSetting:] (in XXXApp) (YTVideoRecorder.mm:114) YTVideoRecorder.mm:114 should be the following code: [videoWriter startWriting]; [videoWriter startSessionAtSourceTime:kCMTimeZero]; And videoWriter is an instance of AVAssetWriter. Currently, memory exhaustion and storage space exhaustion can be ruled out. And AVAssetWriter is used in a single thread. Thanks!

Neither a google search, nor a search of the Apple forums give me a clue as to how to locate or fix the following message I get from Xcode. CLIENT: Failure to determine if this machine is in the process of shutting down, err=1/Operation not permitted This error message came from attempting to build and execute an iOS App which ran just fine the last time I built it. Now, that was actually a little over two years ago. This is an iOS app, which I've run successfully for more than a year on macOS, and that, "My Mac (Designed for iPad)", is what my build target for this run was. Any ideas? Anyone? If this is a "known condition", just why doesn't a friendly internet search or a search of the Apple forums NOT tell me what it means, or what causes the message. Of course, I've upgraded the OS a few times, and updated Xcode as well, but have just not had any time to monkey around with my pet code project. Now that I've gotten some time, and I want to see what's new since March of '23, I finally remember where I stashed my code repository and decided to take it for a spin. Sure, I expect(ed) to see Xcode tell me that the version of Swift has been updated, and maybe some code constructs need to be fixed. But, NO, the code compiles fine. The first build attempt told me that I needed to update my provisioning profiles, and sign-in and agree to the updated developer agreements, which I did. Not so unhelpful was the code window in the debugger: libswiftCore.dylib`swift_willThrow: -> 0x1aeb7b2a0 <+0>: pacibsp 0x1aeb7b2a4 <+4>: str x19, [sp, #-0x20]! 0x1aeb7b2a8 <+8>: stp x29, x30, [sp, #0x10] 0x1aeb7b2ac <+12>: add x29, sp, #0x10 0x1aeb7b2b0 <+16>: adrp x8, 365651 0x1aeb7b2b4 <+20>: add x8, x8, #0x88 ; _swift_willThrow 0x1aeb7b2b8 <+24>: ldapr x8, [x8] 0x1aeb7b2bc <+28>: cbnz x8, 0x1aeb7b2cc ; <+44> 0x1aeb7b2c0 <+32>: ldp x29, x30, [sp, #0x10] 0x1aeb7b2c4 <+36>: ldr x19, [sp], #0x20 0x1aeb7b2c8 <+40>: retab 0x1aeb7b2cc <+44>: mov x0, x21 0x1aeb7b2d0 <+48>: mov x19, x21 0x1aeb7b2d4 <+52>: blraaz x8 0x1aeb7b2d8 <+56>: mov x21, x19 0x1aeb7b2dc <+60>: b 0x1aeb7b2c0 ; <+32> Still not much to go on. I decide to see if it was a macOS vs. iOS issue, so did a clean build folder and tried running on an iPad simulator, "iPad (10th generation)". Now, I have a blank white screen on my simulator and not much to go on in the code window. import SwiftUI @main struct JottoApp: App { Thread1: Breakpoint 1.1 var body: some Scene { WindowGroup { ContentView() } } init() { UITableView.appearance().backgroundColor = UIColor.clear } } Any and all help with this error message will be appreciated.

Hello. Experimenting with xcode programming at the siging and Capabilities i see Team - Personal Team Provisioning profile - Xcode MAnaged Profile Siging sertificate - Apple Development and two errors Communication with Apple failed. Your maximum App ID limit has been reached. You may create up to 10 App IDs every 7 days. No profiles for 'ssd3' were found: Xcode couldn't find any Mac App Development provisioning profiles matching 'ssd3'. what is happaned? I do not Apple Dev ID But i think i have posibillyty to programming and build on my own Mac Anybody can help? Thanks

I am encountering an issue while running my CarPlay app in the simulator using CPListTemplate. On app launch, when I tap on the first item in the list and then tap on the second item, both items remain selected instead of only the latest tapped item. This behavior does not align with the expected single-item selection functionality. Has anyone else faced this issue? Is there a workaround or a known resolution for this behavior?

This question is a component of this question and an extension to this question which has been solved. This situation might feel a pinch constructed but it is a simplified version of one step of the original question. Basically in my app I have a script that outputs a folder with a few files inside of it. This folder is output to $(BUILT_PRODUCTS_DIR)/build/ and is referenced via a PBXBuildFile. Because I put a wait in the script (to simulate a long build I have in my real project) it is very obvious when the script is or isn't run. The goal would be for it to run only when its dependencies have changed. The trick is if I put this script as a "run script" phase within my final target dependency analysis works great. The script only runs when the dependencies are updated. However if I put the "run script" phase into an aggregate target then add it as a Target Dependency in the main target Xcode wants to run the script every time. Regardless of if the dependencies have changed. However if you build just the aggregate target alone everything goes just fine. It only builds when it has to. To me this does not quite make sense. I thought that dependency analysis of the script within my aggregate target would be the same regardless of whether that script was within the aggregate target or the main target. In my app I ideally need the aggregate target to be shared by multiple other targets. While I could put the script in each it would be more foolproof to have them share an aggregate target. Why would dependency analysis come to a different conclusion when the script is within an aggregate target that is a target dependency of the main target? If it helps here is the script and the entire project can be found here on GitHub if you would like to play with it. mkdir -p "${SCRIPT_OUTPUT_FILE_0}/build/" echo "Pausing for 10 seconds before creating files..." sleep 10 cat "${SCRIPT_INPUT_FILE_0}" cat > "${SCRIPT_OUTPUT_FILE_0}/build/index.html" << EOF <!DOCTYPE html> <html> <head> <title>Simple Page</title> </head> <body> <h1>Welcome to Simple Page</h1> <p>Generated at: $(date)</p> </body> </html> EOF cat > "${SCRIPT_OUTPUT_FILE_0}/build/page.html" << 'EOF' <!DOCTYPE html> <html> <head> <title>Simple Page</title> </head> <body> </body> </html> EOF

I have an App that has working audio for most devices except for iOS18 + Air pods pro connected. Eventually I realized that this is due to the Audio Spatialization which is enabled by default. I found a information property list key called AVGameBypassSystemSpatialAudio which can be enabled to true AVGameBypassSystemSpatialAudio and now the audio works for 90% of the game. However my game has a .MP4 which when it is played will be paused when the air pods are connected and after force skipping the video the Spatialization is now enabled and the app no longer has audio. I checked through the logs and found this part mediaplaybackd <<<< FigFilePlayer >>>> itemfig_establishedStereoAudioSpatializationPreferenceForAsset: <0x53451c000|I/OWH.01>: Stereo Spatialization allowed by default due to asset containing video After this line I can see the Spatialization being enabled. Does anyone know how to disable this auto setting of stereo Spatialization by default?

Trying to test applications on AVP as opposed to simulator. AVP can connect to MacBook via Mac virtual display so connection exists, but in X code under Windows devices the AVP does not show up same holds true on the AVP itself under remote devices. The MacBook Pro does not appear. I am signed in under the same account on the same Wi-Fi network. I have tried all basic troubleshooting. It is not clear to me that I am logged in as a developer, which could be the issue, but I am using OS 26, which does not appear to have the developer option under privacy and security where it used to reside in previous versions of the OS.

I've got a 2019 Intel iMac running Sequoia 15.4.1 and Xcode 16.3. Every time I try to view a storyboard Xcode locks up and beachballs on me. It takes minutes to load the file. When I force-quit Xcode, the report that shows up has this as the reason: Processes reached dispatch thread soft limit (64): launchd_sim [96305] [unique pid 194673], launchd_sim [96260] [unique pid 194628] Deadlock: AppleSpell [1494] thread 0x1df0c4 DispatchQueue 313 -> AppleSpell [1494] thread 0x1df0c4 DispatchQueue 313 Deadlock: AppleSpell [1494] thread 0x1df114 DispatchQueue 86 -> AppleSpell [1494] thread 0x1df114 DispatchQueue 86 Blocked by Deadlock: 1 task - AppleSpell [1494] I'm wondering, why is AppleSpell trying to spell-check a plist file? Is there any way to tell AppleSpell to ignore a file?

hi , There is a crash when we run on an **iOS 16 real device ** if we set a .toggleButton trait for accessibilty . it has version check as apple doc refers (IOS 17 +) but it crashes so there is someinconsistency between availbility in ios 18 + , somehow other xcodes made it available from 17 for now we commented our code , but would like dto report this to be fixed cheers

for instance: po [NSBundle mainBundle] 0x0000600002130000 p [NSBundle mainBundle] (NSBundle *) 0x0000600002130000 p [[NSBundle mainBundle] bundlePath] error: Execution was interrupted, reason: EXC_BAD_ACCESS (code=1, address=0x0). The process has been returned to the state before expression evaluation. I am in debug mode

Hey everyone, I'm encountering an issue when trying to run my iOS application, which integrates a Unity project, on the iOS Simulator. I'm consistently getting a dlopen error 232 related to UnityFramework.framework. The full error message is: Error loading ...UnityFramework.framework/UnityFramework (232): dlopen(...UnityFramework.framework/UnityFramework, 0x0109): tried: '...UnityFramework.framework/UnityFramework' (mach-o file (...UnityFramework.framework/UnityFramework), but incompatible platform (have 'iOS', need 'iOS-sim')) It seems like the UnityFramework.framework is built for a physical iOS device (ARM architecture), but the simulator requires a different architecture (x86_64 for Intel Macs or arm64 for Apple Silicon Macs). I've already tried: Cleaning the build folder in Xcode. Checking the "Frameworks, Libraries, and Embedded Content" settings in my target's General tab. Could anyone provide guidance on how to properly configure my Unity build or Xcode project to ensure UnityFramework.framework includes the necessary simulator architectures? Any specific build settings in Unity or Xcode, or steps to re-export/re-integrate the framework, would be greatly appreciated! Thanks in advance for your help!

Start from clean iOS 18.4 simulator. Application tried to request authorisation from user for microphone access. Clicking allow caused the application crashed. Used Swift 6. Report Identifier FB17686864.

Hi all, I'm encountering a strange crash issue during local iOS debugging on a real device, and I'm hoping someone can help explain it. The crash log contains unusually high offsets that are completely outside of any module address ranges listed in Binary Images. For example: 6 ??? 0x129ac0ee8 -[...:] + 1052 But the Binary Images section shows: 0x102358000 - 0x102363fff ChinaMobile arm64 ... 0x11bb2c000 - 0x11bdeffff ChinaMobile.debug.dylib arm64 ... ... There are two binaries for my app listed here, but neither matches that high crash address (0x129ac0ee8). Additionally, sometimes the Binary Images section doesn't even include my app's binary at all, which makes the crash logs even harder to analyze. This crash definitely happens inside my main app’s business code, yet the crash offset doesn’t match any listed binary range. Also, the crash logs contain many ??? module names and missing symbols, even though I'm running a Debug build locally, and I know how to symbolize logs manually. My Questions: Why does the crash log show such high offsets, far beyond any Binary Images' range? Why does it have so many ??? entries and missing symbols, even in a local debug build? Could this be related to Xcode version, build settings, or some project misconfiguration? Any suggestions or insights would be greatly appreciated!