Hello, I am very new to programming for iPhone, so please excuse me if this question is ignorant and I'm missing something silly. I am trying to build an app for my phone (iPhone SE 3rd gen) using my Macbook Air (same Apple Account). I downloaded XCode and started with the default "Hello World!" template. I created a personal team and figured out all the settings on my phone (trusted the computer, turned on developer mode, trusted the account). However, after uploading, I get the following error: The weird part is that I have a stable internet and cell connection. Following the instructions given to me in the similar error on my Mac, I head to General -> VPN and Devices -> my account and click "Verify App". This gives me a pop-up: Clicking Verify, it loads for a second and absolutely nothing happens. Not sure how to proceed or what's wrong.

Title says it all. I type a colon when Xcode is set to Vim mode, and for some reason the line number pop-up comes up, as if I'd typed Command-L. Why is that? I feel like it didn't do this in the past; I could have sworn I used to be able to close editor tabs by typing :x. At any rate, this is incorrect behavior; jumping to line numbers in vim is done by just typing the number followed by a capital G. Is there any way to turn this off? I couldn't find anything in the shortcuts preferences.

Hi Apple, I’m exploring the built-in MCP support in Xcode 27 and noticed that the available Xcode MCP tools don’t seem to provide a way for an agent to manage Swift Package dependencies. For example, an agent can inspect and modify source code, build the project, run tests, and diagnose build issues. However, I haven’t found an MCP tool that allows the agent to perform operations such as: Add a Swift Package dependency to an Xcode project Remove a Swift Package dependency Add/remove a package product from a target Change the version/branch/revision requirement of a package dependency For example, I’d like to be able to give an agent an instruction such as: Add https://github.com/xxx/SomePackage.git to the project, use version 1.2.0 or later, and link the SomePackage product to the MyApp target. At the moment, it appears that the agent can identify that the package is missing when compilation fails, but it cannot actually perform the package configuration step through the Xcode MCP tools. Is Swift Package dependency management intentionally not exposed through Xcode MCP at this time? If it is not currently supported, are there plans to expose APIs/tools for managing: Package dependencies Package products Target-package relationships Package version requirements This would be particularly useful for coding agents, since adding a dependency is a common part of an otherwise automated development workflow. I've submitted a request to feedback, the id is FB24676163. Thanks!

M4 Mac Mini: Xcode generates private keys with wrong label - codesigning impossible Background This is a follow up to my November 2024 thread "Keychain issues after installing backup on new Mac" which was closed because I had a temporary workaround. That workaround using my wife's MacBook Air for signing is not sustainable. I used AI assistance to determine the root cause. My DTS case 102877839447 is open but has not yet been forwarded to a DTS engineer. Environment Mac Mini M4, macOS 15.4.1 (Build 25E253) Xcode 26.4.1 (17E202) Team ID: Q23726668V (Computerade Products) Working comparison machine: MacBook Air, macOS 15.3 Precise Bug — Reproducible Every Time Every time Xcode generates a new certificate and key pair on my Mac Mini: Certificate: Apple Development: Michael Birch (9KD5TCGGHG) ✅ Private key: Apple Development: Michael Birch (Computerade Products) ❌ The key uses the organization name instead of the certificate identifier. They never pair as a valid codesigning identity. security find-identity -v -p codesigning always returns 0 valid identities. Cryptographic Evidence The internal application labels confirm the keys are cryptographically unrelated to their certificates: Key internal application label: 53C26EB056997276B5E938258D00665ACABD1F0F Certificate public key hash: 57cd1af4a9162f26b1a6d750e05a63a2166b75ff These do not match ❌ Confirmed Eliminated As Causes Keychain search list corruption — found and fixed Partition list — set correctly Access control — set to allow all applications Full Disk Access — granted to Xcode Xcode caches and preferences — completely cleared Login keychain — completely reset Orphaned certificates and keys — all removed SIP enabled, system fully up to date Valid P12 Import Also Fails A p12 exported from the working MacBook Air and cryptographically verified as a matched pair also fails on the Mac Mini: security import returns MAC verification failed Keychain Access import returns OSStatus -2 Importing certificate and key separately as PEM files succeeds but they are not recognized as a valid identity pair despite matching application labels A3F3F193B7896DA9055353F59AB450778CB09AE7 Question Is there a known issue with M4 Mac Mini keychain infrastructure where private keys are generated with incorrect internal application labels? Is there a lower level diagnostic or fix beyond what the security command provides? The problem is specific to my Mac Mini M4 and persisted thru more than a year of Mac OS and xCode updates.

