Hi, I’m a paid Apple Developer Program member and I’m seeing an entitlement issuance issue with ShazamKit. ShazamKit is enabled for my App ID (com.tomharris.dnbidfinder) in Certificates, Identifiers & Profiles. However, every iOS Development provisioning profile I generate does not include the entitlement: com.apple.developer.shazamkit verified this by decoding the downloaded .mobileprovision file: security cms -D -i .mobileprovision | /usr/libexec/PlistBuddy -c "Print :Entitlements" /dev/stdin The entitlement dictionary does not contain the ShazamKit key. Because of this: • The signed .app does not contain the Shazam entitlement • SHSession.match(signature) fails on device • I receive ShazamKit runtime error 201 / 212 I’ve already: • Toggled ShazamKit off and back on for the App ID • Created new provisioning profiles • Created a brand new App ID to test • Refreshed profiles in Xcode The portal UI shows ShazamKit as enabled, but the entitlement is not being issued into provisioning profiles. Has anyone experienced this before? Is there an additional approval step required for ShazamKit, or could this be a backend entitlement propagation issue? Thanks.

My Family Controls (Distribution) capability request (C4N7962252) was approved March 15, 2026 for bundle ID com.jedsiegel.unplugtogether. All three Family Controls capabilities are enabled on the App ID. When I generate a provisioning profile (manual or automatic), Xcode reports: "Provisioning profile doesn't match the entitlements file's value for the com.apple.developer.family-controls entitlement." I decoded the profile using security cms -D and found: com.apple.developer.family-controls.app-and-website-usage → present com.apple.developer.family-controls → missing entirely My entitlements file requires com.apple.developer.family-controls with value ["individual"] for AuthorizationCenter. I've tried toggling capabilities off/on, deleting and recreating profiles, switching between automatic and manual signing, and clearing provisioning profile caches. Nothing works because the profile generation itself is not including the entitlement. Team ID: Q4RA4WMD6K Xcode 26.3, targeting iOS 26.2 Has anyone encountered this? Is there a way to get the provisioning system to include this entitlement?

For the last 2 days, the claude agent has stopped working, it's not the issue where you get logged out after 8 hours, I have signed out and back in multiple times, quit xcode, nothing is working, every request just generates the following response: "Your request couldn't be completed."

Several app developers are struggling with the inability to provide a separate app icons that looks nice on older macOS versions while at the same time provide Icon Composer icons that look great on macOS Tahoe 26. An ability to provide separate icons is super important to those who have app icons that follow the curvature of the default icon borders (as the corner rounding radius is different for Sequia and Tahoe). Take a look at this for example: https://github.com/ghostty-org/ghostty/issues/7564#issuecomment-3042061547 Question: Is there a definitive/recommended way to address this issue? How can a developer add a glass icon variant that looks good on Tahoe and provide a bitmap icon for older macOS versions? Some background info: Prior to Xcode 26 beta 4, one could add an App Icon to Assets to be used as app icon for legacy macOS versions (Sequia and older) and use a new Icon Composer icon (placed in the project root) for macOS Tahoe 26. Enabling "Include all app icon assets" under target settings ensured that older macOS versions would use the old app icons while Tahoe the new Icon Composer glass one. Since Xcode beta 4 this technique no longer works. Xcode instead insists on populating Assets.car with Icon Composer generated variants, disregarding the App Icon provided in Assets. Although the App Icon in Assets makes its way to a .incs file in the app bundle's Contents/Resources folder, but that is not used by macOS anymore and is there for some compatibility purposes. The Assets.car file (which matters) only contains the variants generated by Icon Composer and does not contain the png icons provided in the Assets.

I am trying to create a test case in XCTest using the UI Test target. I have a use case where I use a SwiftUI Canvas to draw a network graph; and the user can drag the graph on the Canvas. After the drag, the user may click on a node. The application presents a popup with the information about the network node clicked. SwiftUI provides the information required for the application to translate the location of the tap into the original location prior to the drag; and so the logic behind the popup can determine which node the network graph was tapped by the user. It appears that the distance of the drag operation performed does not match distance that the image actually moved. The drag distance is always larger than the actual distance dragged. I can observe this during the test execution. The arrow starts at the correct spot but then goes further than the object being dragged. I also observe this when I am driving the application. Is there some standard and supported way to determine the distance that the image on the screen was moved given a specific distance of the "thenDragTo:" coordinate?

