It's maddening. I just opened a file and now it's gone because I had the audacity to open another file. I've learned that I can double click the tab of the first file to make it a permanent tab... but, of course, I'll need to do that every time I ever open any file ever, and if I close that file and come back to it later I'm going to be constantly having to double click tabs just to make Xcode stop replacing my tabs for me. It's nuts. It's driving me insane. Please. Is there any way to just DISABLE the temporary tabs behavior? I don't find it helpful in any way and I find it to be destructive to my development workflows.

Hi! When building my app using Xcode 16, fast scrolling (using scrollViewProxy.scrollTo) a list would result in items not appearing even when scrolling stopped. This does not happen when the app is built with Xcode 15, even on iOS 18. I'm also getting this error in the logs: List failed to visit cell content, returning an empty cell. - SwiftUICore/Logging.swift:84 - please file a bug report.

We are experiencing networking issues in our iOS application when it is built with Xcode 16 or later. Our app includes a video conferencing feature that works reliably when built with Xcode 15 or earlier — we can sustain hour-long video sessions without interruption. However, when the app is built using Xcode 16 or higher, network connections drop after 2–3 minutes during a session. This triggers an auto-reconnect, which succeeds, but the connection drops again after another 2–3 minutes. This loop continues indefinitely. Key Details: The issue only occurs in TestFlight builds. When running the app via Xcode debugger, the issue does not occur. The issue is consistently reproducible in TestFlight builds created with Xcode 16 or later. TestFlight builds created with Xcode 15 do not exhibit this issue. All the videoconferencing runs on C and C++ code What We’ve Tried: Reviewed Xcode 16+ release notes but found no relevant changes or deprecations. Verified app configuration and entitlements. Confirmed that no app-side changes occurred between the working and broken builds. Request: We’re seeking guidance on what changes in Xcode 16+ could be affecting networking behavior in release/TestFlight builds. Any insight into relevant build settings, compiler changes, or runtime behavior differences would be greatly appreciated. Thank you in advance for your assistance.

All the threads only contain system calls. The crashed thread only contains a single call to my app's code which is main.swift:13. What could cause such a crash? crash.crash

I've got several Xcode iOS projects and in the Editor menu section there are dozen's of options, as in the diagram. However if I create a new iOX Project (with Xcode 16.2) look at how sparse the Editor menu is. Why is that, why do they appear for other projects but not for a new one and why are the contents different?

Hi everyone, I'm experiencing an issue with my app, which is currently live on the App Store. I attempted to upload a new version, but the App Review team informed me that the app crashes on launch. Sure enough, when I download the app via TestFlight, it crashes immediately on startup — I see a grey screen, and then the app closes after about a second. The strange part is that no crash reports are generated. However, when I build the app in Xcode and install it directly onto my device via USB-C, it runs perfectly fine. I've tried updating to the latest version of Xcode and followed the suggestions in this Reddit thread: https://www.reddit.com/r/iOSProgramming/comments/re2n65/app_crashes_after_testflight_download_but_no/ My app is a Unity game that had been working fine until now. There haven’t been any major changes in the latest update. Could this be an Apple-side issue? And how is it possible that no crash reports are generated? Since the app crashes before it even fully starts, I don’t think it's a memory leak. Any help would be greatly appreciated, I can give more info if needed — I’m completely stuck here. :/

After I uploaded my app to testflight, the MinimumOSVersion was set to 14.0, and TestFlight showed MinimumOSVersion=14.0. However, after I distributed it, if the user's device is iOS 14, then the MinimumOSVersion in Info.plist=14.0, and if it is an iOS 15 or higher device, the MinimumOSVersion in Info.plist=15.0 will be changed. Because my app will detect this value, I had to change my code, but this is too strange, at least there will be no problem before April 27, 2025, because I checked my distribution records.

I am trying to notarize a simple app I made, but keep getting stuck on "In Progress". The app is a MacOS app, and I'm using XCode. I've tried all the steps listed in the links below: https://developer.apple.com/documentation/security/notarizing-macos-software-before-distribution https://developer.apple.com/documentation/security/resolving-common-notarization-issues I've had the same issue with another app, which got rejected after multiple hours. Never got to resolve this.

Device: iPhone 16 Pro Max System Version: 18.3.1 Screen width and height obtained using [UIScreen mainScreen].bounds.size are as follows Why are the two results different?

As of Xcode 16.3 it seems Copy Symbol Name and Copy Qualified Symbol Name have been removed from the context menu. I see they're still under Edit > Copy in the Menu Bar, but this location seems far less accessible. Is there a setting to return them to the context menu? I use these on a daily basis, and I find this change to be frustrating.

I have my main app that connect to multiple internal modules. These modules are built with Xcode 15.4 on Jenkins. If I use these modules as xcframework in main app and try to build main app with Xcode 16.2 it will give error. Framework built with older version of Swift. I thought we have ABI stability with new Xcode versions. Any idea what can be issue?