Please help me i waiting for long time can not got email back, what wrong? We are processing your order and will send you and activation email when it's ready. Please note that it may take up to two business days to process your order.

[Q] Is it a known issue that the Xcode static analyzer hallucinates past results? Basically, the issue I've been observing for a few releases of Xcode now (including 27b) is that if you run a static analysis, fixes the reported issues and re-run a static analysis, you will get exactly the same results as with the first run. It's as if Xcode did not take into account the fixes. If you clean the builds (cmd + shift + K), and run the analysis again, this time, you will get up-to-date results.

I was looking for my app's Application Support folder and was confused to see hundreds of folders with names like 36FE5C78-6D16-4556-8F13-80B0F2E7AD4B-84238-0000088F9B63C05B cluttering the Data folder. Some of these folders are empty, some contain a file named something like 791DC593-238F-4180-9D5D-6ABB7D22A4D3-18720.profraw. It seems that whenever I run any of my tests in Xcode, a new folder is generated and all the old ones are never removed. What's the purpose of these folders and why are they not removed automatically?

Environment: Xcode 27.0 beta 6, Device Hub, tvOS 27.0 When focusing a TextField and using Device Hub to run on tvOS 27.0, I cannot type any text into the field. Focus moves to the TextField as expected, but keyboard input is not received. Has anyone else run into this? Any workaround would be appreciated.

Is there a way to simulate Display Zoom settings under the Appearance tab in Settings on a device simulator? I can only find this setting in my real device.

Hey all, the codex sign in isn't working for me in Agents. I am using the 26.5 release candidate version. It always says "Not Signed In". I have completed the Sign In process multiple times. Anyone else seeing this? I have filed Feedback FB22732574

When tapping on Info.plist the editor area stays completely empty and doesn´t show Info.plist

After tapping topmost project name in navigator area xCode won´t show the editor area to update the Project / Target pages and General tab

Each time I launch a Debug version of the app on iOS Simulator, I see the Launch Screen presented and then about a 30-second delay before the app is responsive and debug output appears in the console panel. Filed FB22345091