Good day! When your project have total 887 or more SPM local targets and then you try to build it, xcodebuild will be crash. Crash log: SWBBuildService-2025-08-11-151103.ips Thread 2 Crashed:: Dispatch queue: com.apple.root.default-qos.cooperative 0 libxpc.dylib 0x197c4826c _availability_version_check + 8 1 libswiftCore.dylib 0x1a9b44428 __isPlatformVersionAtLeast + 92 2 libswiftCore.dylib 0x1a9a6e054 _swift_allocObject_ + 1100 3 SWBMacro 0x104a9c408 specialized _ArrayBuffer._consumeAndCreateNew(bufferIsUnique:minimumCapacity:growForAppend:) + 116 4 SWBMacro 0x104a97b58 specialized Array.append<A>(contentsOf:) + 116 5 SWBMacro 0x104a954e8 MacroEvaluationProgram.executeInContext(_:withResultBuilder:alwaysEvalAsString:) + 160 6 SWBMacro 0x104a96548 MacroEvaluationProgram.executeInContext(_:withResultBuilder:alwaysEvalAsString:) + 4352 7 SWBMacro 0x104a96548 MacroEvaluationProgram.executeInContext(_:withResultBuilder:alwaysEvalAsString:) + 4352 8 SWBMacro 0x104a96548 MacroEvaluationProgram.executeInContext(_:withResultBuilder:alwaysEvalAsString:) + 4352 9 SWBMacro 0x104a96548 MacroEvaluationProgram.executeInContext(_:withResultBuilder:alwaysEvalAsString:) + 4352 10 SWBMacro 0x104a96548 MacroEvaluationProgram.executeInContext(_:withResultBuilder:alwaysEvalAsString:) + 4352 But if you try to build Package.swift via swift build command, it works. Here you can open sample project: Just Package.swift with SPM 900 targets Open Package.swift via Xcode 26 any beta and try to build Xcode workspace with SPM 900 targets Open MyApp.xcworkspace and try to build You can also make by self the Package.swift (also make required directories for SPM): // swift-tools-version: 5.9 import PackageDescription // let count = 800 // no crash let count = 900 // crash let targetsNames = (1...count).map { "Pkg1Target\($0)" } let targets = targetsNames.map { Target.target(name: $0) } let package = Package( name: "Pkg1TargetLibrary", platforms: [.iOS(.v16)], products: [ .library(name: "Pkg1TargetLibrary", targets: targets.map(\.name)), ], targets: targets )

Hi, We're experiencing inconsistent and unexpected values returned by Storefront.current?.countryCode when running our app via TestFlight. In our case: The device region and locale are set to Poland The App Store account (Media & Purchases) is also set to Poland However, when running a TestFlight build, Storefront.current?.countryCode sometimes returns a completely different value (e.g. "NO" for Norway), which does not match the current App Store account configuration. Here's the code we're using: if #available(iOS 15.0, *) { let code = await Storefront.current?.countryCode print("Storefront countryCode:", code ?? "nil") } What's particularly confusing: Across different devices logged into the same App Store account, we sometimes receive different countryCode values The returned value does not seem to reflect the current App Store region or device settings We understand that Storefront reflects the App Store storefront and not the device locale, but in this case the value appears stale or incorrect even with a properly configured App Store account. Questions: Is Storefront.current?.countryCode expected to behave differently in TestFlight vs. production builds? Are there known caching or propagation delays for storefront updates across devices? Can TestFlight builds return outdated or inconsistent storefront values? What is the recommended way to reliably determine the user's App Store region in this scenario? We rely on storefront to determine regional availability of features, so understanding this behavior is important for us. Thanks in advance for any clarification!

