I am new to Xcode and trying to learn how to use Metal for my internship. I am trying to link the binaries of Foundation.framework, Metal.framework, and Quartcore.framework. But whenever I try to build it always fails to find any of them. I have my Header Search Path as $(PROJECT_DIR)/metal-cpp, I tried adding some for the Frameworks but that did not work either. I do have the binaries linked in the Build Phases, so I don't know what else I could be missing.

Apple could not verify “iPad_Air_M2_26.0_23A5260n_Restore.ipsw” is free of malware that may harm your Mac or compromise your privacy. xCode 26 fails to download simulators. I downloaded from the apple developer site. When I double click I get the above message. I went to the System Settings > GateKeeper, and selected Open Anyway. This poped up a window with a button, Open in xCode-bata. Clicking the button does not appear to do anything. I can not use xcode without simulators.

The “Deployment Targets” for iOS was IOS12 or higher in Xcode15, but is now listed as IOS15 or higher in Xcode16. https://developer.apple.com/support/xcode/ How does this change affect developers and users? For example, if a developer specifies less than iOS15 in the “iOS Deployment Target” on Xcode, how will this affect them? Also, will users under iOS 15 be unable to run the apps?

The latest build MacOS 26.0 Beta 25A5316i has introduced an error with the conversion tool ProjectedMediaConversion example shown at WWDC Error. I trying recompiling, but with same error: dyld[5902]: Symbol not found: _$sSo18AVAssetWriterInputC12AVFoundationE19PixelBufferReceiverC6append_4with9isolationy9CoreVideo010CVReadOnlyeF0C_So6CMTimeaScA_pSgYitYaKFTjTu Referenced from: /Users/***/Library/Developer/Xcode/DerivedData/ProjectedMediaConversion-elcmxcasetuopvghcomowlupqnuj/Build/Products/Debug/ProjectedMediaConversion Expected in: <129D07B2-72FC-32A1-8162-0E6FD4A5DB2F> /usr/lib/swift/libswiftAVFoundation.dylib

A empty macos project created using xcode. run build failed with the following error message. nothing in detail. retry no help. seems indexing takes forever!! The Xcode build system has terminated due to an error. Build again to continue.

Vision Pro or Vision Pro 2732x2048? Which one is larger? My iMac is very slow, so I wanted to use the smaller one.

I am working with a Texas Instruments RF430 NFC tag, which is compliant with: ISO/IEC 14443-4 (ISO-DEP) NFC Forum Type 4 Tag NFC-B protocol NDEF-formatted storage I’m using an iPhone 12 running iOS 18, and my app uses the Core NFC framework. Using NFCNDEFReaderSessionDelegate, I am able to successfully read the first NDEF message from the tag. However, the tag stores multiple NDEF messages, and I would like to access the others. Based on the tag’s specification, these messages are accessible via an NDEF file located at file ID 0xE104. To try and access this additional NDEF file, I attempted to use NFCTagReaderSession with the NFCTagReaderSessionDelegate, intending to issue APDU commands. However, the tagReaderSession(_:didDetect:) delegate method is never called, even though the tag is present and detected using NFCNDEFReaderSession. My questions: Does Core NFC on iOS 18 support issuing custom APDU commands to ISO 14443-4 (NFC-B) tags like the TI RF430? Is the use of NFCTagReaderSession with NFC-B fully supported for tags that implement ISO-DEP (even if they are NDEF-formatted)? Is there any known limitation or configuration required to ensure tagReaderSession(_:didDetect:) is triggered for NFC-B/ISO-DEP tags?

I used Xcode to upload to App Store Connect, and I only clicked "Distribute App" once, but the build was uploaded to TestFlight twice, resulting in build numbers 356 and 357 ( I need 356 ). But this doesn’t happen every time. Why would this happen?

Our business is to scan the code to open App Clip, but then App Clip will appear in App Library and Siri Suggestions. This can be opened quickly, but the URL of the last scan will be included. This will cause a problem, for example: if the previous scan was code A, but the user does not scan code B when going to place B and directly opens it through App Library or Siri Suggestions, the code I get is still code A, so the result I want is that I want to know where it was opened from, and then if it is opened quickly, I will clear the URL and remind the user to scan the code again. Or if it is opened by quick opening, do not include the URL

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.

For Xcode 15 and Xcode 16, whenever I try to use the Refactor->Rename command I get a spinning busy cursor for a short while then I get an alert that says: Rename Failed Refactoring engine failure. This happens on several projects and I've tried removing the derived data folder, but am at a loss to find additional troubleshooting steps. Are there other files I might remove or reset to get my "Refactoring Engine" back into shape?

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

I am trying to add in-app purchases to my app. I created a StoreKit Configuration file and checked the option 'Sync this file with an app in App Store Connect' because I have already completed the subscription setup in my Apple Developer account. I also tried implementing the in-app purchases directly without using the StoreKit Configuration file, but I’m getting an 'Invalid Product Identifiers' error. I’ve double-checked, and the product ID matches the one listed in my Apple account. Please guide me on what I should do.

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!

If I create a playground project that uses a JSONDecoder I get the following error. The LLDB RPC Server has crashed. The crash log is located at ~/Library/Logs/DiagnosticReports and has a prefix 'lldb-rpc-server'. Please file a bug and attach the most recent crash log. I have raised feedback for this, FB17702087, but I hope that there may be a workaround. The code I am using to try and get this to work is from The Apple Developer Documentation - JSON Decoder var greeting = "JSON Test 3" struct GroceryProduct: Codable { var name: String var points: Int var description: String? } let json = """ { "name": "Durian", "points": 600, "description": "A fruit with a distinctive scent." } """.data(using: .utf8)! let decoder = JSONDecoder() let product = try decoder.decode(GroceryProduct.self, from: json) print(product.name) // Prints "Durian" A screenshot of the playground showing the error The crash log (the file type has been changed to txt as ips file types cannot be selected for upload. lldb-rpc-server-2025-05-28-140832.txt

I'm using Version 16.4 (16F6) of Xcode on macOS 15.5 (24F74) and everything was working fine until I selected an older build to branch out from. Now, Xcode cant properly know the file status as it keeps on changing it after quitting and relaunching it. The changes in the file are there and when trying to commit to the local repo it doesn't show any changes to stage. At present I'm relying on making project folder backups as a way of backing up builds. Any suggestions what can be done?

I am attempting to generate screenshots at various logical times using a watchOS 11 simulator. % xcrun simctl status_bar "Apple Watch Series 10 (46mm)" override --time 9:06 An error was encountered processing the command (domain=NSPOSIXErrorDomain, code=45): Simulator device failed to complete the requested operation. Operation not supported Underlying error (domain=NSPOSIXErrorDomain, code=45): Status bar overrides not supported on this platform. Operation not supported Using WatchOS Clock Settings gives me at most 59 minutes in which to succeed. Even if I had a physical watch for every series and size, I would have to wait up to 23 hours before being able to generate my marketing screenshots to support various user scenarios. With three settings variations, a minimal wait time to get to good marketable content would be on the order of 1 month per app version.

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.

I'm new to Apple Development. I've converted a python program to swift. The operator selects a top level folder and the program moves files in and out of subFolders within the selected folder. How do I resolve the Permissions errors whenever accessing subfolders?

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?