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.

I've been aware for some time that Push notifications work on the iOS simulator now -- I see them pop up while I'm working. However, it would seem that SILENT push notifications do not work. I came to this conclusion only after several frustrating hours of debugging my app, thinking either the app was broken or the server wasn't sending the notification. Finally I tested it on a device and found that it actually works fine. Why does such a limitation exist? If I can't depend on the simulator to handle ALL of the notifications, I'd rather it didn't work at all. Having it work part of the time on some notifications is really confusing.

Hi I developed an iPhone app but now I want to release the same app for iPad and Mac (Design for iPad). I made the changes below but I still not been able to install the app on my Mac. It says the app is incompatible but my Mac is MacBook Pro M2 which fills the requirements to install it. Things I did so my iPhone app could have support for iPad and Mac Added iPad and Mac (Designed for iPad) for the supported destinations Change the Status Bar Style to Require full screen Changed iOS minimum Deployments iOS to 17.6 Updated the launch screen logo so stays in the middle Xcode version 16.2 See the sccreenshots of the Xcode configuration and of the TestFlight on my MacBook Pro M2 Is there anything else I need to do? Thanks.

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.

Crash while trashing an opened and pinned file. This crashing can be reproduced. Xcode Version 26.0 beta 2 (17A5241o) Part Of Crash Log

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

Is anybody able to save the autocreated testplan successfully with Xcode 16.3? I get a crash no matter what (different filenames, locations, machines, ...). Now created a template project: same thing. Xcode Version 16.3 (16E140) on macOS 15.5 (24F74) Known issue, or am I holding it wrong?

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?

Hi! A couple of months ago my app was archiving just fine. Since an xcode update the build fails. Here is what shows at the end of the log. Thank you in advance for any help! Run custom shell script 'Run Script' Failed to package [project folder] Command PhaseScriptExecution failed with a nonzero exit code

I have a new build/version of my app that required changes by Apple in order to approve. I created a new build and uploaded via XCode (it shows in TestFlight) but cannot for the life of me figure out how to get the "+" sign next to "IOS App" in App Store Connect.

I am trying to setup a unversal linking for my new developing app. but it look like not function well. did any one have some examples or demo domains suggest to use? In fact finally my app is just internal using, user will not suppose connect to internet , how can I using the universal linking without a website ? Thanks

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 have a ContentView in my app which includes the line of code FileUploadProgressAttributes. this struct is defined in a file included in the target FileUploadProgressExtension. and it is an ActivityAttributes. in ContentView I imported FileUploadProgressExtension, and the xcode is able to find the FileUploadProgressAttributes during prebuild. but during build, it gives me Undefined symbols for architecture arm64: "FileUploadProgressExtension.FileUploadProgressAttributes.init(filename: Swift.String) -> FileUploadProgressExtension.FileUploadProgressAttributes the workaround i found is to add the file with the FileUploadProgressAttributes to my app's target, but I'm not sure if this is the right thing to do. When Xcode created the extension for me, it added the extension target as a target dependency of my app. so obviously if i added this file to my app target it makes the extension target pointless. First time working with widgets so I'm not sure if I'm missing something.

I'm an indie developer and I'm managing my builds using xcode scm (git repo) and with github. I'm at a stage when I have to work on two different things at once on my project... Enhancements Feature change At a later stage I might want the enhancements and not the feature changes, or keep both. How should I - branch, merge and/or cherry pick on the current main branch since the Initial commit?

When I try to post a LocationAnnotations of a subclass respect to the one defining variable sceneLocationView, by way of: sceneLocationView.addLocationNodeWithConfirmedLocation(locationNode: bannerAnnotationLocation) When I enter in: public func addLocationNodeWithConfirmedLocation(locationNode: LocationNode) { if locationNode.location == nil || locationNode.locationConfirmed == false { return } updatePositionAndScaleOfLocationNode(locationNode: locationNode, initialSetup: true, animated: true) locationNodes.append(locationNode) print(sceneNode?.description ?? "nil") self.sceneNode?.addChildNode(locationNode) } I find sceneNode to nil, like if the effect of the renderer is lost when subclassing. I also tried to create a new variable in the subclass also assigning SceneLocationView(), but sceneNode remains nil. What to do to force it to assume a value?

