When you try to reset settings through the Apple Vision Pro simulator (VisionOS 2.4) you get an error "Preferences quit unexpectedly". Bug report: FB17666053

Setting breakpoints in Xcode and debugging the program will output the following information in the console. The first breakpoint debugging is triggered every time you compile and run the program. Furthermore, loading variables during breakpoint debugging takes a very long time. Why is this information outputted? And why does it take so long warning: (arm64) /Users/xxx/Library/Developer/Xcode/DerivedData/MYApp-edwwubwxxruxpddmfzegvkdqhppk/Build/Products/Debug-iphoneos/XCFrameworkIntermediates/FBKVOController/FBKVOController.framework/FBKVOController(FBKVOController.o) '/var/folders/45/h0vrkd951jjbc538flwxctqc0000gn/C/clang/ModuleCache/2OX0YH8X0GZ6V/UIKit-HKJAGZJT5Z2N.pcm' does not existwarning: (arm64) Environment Xcode Version 16.4 (16F6) + any iPhone device

In many cases I’ll be talking to folks with a memory management problem and I’ll say “You should investigate this with the standard memory debugging tools.” They then turn around and ask me “What are those tools?” Well, this is what I mean: Zombies — This lets you quickly detect when an object is used after it’s been deallocated. Learn more about it in the Finding zombies section of the Instruments Help and in Investigating crashes for zombie objects. There was also an excellent WWDC video about this, namely, WWDC 2010 Session 311 Advanced Memory Analysis with Instruments. This is no longer available in the video archive but if you can find a copy it’s well worth a watch. Address Sanitizer — This is a lower-level tool that finds a variety of common memory management issues, including use after free and buffer overruns. Learn more about this in Diagnosing memory, thread, and crash issues early and the various articles it links to. There’s also a good discussion of this tool, and other Xcode runtime diagnostic tools, in WWDC 2017 Session 406 Finding Bugs Using Xcode Runtime Tools (also no longer available from Apple). Hardware memory tagging — If you have access to a device with hardware memory tagging — starting with the A19 or M5 processors — consider enabling Memory Integrity Enforcement (MIE). For the details, see Enabling enhanced security for your app or watch Secure your app with Memory Integrity Enforcement. Even if you don’t want to do that for your production app, enable it just for development by checking Hardware Memory Tagging in the Options tab of Xcode’s scheme editor. Older tools — There are a variety of older tools that might be useful in some specific circumstances. See the Enabling the Malloc Debugging Features section of the Memory Usage Performance Guidelines for more information about these. Of specific interest is libgmalloc, which is documented in a UNIX man page. For some practical examples of how to identity a memory management crash report and then investigate that crash with these tools, take a look at WWDC 2018 Session 414 Understanding Crashes and Crash Logs. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = "eskimo" + "1" + "@" + "apple.com" Revision History: 2026-03-02 Added a discussion of hardware memory tagging. 2023-05-09 Added a link to Investigating crashes for zombie objects. 2023-03-22 Removed another WWDC session video link. Made minor editorial changes. 2020-10-23 Fixed some formatting errors. 2019-10-30 Removed the link to WWDC 2010 Session 311 Advanced Memory Analysis with Instruments because it’s not long available in the archive. Refreshed all the other links. 2019-01-22 Fixed the link to libgmalloc. 2018-11-02 Updated to include a reference to WWDC 2018 Session 414 Understanding Crashes and Crash Logs. 2017-11-16 First posted.

The following code results in a blue button with a black checkmark. The checkmark should be white. Image(systemName: "checkmark") .frame(width:34, height: 34, alignment: .center) .background(.blue) .foregroundStyle(.white) .cornerRadius(17) I also tried .foregroundColor(.white). I get the same results.

I am on MacOs 15.4.1 which is being deployed with an old version of Ruby ruby 2.6.10 and bundler version 1.17.2. I ran pod install after generating the pods with these versions and during the application compilation there have been several issues reported against pods code.

Using the #Playground macro in beta 3 worked fine, but the Playgrounds package appears to be missing in beta 4. import Playgrounds #Playground { print("🚀 Playground is active") } Canvas error message: Cannot find playgrounds Check whether the playground is compiled for the current scheme and OS of the selected device. There could be compile time checks filtering playgrounds out. Check for dead code stripping or other settings that could exclude playgrounds from the final binary.

