“Xcode”

Hi Quinn, Thank you for your excellent advice! I followed your guidance, specifically by enabling Automatically manage signing in Xcode's Signing & Capabilities settings and conducting an overall review of my Xcode configuration. I'm pleased to report that I've now successfully built the application. Your assistance was greatly appreciated.

In a threaded comment, @kambala said: right now CI (GH Actions) produces iOS builds as well as the .symbols files (which are generated from dSYM using symbols command), but I upload builds manually from my Mac (this will be changed in the future to upload from CI directly). I can of course also store dSYM as a build artifact, but wondered if it's possible to avoid that and store the minimal amount of artifacts on CI. As I said above, you should be keeping the entire Xcode archive, which includes the original dSYM file for any build that you ship to your customers. There's a few things that underpin this advice, including the ability to symbolicate any crash report coming from the field on any version of your app in active use, but also the ability to export your app for different types of distribution, which can enable some further testing and debugging workflows. I can't speak to the storage details of your particular CI system, but for Xcode Cloud, you are provided with the ability to down

There is potentially one detail I jumped over that is relevant — are you expecting clients of your library to build from source, or to consume a pre-compiled library? I had assumed it was a pre-compiled library based on the .a file mention. I think that's accurate, but it would be good to confirm that. If the library is intended to be a pre-compiled asset, then what you'd deliver to the client is an XCFramework. This is meant to be a single container that has everything a library client needs — copies of a built binary for each platform and simulator your library supports, plus the header files. While you can hand your clients the XCFramework so they can drag-and-drop it in their Xcode project, one nice vehicle you can use for distribution is a Swift package, which will point to a compressed (zipped) copy of the XCFramework, along with a checksum for verifying its integrity. This way, it's easy to ship updates of the library to your clients. Distributing binary frameworks as Swift packages has the de

Thanks for the email. No, to be clear, I do not recommend a re-signed of any form. I recommend to test on your device and deploy with Xcode to make sure the provisioning profile is the same. I'm not encouraging nor endorsing any other test. Hope this help Albert Pascual
  Worldwide Developer Relations.

First, thank you for taking the time to post these. We really love hearing from our developers because this helps us make the tools better. Re: OAuth — hmm, OK we're investigating. Is there any pattern to this? Do you see this after a certain amount of time? Re: Thinking — interesting, this is good feedback about how you're using thinking as progress tracking. We know about the issue where you can't open the popover until the thinking is done. But, sounds like you really want a don't put thinking in a bubble entirely because that's part of your tracking of the agent progress. Makes sense. It'd be great if you could file a feedback request specifically for this. Re: Slowness to start — yeah, I agree that sounds weird. The only way we have to debug this at the moment is if you attach the contents of your conversation via the Bug button at the bottom of the transcript. Re: Codex & Claude showing — Have you downloaded both agents using the Intelligence settings even if you haven't logged in? We support talkin

The error happens exactly when requesting to create a document. It looks like Claude is replying some document information to Xcode and Xcode cannot handle the information because it cannot be decoded as TextEditorCommand.

Thanks for the post, and welcome to Xcode and iOS development! To download iOS Simulators for Xcode 26.2, use the Components settings within Xcode. Navigate to Xcode > Settings, from the menu bar, then select the Components tab. The Platform Support section displays the latest available platform and Simulator runtimes. To obtain a previously released Simulator runtime, click the Add button (+) in the lower-left corner, select a platform, and then choose the desired version. Click Download & Install to proceed. Xcode 26.2 includes SDKs for iOS 26.2, iPadOS 26.2, macOS 26.2, tvOS 26.2, visionOS 26.2, and watchOS 26.2. These SDKs are necessary for developing and testing applications for their respective platforms. There are other methods to download simulators but if you are in Xcode, will be easier if you just use that tool to download the simulators as they should be downloaded after installation. I would also recommend to update Xcode to th