Translated Report (Full Report Below) Process: Xcode [3530] Path: /Applications/Xcode.app/Contents/MacOS/Xcode Identifier: com.apple.dt.Xcode Version: 26.6 (24959) Build Info: IDEApplication-24959000000000000~2 (17F113) Code Type: ARM-64 (Native) Role: Background Parent Process: launchd [1] Coalition: com.apple.dt.Xcode [1786] User ID: 501 Date/Time: 2026-08-17 23:51:47.2077 +0100 Launch Time: 2026-08-17 23:51:47.0576 +0100 Hardware Model: MacBookPro18,2 OS Version: macOS 26.6.2 (25G83) Release Type: User Crash Reporter Key: A48FA3EB-7CA7-3507-8300-E41E5EDD5284 Incident Identifier: 7B4676E3-9607-4890-B61E-04DE788BC3C3 Time Awake Since Boot: 1000 seconds System Integrity Protection: enabled Triggered by Thread: 0, Dispatch Queue: com.apple.main-thread Exception Type: EXC_CRASH (SIGABRT) Exception Codes: 0x0000000000000000, 0x0000000000000000 Termination Reason: Namespace SIGNAL, Code 6, Abort trap: 6 Terminating Process: Xcode [3530] Thread 0 Crashed:: Dispatch queue: com.apple.main-thread 0 libsystem_kernel.dylib 0x189cb05e8 __pthread_kill + 8 1 libsystem_pthread.dylib 0x189ceb8d8 pthread_kill + 296 2 libsystem_c.dylib 0x189bf1978 abort + 148 3 libsystem_c.dylib 0x189bf1a94 abort_report_np + 84 4 Xcode 0x102238ed0 main.cold.1 + 36 5 Xcode 0x102238e1c main + 340 6 dyld 0x1899204e4 start + 6992 Thread 0 crashed with ARM Thread State (64-bit): x0: 0x0000000000000000 x1: 0x0000000000000000 x2: 0x0000000000000000 x3: 0x0000000000000000 x4: 0x0000000000000073 x5: 0x000000000000002e x6: 0x000000016dbc7248 x7: 0xfffff0003ffff800 x8: 0x05371949b50970d8 x9: 0x05371948437bd158 x10: 0x0000000000000002 x11: 0x00000000fffffffd x12: 0x0000000000000000 x13: 0x0000000000000000 x14: 0x0000000000000000 x15: 0x0000000000000000 x16: 0x0000000000000148 x17: 0x00000001f7d6b358 x18: 0x0000000000000000 x19: 0x0000000000000006 x20: 0x0000000000000103 x21: 0x00000001f672a260 x22: 0x0000000102a04ce0 x23: 0x00000001f6731908 x24: 0x0000000000000001 x25: 0x000000016dbc76a0 x26: 0x00000001f672ba70 x27: 0x0000000000000000 x28: 0x0000000000000000 fp: 0x000000016dbc73c0 lr: 0x0000000189ceb8d8 sp: 0x000000016dbc73a0 pc: 0x0000000189cb05e8 cpsr: 0x40001000 far: 0x0000000000000000 esr: 0x56000080 (Syscall) Binary Images: 0x102238000 - 0x10223bfff com.apple.dt.Xcode (26.6) <8025d4bb-71ea-3f57-bade-2e3c847b6cf3> /Applications/Xcode.app/Contents/MacOS/Xcode 0x189ca7000 - 0x189ce42e7 libsystem_kernel.dylib () /usr/lib/system/libsystem_kernel.dylib 0x189ce5000 - 0x189cf1b3b libsystem_pthread.dylib () /usr/lib/system/libsystem_pthread.dylib 0x189b79000 - 0x189bfa1e7 libsystem_c.dylib () /usr/lib/system/libsystem_c.dylib 0x189900000 - 0x1899b34ff dyld () <74e52480-c2bd-3c8d-812d-95fe2b74a096> /usr/lib/dyld 0x0 - 0xffffffffffffffff ??? (*) <00000000-0000-0000-0000-000000000000> ???

For the life of me, I cannot find how to bring up the Siri Remote in the Apple TV Simulator in Xcode 27 Device Hub (Beta). Is it no longer available? I have always seem to have had issues using the computer's keyboard for navigating my tvOS apps. Maybe it's me, but the Siri Remote always worked perfectly fine. I hope the remote will make a reappearance in the next beta... ?

Xcode 27.0: Apple TV Simulators fail to navigate to some buttons in a UIViewController via keyboard arrows. Works fine with Xcode 26 (Siri Remote) simulator and also works as expected on an actual Siri Remote for Apple TV device running tvOS 27 Beta. Anyone else experience issues with navigating their app's UI using the Mac keyboard in Device Hub? Any tips for tracking this down?

When I try to download the metal toolchain 26.6 (17F109) in Xcode it just stays on preparing to download. Does anyone have an idea on how to fix this? I'm on macOS 26.6.1 (25G76)

Hi systems programming guys. I’m exploring the macOS as a low-level itself, so when I use the otool(1) utility to inspect a tiny objc helloworld program, it told me that there is a shared library like /usr/lib/libobjc.A.dylib (not identical) but I didn’t find that in path /usr/lib/. Also the docs sucked (see below). I want to know more details about the objc runtime on macOS (beta 27.6 +) and be seeking for help here because there are few materials online and not even to say the sucked AI. The prima motivation is the runtime itself and how it works. Of course I would love to read disassembled code and manpages or using utilities that Apple offered to understand those things . But I really don’t know where is the runtime if both docs and otool output lied. The latest documentation about Objective-C Runtime is outdate and it said “Objective-C runtime library support functions are implemented in the shared library found at /usr/lib/libobjc.A.dylib.”