Has anyone else discovered that Xcode 26 will not open any files that aren’t code? None of my project’s Storyboard, Launch Screen, Assets, built targets, Info plist will open when I click them in the Project Navigator… I just get a blank white screen in the main pane. They still exist, however: I can build my project just fine, using the pre-existing configurations and Storyboard.

 I’ve discovered a workaround, such as it is: I can open my project back in Xcode 16 to edit my Storyboard, and then open it once again in Xcode 26 to build the project. This works, but as you can imagine, it’s a PITA. I’m also not able to access any Xcode 26 improvements to the Interface Builder, if there are any.

 Has anyone else experienced this? Or even fixed it? I can report it as a bug but I'm surprised that I haven't even found anyone else encountering this yet.

I have experienced problems with my app crashing on build (I believe it's while linking) with various combinations of Xcode version and iOS simulator version. It dates back to Xcode 16.3 in my testing, and continues through Xcode 16.4 and all Xcode 26 betas. This occurs whether the project running is UIKit-based or SwiftUI-based. Simply dropping a file with the following code into a project, without even needing to refer to its class anywhere else in the project, produces the crash. import Foundation import WebKit class WebBrowserController: NSObject, ObservableObject, WKNavigationDelegate { var webView: WKWebView override init() { self.webView = WKWebView() super.init() } func findString(_ string: String, completion: @escaping (WKFindResult) -> Void) { let configuration = WKFindConfiguration() webView.find(string, configuration: configuration) { result in completion(result) } } } With Xcode 26 beta 4 I am experiencing this issue with iOS 18.4 and iOS 18.5 simulators, but not with iOSW 18.3 or iOS 26 simulators. The complete history of my testing back to Xcode 16.3 and the problematic iOS versions is included Feedback #FB17737471. The crash message appearing in the Xcode 26 beta 4 console for iOS 18.5 is below: dyld[7438]: Library not loaded: /usr/lib/swift/libswiftWebKit.dylib Referenced from: <EF9CE2A7-9F7C-316D-869F-087AECC76C53> /Users/dennisbirch/Library/Developer/CoreSimulator/Devices/CD82152C-E407-4350-B8AE-C15B5304CA05/data/Containers/Bundle/Application/94F80728-CECE-4C24-84CF-C435069B276A/SwiftUIMissingWebViewLib.app/SwiftUIMissingWebViewLib.debug.dylib Reason: tried: '/Users/dennisbirch/Library/Developer/Xcode/DerivedData/SwiftUIMissingWebViewLib-dbhkxwiichsdtygsnxqszkylbivv/Build/Products/Debug-iphonesimulator/libswiftWebKit.dylib' (no such file), '/Library/Developer/CoreSimulator/Volumes/iOS_22F77/Library/Developer/CoreSimulator/Profiles/Runtimes/iOS 18.5.simruntime/Contents/Resources/RuntimeRoot/usr/lib/system/introspection/libswiftWebKit.dylib' (no such file), '/Library/Developer/CoreSimulator/Volumes/iOS_22F77/Library/Developer/CoreSimulator/Profiles/Runtimes/iOS 18.5.simruntime/Contents/Resources/RuntimeRoot/usr/lib/swift/libswiftWebKit.dylib' (no such file), '/usr/lib/swift/libswiftWebKit.dylib' (no such file, not in dyld cache), '/Library/Developer/CoreSimulator/Volumes/iOS_22F77/Library/Developer/CoreSimulator/Profiles/Runtimes/iOS 18.5.simruntime/Contents/Resources/RuntimeRoot/usr/lib/libswiftWebKit.dylib' (no such file) Library not loaded: /usr/lib/swift/libswiftWebKit.dylib Referenced from: <EF9CE2A7-9F7C-316D-869F-087AECC76C53> /Users/dennisbirch/Library/Developer/CoreSimulator/Devices/CD82152C-E407-4350-B8AE-C15B5304CA05/data/Containers/Bundle/Application/94F80728-CECE-4C24-84CF-C435069B276A/SwiftUIMissingWebViewLib.app/SwiftUIMissingWebViewLib.debug.dylib Reason: tried: '/Users/dennisbirch/Library/Developer/Xcode/DerivedData/SwiftUIMissingWebViewLib-dbhkxwiichsdtygsnxqszkylbivv/Build/Products/Debug-iphonesimulator/libswiftWebKit.dylib' (no such file), '/Library/Developer/CoreSimulator/Volumes/iOS_22F77/Library/Developer/CoreSimulator/Profiles/Runtimes/iOS 18.5.simruntime/Contents/Resources/RuntimeRoot/usr/lib/system/introspection/libswiftWebKit.dylib' (no such file), '/Library/Developer/CoreSimulator/Volumes/iOS_22F77/Library/Developer/CoreSimulator/Profiles/Runtimes/iOS 18.5.simruntime/Contents/Resources/RuntimeRoot/usr/lib/swift/libswiftWebKit.dylib' (no such file), '/usr/lib/swift/libswiftWebKit.dylib' (no such f dyld config: DYLD_SHARED_CACHE_DIR=/Library/Developer/CoreSimulator/Caches/dyld/25A5316i/com.apple.CoreSimulator.SimRuntime.iOS-18-5.22F77/ DYLD_ROOT_PATH=/Library/Developer/CoreSimulator/Volumes/iOS_22F77/Library/Developer/CoreSimulator/Profiles/Runtimes/iOS 18.5.simruntime/Contents/Resources/RuntimeRoot DYLD_LIBRARY_PATH=/Users/dennisbirch/Library/Developer/Xcode/DerivedData/SwiftUIMissingWebViewLib-dbhkxwiichsdtygsnxqszkylbivv/Build/Products/Debug-iphonesimulator:/Library/Developer/CoreSimulator/Volumes/iOS_22F77/Library/Developer/CoreSimulator/Profiles/Runtimes/iOS 18.5.simruntime/Contents/Resources/RuntimeRoot/usr/lib/system/introspection DYLD_INSERT_LIBRARIES=/Library/Developer/CoreSimulator/Volumes/iOS_22F77/Library/Developer/CoreSimulator/Profiles/Runtimes/iOS 18.5.simruntime/Contents/Resources/RuntimeRoot/usr/lib/libLogRedirect.dylib:/Library/Developer/CoreSimulator/Volumes/iOS_22F77/Library/Developer/CoreSimulator/Profiles/Runtimes/iOS 18.5.simruntime/Contents/Resources/RuntimeRoot/usr/lib/libBacktraceRecording.dylib:/Library/Developer/CoreSimulator/Volumes/iOS_22F77/Library/Developer/CoreSimulator/Profiles/Runtimes/iOS 18.5.simruntime/Contents/Resources/RuntimeRoot/usr/lib/libMainThreadChecker.dylib:/usr/lib/libRPAC.dylib:/Library/Developer/CoreSimulator/Volumes/iOS_22F77/Library/Developer/CoreSimulator/Profiles/Runtimes/iOS 18.5.simruntime/Contents/Resources/RuntimeRoot/usr/lib/libViewDebuggerSupport.dylib DYLD_FRAMEWORK_PATH=/Users/dennisbirch/Library/Developer/Xcode/DerivedData/SwiftUIMissingWebViewLib-dbhkxwiichsdtygsnxqszkylbivv/Build/Products/Debug-iphonesimulator DYLD_FALLBACK_FRAMEWORK_PATH=/Library/Developer/CoreSimulator/Volumes/iOS_22F77/Library/Developer/CoreSimulator/Profiles/Runtimes/iOS 18.5.simruntime/Contents/Resources/RuntimeRoot/System/Library/Frameworks DYLD_FALLBACK_LIBRARY_PATH=/Library/Developer/CoreSimulator/Volumes/iOS_22F77/Library/Developer/CoreSimulator/Profiles/Runtimes/iOS 18.5.simruntime/Contents/Resources/RuntimeRoot/usr/lib

In Xcode26/iOS26, within an navigation stack, I have a background view that fills the whole screen and the top half is covered by a map view that extends to the edge of the top of the screen. The blurring effect is displaying the blurred background and not the blurred map. Is this expected behavior or a possible bug? In the screen shot, you can see my blue backround blur is being displayed instead of a blurred image of the map that I would expect to see. Am I doing something wrong?

Just wondering if it is possible to configure a secondary macbook to act as a run destination in Xcode, similar to how you would configure an iPhone as a run destination. I have tried connecting my device via USB-C and I can see that my macbook detects the second macbook via USB but it does not show up when trying to add devices in Xcode. I suppose this flow might not be supported?

I'm not seeing the Accessibility or Attributes Inspectors in Xcode 26. Were these features removed? Xcode 16 Xcode 26