“xcode github”

What version of Xcode are you using? I have 26.2 and still can’t add WebP assets.

I started to experience this issue three days ago - it literally came out of the blue. I've tried cleaning all possible caches, installing different versions of Xcode, and in the end went as far as to reinstall macOS completely. When this error appeared again after the clean install I was flabbergasted and devastated. I'm happy to learn that I'm not the only one facing this poltergeist. Hope Apple releases a fix soon.

Hey @DTS Engineer, if my submission is designed as an iPad app, is there a way to make sure that it is tested on a iPad simulator in Xcode and not on a iPhone simulator ?

it's Xcode 26.2 and watchOS 26.3 if it matters

I managed to get it working on my Intel MBP. Xcode downloads the Apple Silicon version of codex, but you can replace it with the Universal one (And even a later version). I had codex CLI installed through brew, and it was installed at /usr/local/Caskroom/codex/0.104.0/codex-x86_64-apple-darwin I copied this file to /Users/darrenjones/Library/Developer/Xcode/CodingAssistant/Agents/Versions/17C528 and renamed it to codex. Restarted Xcode, and I could now Sign In through the Xcode settings. Restarted Xcode again, and I could even select the new 5.3 model.

If you use your intent phrase inside of the Xcode scheme settings (there is a place called Siri Intent Query where you can type it in), does the same thing happen? If that's still giving you trouble, then the next thing I'd do is create a brand new test project in Xcode, give it an app name that's pretty unique, and bring in the basic outline of your Siri intent code, and make sure everything is working there. The goal of that is so that you review all of the integration steps again from a clean slate to make sure you didn't miss anything, as well as validating that once the code does run, you have a basic functional outline you can build upon for exploring the API as you build out the feature for your real app. Jumping ahead a step, one additional thing that trips people up when debugging their intent extension is a misunderstanding of when the code runs — it is in a separate process, and so depending how you launch it, breakpoints you set for debugging may or may not be activated. A good r

Thanks again for reporting the issue. It seems that the issue is impacting the community, but I haven't seen any feedback report ID posted here. Do folks have any feedback report yet? If not, would you mind to file one and share your report ID here? I understand that filing an actionable feedback report takes time, but that will help. I am trying to capture the issue, and yet, my current configuration, Xcode 26.2 (17C52) + iPhone 17 Pro with iOS 26.3 (23D127) + Apple Watch series 10 with watchOS 26.3 (23S620), does work for me. Best, —— Ziqiao Chen  Worldwide Developer Relations.

Thanks for your post as it seems very well written explaining the issue with the code in the end, but following your code as you just looking at a subscription is difficult to understand what is the cause of the issue. I’m not an expert in subscriptions but I wonder looking at your code if could be a Swift's concurrency issue as you are not setting the for await result in Transaction.updates ? I think the problem may b3e that your current handler, though running on @MainActor, processes transactions sequentially within that single loop. If processing takes even a few milliseconds, new updates can arrive and pile up behind the currently processing one, potentially leading to them being handled more than once if logic isn't airtight? I do believe by encapsulating your logic within an actor and using a set for deduplication, you create a predictable and thread-safe environment for handling StoreKit's asynchronous transaction updates, effectively solving the duplicate problem you've encountered. Something like th

It is not fixed on macOS 26.4 beta or Xcode 26.4 beta. I believe I have found a workaround however: Set this value in Terminal and then restart Xcode and run Update to latest package versions. defaults write com.apple.dt.Xcode IDEPackageSupportUseBuiltinSCM 1 I have verified this works for me with Xcode 26.3 and 26.4 on macOS 26.4 beta after previously having the issue above.

[quote='876690022, ZKK640, /thread/806582?answerId=876690022#876690022, /profile/ZKK640'] What are the consequences of using Xcode15? [/quote] There are a couple that spring to mind: Xcode 15 doesn’t include the iOS 26 SDK, so you won’t be able to use the latest iOS features. You won’t be able to test your submission properly, because it will ultimately be reviewed on Xcode 26. While Xcode is generally good about working with projects from older versions, the only way to be sure that it’ll work is to try it. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com