In Xcode 27 Beta 4 (27A5228h), building a project that has a SwiftPM binary target (xcframework) linked directly from both an app target AND a framework target that is embedded in that app fails with "Multiple commands produce" errors. The same project and pbxproj builds successfully in Xcode 27 Beta 3 (27A5218g), so this is a regression introduced in Beta 4. Steps to Reproduce Create a new iOS App project. Add a Framework target (e.g. "SampleCommon") and embed it into the app. Add a SwiftPM dependency for a package that vends a binary xcframework product. Confirmed with airbnb/lottie-spm 4.6.1 (https://github.com/airbnb/lottie-spm). In "Frameworks, Libraries, and Embedded Content" of the app target, add the SwiftPM product (Lottie) with "Embed & Sign". In "Frameworks and Libraries" of the framework target, add the same SwiftPM product (Lottie). Build the app scheme for iOS Simulator. Expected result Build succeeds. The xcframework is embedded exactly once into the .app bundle. This is the behavior in Xcode 27 Beta 3 and Xcode 26. Actual result Build fails with: error: Unexpected duplicate tasks error: Multiple commands produce '.../<App>.app/Frameworks/Lottie.framework/Lottie' error: Multiple commands produce '.../<App>.app/Frameworks/Lottie.framework' Two Copy tasks are emitted for the same output path in the app target: Copy from Build/Products/Debug-iphonesimulator/PackageFrameworks/Lottie.framework Copy from SourcePackages/artifacts/lottie-spm/Lottie/Lottie.xcframework/ios-arm64_x86_64-simulator/Lottie.framework Additionally, an auto-generated target named "Lottiedynamic-product" emits duplicate MkDir / ProcessInfoPlistFile tasks for PackageFrameworks/Lottie.framework, which suggests the packaging path for binary xcframework products has been duplicated in Beta 4. Regression Xcode 27 Beta 3 (27A5218g): builds successfully Xcode 27 Beta 4 (27A5228h): fails with the above errors Xcode 26.x: builds successfully Minimal reproduction The issue reproduces on a 2-target Xcode project (app + framework) with airbnb/lottie-spm added and linked from both targetstory captures the smallest triggering diff: pattern1: app links Lottie only -> BUILD SUCCEEDED pattern2: framework links Lottie only -> BUILD SUCCEEDED pattern3: both app and framework link Lottie -> BUILD FAILED (only on Beta 4) Only the framework target's packageProductDependencies and Frameworks build phase entries differ between the succeeding and failing states. Workaround Link the SwiftPM binary product from only one target (either the app or the framework, not both). If only the framework tarl gets the framework transitively at runtime. Impact Any project that uses a SwiftPM binary xcframework and organizes code across multiple linked targets (a very common pattern for larger apps) is blocked from adopting Xcode 27 Beta 4. Environment Xcode 27.0 Beta 4 (27A5228h) macOS 26.5.2 Package: airbnb/lottie-spm 4.6.1 Destination: iOS Simulator (iPhone 17, latest)

First of all, let me just state that I'm trying to create an app with an AI, so if that's not allowed in this forum, let me know. I'm not an experienced app developer, far from it, so please excuse my ignorance. I have used PC/Windows machines for decades, so the Apple/Mac stuff is foreign to me. My app development but ran into a snag. We're trying to get the app in Xcode to test run on my iPhone 16 Pro. It works in the simulator but fails on the iPhone. It all boils down to the keychain password that keeps popping up. I have only created four different passwords for Apple/Mac and Keychain won't accept any of them. How do I change the keychain password? I have read articles on it but no luck. Appreciate any help. '24 Mac Mini, M4, Tahoe 26.6.2 Xcode 26.6