I am here and I AM UNABLE TO PUBLISH AN UPLDATE! On xcode in the "signing" i see ONLY ME AND NOT THE COMPANY, i am added as administrator in the apple console developer BUT NOTHING CHANGE!! i tried to add an account but I STILL NOT SEE THE COMPANY, ONLY ME HOW TO FIX THIS?? THIS IS THE WORSE WAY TO SETUP AN ACCOUNT I EVER SEE

How to add an app icon created in Icon Composer to an App Playground project?

We using below command to run unit test and collect coverage: xcodebuild -workspace Demo.xcworkspace -scheme VideoTests -configuration Debug -derivedDataPath ../build/derivedData -destination 'platform=iOS Simulator,id=E6630007-570B-4DEB-A023-2BCE91116A8D' -resultBundlePath './fastlane/test_output/VideoTests.xcresult' -enableCodeCoverage YES -testPlan 'Video' test-without-building | tee '/Users/rcadmin/Library/Logs/scan/VideoTests.log' | xcbeautify -q --is-ci and using xcrun llvm-cov show command to generate coverage report: xcrun llvm-cov show /build/unit-test/coverage/libraries/merged/video.o -instr-profile=/app/ios/build/derivedData/Build//ProfileData/E6630007-570B-4DEB-A023-2BCE91116A8D/video.profdata -show-branches count -show-expansions -show-line-counts -use-color -format=html -output-dir coverage and the html report does not include branch coverage: how to generate the branch coverage?

Desc: app build by old xcode it can install on iOS 26 Beta 1 (Simulator) it install failed on iOS 26 Beta 2 (23A5276e) (Simulator) My Xcode version is 26.0 beta 2 (17A5241o) MacOS version is 15.5 (24F74) Error message: Failed to find matching arch for input file: /Users/klaus.lai/Library/Developer/CoreSimulator/Devices/B52662D2-89AE-4FD3-91A0-D0A67629015B/data/Library/Caches/com.apple.mobile.installd.staging/temp.c5M63e/extracted/Glip.app/Glip

When watching videos about Xcode, the AI coding feature is demonstrated using Swift. Since our company started development early with an Objective-C codebase, I want to know whether the Intelligence feature mentioned in the new feature video supports Objective-C

在项目中没有发现CoreServices.framework，然后编译运行就出现崩溃

When a new application runs on iOS 18.4 simulator and tries to access the Speech Framework, prompting a request for authorisation to use Speech Recognition, the application will crash if the user clicks allow. Same issue in the visionOS 2.4 simulator. Using Swift 6. Report Identifier: FB17686186 /// Checks speech recognition availability and requests necessary permissions. @MainActor func checkAvailabilityAndPermissions() async { logger.debug("Checking speech recognition availability and permissions...") // 1. Verify that the speechRecognizer instance exists guard let recognizer = speechRecognizer else { logger.error("Speech recognizer is nil - speech recognition won't be available.") reportError(.configurationError(description: "Speech recognizer could not be created."), context: "checkAvailabilityAndPermissions") self.isAvailable = false return } // 2. Check recognizer availability (might change at runtime) if !recognizer.isAvailable { logger.error("Speech recognizer is not available for the current locale.") reportError(.configurationError(description: "Speech recognizer not available."), context: "checkAvailabilityAndPermissions") self.isAvailable = false return } logger.trace("Speech recognizer exists and is available.") // 3. Request Speech Recognition Authorization // IMPORTANT: Add `NSSpeechRecognitionUsageDescription` to Info.plist let speechAuthStatus = SFSpeechRecognizer.authorizationStatus() logger.debug("Current Speech Recognition authorization status: \(speechAuthStatus.rawValue)") if speechAuthStatus == .notDetermined { logger.info("Requesting speech recognition authorization...") // Use structured concurrency to wait for permission result let authStatus = await withCheckedContinuation { continuation in SFSpeechRecognizer.requestAuthorization { status in continuation.resume(returning: status) } } logger.debug("Received authorization status: \(authStatus.rawValue)") // Now handle the authorization result let speechAuthorized = (authStatus == .authorized) handleAuthorizationStatus(status: authStatus, type: "Speech Recognition") // If speech is granted, now check microphone if speechAuthorized { await checkMicrophonePermission() } } else { // Already determined, just handle it let speechAuthorized = (speechAuthStatus == .authorized) handleAuthorizationStatus(status: speechAuthStatus, type: "Speech Recognition") // If speech is already authorized, check microphone if speechAuthorized { await checkMicrophonePermission() } } }