FB19249805 Main: The option to open files in New Window Tab doesn't appear anywhere in either Preferences or the contextual menu on clicking the files in the project (unlike previous Xcode versions). Only the option to open in New Tab is available (which is useless). This BREAKS EXISTING WORKFLOWS that have been established through years for countless developers. I can only see the option to open in New Tab, which breaks all existing workflows and habits. This results in an astonishing blow to productivity. Dear Xcode team: Please restore this option immediately! Additional details: Several years ago (I've been using Xcode since version 2), Xcode renamed the normal tabs into "Window Tabs" and introduced new "Tabs". The new "Tabs" proved to be a useless and counterproductive option for the following reasons: -They cannot be used in Behaviors. (Only Window Tabs can be, and many workflows have been built around this.) -It takes much longer to load a file into a Tab than into a Window Tab (where files are loaded nearly instantly). -Navigators and Inspectors cannot be customized for individual Tabs (only for Window Tabs). -Using both Tabs and Window Tabs is not an option, as it adds another tab bar that eats an enormous part of screen real estate without providing any benefits. Fortunately, we didn't have to use Tabs and could just disable them into oblivion where they belong. Now, in Xcode 26, the option to open files in new Window Tabs is gone. Really, I can only classify it as intentional sabotage. Many years of my Xcode habits and workflows are based on opening files in New Window Tabs via the Preferences > Navigation > With Option option. Or via the contextual menu. Now this option is gone. I'm sure there are plenty of other developers in the same situation. Please reenable the option to open in New Window Tabs. Thank you for your attention to this matter!

FB22576466 Another update - another blow to developers' productivity from the Xcode team, and more time wasted. Xcode 26.4.1 reset all windows and tabs in all projects. All carefully set up window tabs in multiple projects, as well as the ones that were previously open, are gone. Developers now have to set them up manually again. Ok there's nothing that can be done in 26.4.1 already; the damage has already been done. But dear Xcode development team... just DON'T. DO. THIS. AGAIN. Please! Tanks.

Previews seemed to be working okay. However, I wanted to test out some changes inside of a package that I'm working on for work, but in a lighter project since in our main project (where I have the package pulled in locally for now) is just too big to have the previews render in a decent amount of time. So, I opened a small project that was already importing that package and was set to 'Up to Next Major', but I switched that to 'branch' and added my branch. This is the second time I've done that and it causes Xcode to freak out in terms of the previews. This is the code I have: import SwiftUI extension EnvironmentValues { @Entry var trailingDescriptionColorToken: Color = .secondary } extension View { func updateTrailingDescriptionColor(to colorToken: Color, when trigger: Bool) -> some View { environment(\.trailingDescriptionColorToken, trigger ? colorToken : .secondary) } } // MARK: - ListItemDescription public struct ListItemDescription: View { @Environment(\.trailingDescriptionColorToken) var trailingDescriptionColorToken let description: String init(_ description: String) { self.description = description } public var body: some View { Text(description) .font(.caption) .foregroundStyle(trailingDescriptionColorToken) } } struct ContentView: View { @State private var isError = false var body: some View { VStack { Button("Error Trigger") { isError.toggle() } ListItemDescription("Description") .updateTrailingDescriptionColor(to: .red, when: isError) } .padding() } } #Preview { ContentView() } As soon as I tap the button to toggle the isError state property, that causes the preview canvas to indefinitely load and spin eventually leading to a crash. This is infuriating as I've just wasted a ton of time at work trying to figure out what's going on. Xcode and SPM is so fragile and delicate that at this point I feel like if I breathe on it wrong it'll break. I'm not sure what fixed it last time. Nothing in Xcode makes sense anymore. How to I resolve this please?

I already have a working iOS React Native app and I’m planning to add a watchOS companion app. Is it possible to keep the iOS app and the watchOS app in separate repositories? If so, will WatchConnectivity still work properly between them? Or is it recommended to keep both in a single Xcode project/repository?

Hi everyone, yesterday i installed some package in my ios app , but i had a lot of problems to compile , due to reset my branch and get started from 0. My project have pods with firebase, lottie, instana and truskit but now, when a i try to run my project, xcode show "Unable to resolve module dependency" into LOTTIE, INSTANA, TRUSKIT, FIREBASE . I visited a lot of forums and websites, and i tried the followings steps: Pod deintegrate pod repoupdate pod install Clean build folder Delete derived data but isnot working. Also,I reinstalled xcode , 2 versions , i "re"clone my repository and the issue persist. Sorry, my english is basic only

