“file uri scheme”

Hi everyone, I'm working in a strictly offline (intranet) environment and cannot use the standard online installation process to download and install the Claude Agent for Xcode. What I've tried: I manually copied the Agent binary/folder from an online machine to the following path: ~/Library/Developer/Xcode/CodingAssistant/Agents/Versions/26.3/claude The Issue: Even though the files are in the correct directory, Xcode fails to recognize the agent. It doesn't appear in the settings, and the Coding Assistant remains unavailable. Questions: Is there a specific metadata file (e.g., a .plist or .json index) that needs to be updated for Xcode to see the manually added agent? Are there any code signing or quarantine issues (like xattr) that need to be addressed when moving the agent between machines? Does anyone know if there are other dependencies or cache folders (besides ~/Library/Developer/Xcode/CodingAssistant/) that need to be synchronized? Environment: macOS: 26.3 (25D122) Xcode: 26.3 (17C51

Every time I touch (add a key, remove a key, even add a key, then remove it) the Strings Catalog .xcstrings file, it re-renders the entire file and creates a 18 thousand line dif. When I looked closer, it changes the whitespace before colons! version: 1.0 version : 1.0 it does so for every JSON node. This makes the whole feature useless, because we wont be able to see what we changed upon code review (diff is unprintable in the github interface) and every time we change a single translation, we will be stacking 18k lines diff. Not to mention merge conflicts?

Hi, I am developing instant snapshot backup solution for macOS using Endpoint Security. We have stumbled upon a Kernel Panic when using fclonefileat API. We are catching a kernel panic on customer machines when attempting to clone the file during ES sync callback: panic(cpu 0 caller 0xfffffe002c495508): apfs_io_lock_exclusive : Recursive exclusive lock attempt @fs_utils.c:435 I have symbolized the backtrace to know it is related to clone operation with the following backtrace: apfs_io_lock_exclusive apfs_clone_internal apfs_vnop_clonefile I made a minimal repro that boils down to the following operations: apfs_crash_stress - launch thread to do rsrc writes static void *rsrc_write_worker(void *arg) { int id = (int)(long)arg; char buf[8192]; long n = 0; fill_pattern(buf, sizeof(buf), 'W' + id); while (n < ITERATION_LIMIT) { int file_idx = n % NUM_SOURCE_FILES; int fd = open(g_src_rsrc[file_idx], O_WRONLY | O_CREAT, 0644); if (fd >= 0) { off_t off = ((n * 4096) % RSRC_DATA_SIZE); pwrite(fd, buf, s

I've been rejected a couple of times for Guidelines 5.1.1(i) and 5.1.2(i) regarding third-party AI data sharing consent. Each time, the reviewer states they cannot see the consent prompt, even though it is the first screen displayed on every app launch. My app (GymFusion) uses Anthropic's Claude AI for features like meal scanning, body composition analysis, and workout coaching. Here is exactly what I've implemented: IN-APP CONSENT (embedded in view hierarchy, not a sheet/popup): In my RootView.swift, the consent is a conditional view that blocks the entire app: } else if !consentManager.hasConsented && !consentManager.hasSeenConsent { AIConsentView() } else if auth.isAuthenticated { MainTabView() } The hasSeenConsent flag is reset to false on every app launch in the App's init(), so the consent screen appears on every launch until the user accepts: init() { UserDefaults.standard.set(false, forKey: user_ai_consent_seen) AIConsentManager.shared.hasSeenConsent = false FirebaseApp.configure() } THE CONSE