I’ve developed an Apple Watch extension for an existing iOS app. When I run the app on the watch via Xcode using the simulator, everything works fine. However, when I try to install it on my iPhone, the Watch app doesn’t show it in the "Available Apps" list, so I can't install it on the watch. The Apple Watch is connected to my iPhone, and I can see other apps available for installation without any issues. I also created a brand new project with watchOS support to troubleshoot, but the same problem occurred. Any ideas on how to resolve this?

In previous Xcode versions, it was possible to add a folder reference to a project, and in the copy resources build phase it would copy the folder the bundle, rather than the contents (i.e. the folder's contents would be nested inside a directory named after the folder). In Xcode 16.4, when creating a folder reference, the copy resources build phase will copy the contents of the folder to the bundle at the root level (not nested), like the old behavior when creating a group rather than a folder reference. If you look at the raw project.pbxproj file, it shows up as a "File System Synchronized Root Group" rather than a "File Reference". Is there a way to get the old behavior, aside from hand-editing the project.pbxproj file?

How can I add more architectures to my app using Xcode? I made it using beeware and it is made for iOS.

My app works fine when I load it directly from Xcode to my phone via USB but once I load it to TestFlight the sounds no longer play when the app is not in focus or the phone is locked. I've tried every combination of tools available from the support group and from AI! And I'm out of ideas.

Hi everyone, I’m running into an issue trying to use the new SpeechAnalyzer framework announced at WWDC 2025. ❯ My Setup: • macOS: Sequoia 15.5 (Build 26.0 / macOS Tahoe Beta 26.0) • Xcode: 26.0 beta 2 (17A5241o) • Deployment Target: macOS 26.0 • Toolchain: Clang 17.0.0 (Apple) ❯ Problem: Despite following all setup requirements: • Setting macOS 26 as the deployment target • Using the latest Xcode 26 beta 2 • Running the correct developer toolchain (xcode-select is pointing to Xcode-beta) I still get the error: No such module 'SpeechAnalyzer' Additionally: • The SpeechAnalyzer.framework does not appear under /Applications/Xcode-beta.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/ • It is also not listed in the Link Binary with Libraries pane. ❯ What I’ve Tried: • Clean builds • Deleted DerivedData • Verified SDK installation paths • Reinstalled Xcode 26 beta 2 • find search for SpeechAnalyzer.framework returned nothing ❯ Request: Has anyone successfully used SpeechAnalyzer in Xcode 26 beta 2 on macOS Sequoia/Tahoe? Is there a separate SDK or seed profile required to access this framework? Would appreciate any guidance from Apple engineers or other beta testers. Thanks! — Lalit Lakhara

HI, I upgraded to macos 15.5 and xcode 16.3. Last year I was able to update one of my apps on the App Store without issues. Today, after a successful Testflight test, I now need to submit a new version of my app to the App Store for Distribution as the next version/build. However, when I configure a manual setting for the signing, I can select the correct choices. But when I click automatically manage signing, and choose the correct team, xcode put in the wrong signing certificate. It is choose a development one, and not the distribution one. I am concerned about this since I have read that when using the Archive tool, it choses the automatically manage signing by default. And that check box is selecting the "default" settings. I do not know where these default settings are being set, or how to fix this issue. I do not see any info in my searching up to this point. I hope someone can help. thank you, cc

We are experiencing a significant issue with the SKStoreReviewController.requestReview(in: scene) API that may be affecting our app's rating collection on the App Store. Issue Details: Development Environment Behavior: The rating popup displays consistently in development builds (as expected per documentation) API calls are functioning correctly in our test environment Production Environment Issue: We have observed a major drop in App Store ratings received between January and July 2025 The same codebase that works in development is deployed to production Analytics Confirmation: Before calling SKStoreReviewController.requestReview() in production, we fire analytics tags to track API invocations Our analytics show no drop in the number of times this API is being called This confirms the API is being invoked correctly in production Discrepancy: Despite consistent API calls (confirmed by analytics), we see a major drop in actual ratings received on the App Store This suggests the rating popup may not be displaying to users in production, even though the API call is successful Questions: Are there any known issues with SKStoreReviewController.requestReview() API between January-July 2025? Are there any iOS version-specific issues that might prevent the popup from appearing in live app? What debugging steps do you recommend to identify why the API calls aren't resulting in visible rating prompts?