They said something like hold option or whatever but It didn't seems to work with me...

C++ code that compiled fine on Xcode 16.2 when targeting macOS 13.3 after upgrading to Xcode 16.3 gives an error that the minimum required target is macOS 13.4 with an error like: `/Applications/Xcode-16.3.0.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX15.4.sdk/usr/include/c++/v1/__format/formatter_floating_point.h:74:30: error: 'to_chars' is unavailable: introduced in macOS 13.4 unknown 74 | to_chars_result __r = std::to_chars(__first, __last, __value, __fmt, __precision); Here’s example taken directly from (https://en.cppreference.com/w/cpp/utility/format/format): #include <format> #include <iostream> #include <string> #include <string_view> template<typename... Args> std::string dyna_print(std::string_view rt_fmt_str, Args&&... args) { return std::vformat(rt_fmt_str, std::make_format_args(args...)); } int main() { std::cout << std::format("Hello {}!\n", "world"); std::string fmt; for (int i{}; i != 3; ++i) { fmt += "{} "; // constructs the formatting string std::cout << fmt << " : "; std::cout << dyna_print(fmt, "alpha", 'Z', 3.14, "unused"); std::cout << '\n'; } } It doesn’t make any sense to suddenly require targeting 13.4 for features that worked fine on 13.3. The Apple documentation for C++ feature support explicitly discusses 13.3. https://developer.apple.com/xcode/cpp/ (search for P0067R5 on the page) I haven't tested it, but based on the standard library headers the minimum required iOS version has also been bumped - from 16.3 to 16.5. Am I doing something wrong? Is there a known work-around? Filed feedback: FB17081499

I recently encountered an issue involving Core Data’s new Composite Attributes feature and thought I would share my experience, as well as seek clarification. I created a composite type where all attributes were mandatory, except for one. Subsequently, I added an attribute to an entity and set its type to that composite type. Upon running the app, the console output the following error: CoreData: error: CoreData: error: Row (pk = 85) for entity ‘(EntityName)’ is missing mandatory text data for property ‘(propertyName)’ The way I resolved this was by removing the composite type attribute from the entity, after which the error no longer appeared. I also observed that in another entity, where a different composite type is used, all the attributes were optional — and no error occurred. This raises the question: why must all attributes in a composite type be optional? Furthermore, why does Xcode not inform the developer of this requirement? I have reviewed both the documentation and the WWDC23 “What’s New in Core Data” session, but neither mentions that having non-optional attributes within a composite type will cause such errors and lead to unpredictable application behaviour. Additionally, this issue remains unresolved in another area I raised previously in this topic: Composite Attributes feature requires tvOS deployment target 17.0 or later Composite Attributes feature requires watchOS deployment target 10.0 or later However, I do not have a tvOS or watchOS target, nor do I intend to add one. Could someone from Apple, or anyone with more experience, please clarify why all attributes within a composite type must be optional? And could it be possible for Xcode to flag this at compile time, rather than failing at runtime? Thank you in advance.

Unknown error from LeakAgent. errorStatus: 2 Domain: XRMemoryGraphDebuggerErrorDomain Code: 5 User Info: { DVTErrorCreationDateKey = "2025-04-01 02:49:23 +0000"; DVTRadarComponentKey = 637311; } Event Metadata: com.apple.dt.memory_graph_capture : { "debugSession_coalescedState" = 1; "debugSession_currentStackFrame" = "mach_msg2_trap"; "debugSession_currentThread" = "Thread 1"; "debugSession_isSynthetic" = 0; "debugSession_state" = 1; "device_identifier" = "00008110-000154D00EEB801E"; "device_isCoreDevice" = 1; "device_model" = "iPhone14,2"; "device_osBuild" = "18.4 (22E240)"; "device_platform" = "com.apple.platform.iphoneos"; "device_thinningType" = "iPhone14,2"; "dvt_coredevice_version" = "443.19"; "dvt_coresimulator_version" = "1010.10"; "dvt_mobiledevice_version" = "1784.102.1"; "launchSession_schemeCommand" = Run; "launchSession_state" = 2; "launchSession_targetArch" = arm64; "memgraphDebugger_duration_ms" = 0; "memgraphDebugger_precedingCount" = 1; "memgraphDebugger_status" = 5; "param_debugger_attachToExtensions" = 0; "param_debugger_attachToXPC" = 1; "param_debugger_type" = 3; "param_destination_isProxy" = 0; "param_destination_platform" = "com.apple.platform.iphoneos"; "param_diag_113575882_enable" = 0; "param_diag_MainThreadChecker_stopOnIssue" = 0; "param_diag_MallocStackLogging_enableDuringAttach" = 0; "param_diag_MallocStackLogging_enableForXPC" = 1; "param_diag_allowLocationSimulation" = 1; "param_diag_checker_tpc_enable" = 1; "param_diag_gpu_frameCapture_enable" = 0; "param_diag_gpu_shaderValidation_enable" = 0; "param_diag_gpu_validation_enable" = 0; "param_diag_guardMalloc_enable" = 0; "param_diag_memoryGraphOnResourceException" = 0; "param_diag_mtc_enable" = 1; "param_diag_queueDebugging_enable" = 1; "param_diag_runtimeProfile_generate" = 0; "param_diag_sanitizer_asan_enable" = 0; "param_diag_sanitizer_tsan_enable" = 0; "param_diag_sanitizer_tsan_stopOnIssue" = 0; "param_diag_sanitizer_ubsan_enable" = 0; "param_diag_sanitizer_ubsan_stopOnIssue" = 0; "param_diag_showNonLocalizedStrings" = 0; "param_diag_viewDebugging_enabled" = 1; "param_diag_viewDebugging_insertDylibOnLaunch" = 1; "param_install_style" = 2; "param_launcher_UID" = 2; "param_launcher_allowDeviceSensorReplayData" = 0; "param_launcher_kind" = 0; "param_launcher_style" = 99; "param_launcher_substyle" = 0; "param_runnable_appExtensionHostRunMode" = 0; "param_runnable_productType" = "com.apple.product-type.application"; "param_structuredConsoleMode" = 1; "param_testing_launchedForTesting" = 0; "param_testing_suppressSimulatorApp" = 0; "param_testing_usingCLI" = 0; "sdk_canonicalName" = "iphoneos18.4"; "sdk_osVersion" = "18.4"; "sdk_variant" = iphoneos; } System Information macOS Version 15.3.2 (Build 24D81) Xcode 16.3 (23785) (Build 16E140) Timestamp: 2025-04-01T10:49:23+08:00

macOS Version 15.3.2 (Build 24D81) After initiating via Shift/Command/0 the Developer Documentation Window, the indexing of v277 index structure is starting /Users/[name]/Library/Developer/Xcode/DocumentationCache/ ==> but unfortunately not ending! Activity Monitor reports during hours high CPU (~80%) for Xcode process, but the indexing does not stop or end. After hours it is still around 146 MB instead of about 550 MB as in previous releases. Indexing starts with 11 or more threads, but suddenly it drops to 10 threads and seems stopping, still using cpu. Also restarting Xcode does not help. Process restarts but after some minutes seems to hang or stuck around 200MB indexed. Also removing subfolders does not help. (NSOperatingSystemVersion(majorVersion/ 16, minorVersion/ 3, patchVersion/ 0) they are recreated but index still stucks after some time. No clue. will reverting back to 16.3 beta2 Reported via FB16926964

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?

I have a sample SwiftUI iOS app. As shown in the screenshot below, my project has three configurations: Debug, MyDebug, Release. If I select the Debug or MyDebug scheme, I get a preview. But if I select the Release scheme, I get an error that says the following. ”***.app” needs -Onone Swift optimization level to use previews (current setting is -O) , where *** is the app name. It probably has nothing to do with the Preview error, but the Info.plist has a dictionary such that the key name is devMode, and the value is $(DEVMODE). And I have a user-defined setting as shown below. My ContentView has the following. import SwiftUI struct ContentView: View { @State private var state: String = "" var body: some View { VStack { Text("Hello, world!: \(state)") } .onAppear { if let devMode = Bundle.main.object(forInfoDictionaryKey: "devMode") as? String { print("Development mode: \(devMode)") state = devMode } if let path = Bundle.main.path(forResource: "Info", ofType: "plist") { if let dict = NSDictionary(contentsOfFile: path) { print("**** \(dict)") } } #if DEBUG print("Debug") #elseif MYDEBUG print("MyDebug") #else print("Que?") #endif } } } #Preview { ContentView() } So my question is how I get the preview for all three build schemes? Muchos thankos.

Hi everyone, I'm encountering a persistent issue when trying to build my React Native project for iOS. I'm using the react-native-vision-camera library (version 4.6.4) and I've set my iOS deployment target to 16.0 in the app.json file. Despite this, the build process fails with an error related to the react-native-vision-camera pod, which seems to be stuck on an older version (2.15.4) that requires a different C++ version and a lower deployment target. Here's what I've tried so far: Ensured that the C++ version is set to 17 as required. Cleared and reinstalled all pods (rm -rf ios/Pods ios/Podfile.lock followed by pod install). Confirmed that the deploymentTarget in the app.json is set correctly to 16.0. However, the error persists and the build continues to fail, pointing to a compatibility issue with the react-native-vision-camera pod. I'm not sure if there's a cache issue or a configuration step I'm missing. Environment: React Native version: 0.76.7 react-native-vision-camera version: 4.6.4 iOS deployment target: 16.0 Expo SDK version: 52.0.40 Attached: app.json, eas.json, package.json, and the error log screenshot. Error log screnshot: Files: app.json eas.json package.json Any insights or suggestions from the community or Apple engineers would be greatly appreciated. Thank you!

Has Objective-C been deprecated?