I've recently installed Xcode 26.4, and it seems like all of our libraries now give multiple linker error when building of the format libtool: warning: 'Foo.o' has no symbols Most of these errors come from extensions over objc types written in objc. (for instance we have some extensions over NSArray in the file NSArray+NSSet.mm) Is that a new feature of some stricter libtool invocation? or a bug? should I do anything about it?

I am using SwiftData for my model. Until Xcode 15 beta 4 I did not have issues. Since beta 5 I am receiving the following red warning multiple times: 'NSKeyedUnarchiveFromData' should not be used to for un-archiving and will be removed in a future release This seems to be a CoreData warning. However, I am not using CoreData directly. I have no way to change the config of CoreData as used by SwiftData. My model just uses UUID, Int, String, Double, some of them as optionals or Arrays. I only use one attribute (.unique).

Hello together. Since a few weeks I have the problem, that both of my iPhones (iPhone 15 with iOS 26.4.1 and an iPhone Xs with iOS 18.7.4) are NOT recognized by xcode, but are visible in Mac Finder this is what xcode shows: When I click on that I see this: and in finder: I tried everyhting I re-installed XCode 5 times and deleted ALL XCode folders manually I restarted all devices and today I completely reinstalled my mac My Macbook has iOS 26.4.1 as well and XCode is freshly installed from App Store

Objective C projects, if that matters, but several useful editing features were removed, but the biggest issues relate to Storyboards. Action buttons were moved all around. Not sure why it was changed, as the new layout is not intuitive at all. Loading of storyboards is amazingly slow. It's been getting worse for several revisions, but it is really bad now. Connecting from the storyboard to code is non functional with this revision. Connections have to be done from the code to the storyboard only, which means all the code has to be done before storyboard changes. This is much less efficient for coding. Really dislike 26.4 editing changes. You are making our jobs harder, not easier.

Hi, I'm running Xcode version 26.0.1 (17A400). Every time I restart Xcode, it seems to not recognize my Claude login anymore, and I have to go through the whole authentication flow again. It's quite annoying. Does anyone have a solution for it?

Getting macOS app icons from Icon Composer working in Xcode 26.x appears to have caused widespread confusion. I've certainly had more than one headache from it. Here's what works for me: Drag the .icon file from Icon Composer into the Xcode Project Navigator, dropping it at the same level as Assets.xcassets — not inside it. In the Project Navigator, click the top-level project item to open the Project Editor. Select your app target and open the App Icons and Launch Screen section. Enter the icon name (without the .icon extension) in the App Icon field. In that same section, leave App Icons Source unchecked. Go to the Build Phases tab and expand Copy Bundle Resources. Delete the Assets.xcassets entry, leaving only the .icon file. Clean the build folder (⇧⌘K) and run. Your icon should now appear in the Dock. It appears that Icon Composer icons and even the presence of the Asset Catalog icons in Copy Bundle Resources are mutually exclusive right now. Including the Asset Catalog appears to suppress the Icon Composer icon. Removing it lets the Icon Composer icon through. Note: If your app depends on other assets in the Asset Catalog, this approach won't work for you. In that case, fall back to the traditional method — export all required sizes from Icon Composer and import them into the Asset Catalog. Hopefully Apple addresses this conflict soon.

今天在Xcode上使用codeX，直接给我报错了，报错原因是这个： Codex encountered an error: {"detail":"The 'gpt-5.2-codex' model is not supported when using Codex with a ChatGPT account."}

I've recently installed 26.1 Beta 3 alongside stable 26.0.1 When building my app with 26.0.1 the final .ipa size is ~17mb, however after building my app with 26.1 Beta 3 the size has increased up to ~22mb The main difference is Assets.car blowing from 1.1mb to 5.6mb (or 8.6mb if I include all icons settings). Upon examining I've found new liquid glass .icon file duplicating itself multiple times as png variants (any, dark, tinted, etc). Is anyone else experiencing this issue?