Or is it just me does anybody else see this issue or are you seeing it properly? I had to go to developerthe apple.com/operating systems sorry are you using voice control but I had to go to the actual website to get the notes for today July 6 2026 around 240 or so I even tried logging out of my iPhone assistant app logging back in it's showing the old ones from about two or three weeks ago. It's not a big deal I'm just trying to figure out if anybody is seeing this?

I couldn’t find a way to simulate the Apple Watch double-tap gesture in the watchOS Simulator. Is there a keyboard shortcut or another way to trigger it? I’m implementing support for double tap in my app, so being able to test it in the Simulator would be really helpful. If anyone knows whether this is possible, I’d appreciate the help!

Hi, I have two questions: Is there any way to test the revoke consent flow on a local build of our app? When I try using Sandbox to "Revoke App Consent" with the application bundle ID of a locally built and deployed app, it fails with "Cannot Trigger Notification. The bundle ID you provided is invalid or you do not have access to the app." https://developer.apple.com/support/age-assurance/#responsibility states that "When a parent or guardian revokes consent for their child to access an app, Apple will prevent the app from launching." However, when using the Sandbox to revoke app consent, the app is still launchable. Does anyone know if the app being launchable is exclusive to Sandbox, and how this works in prouduction?

Hello, I am having problems with my app icon in App Store Connect and Xcode Cloud. I replaced the app icon with a new one (including the 1024×1024 App Store icon), committed and pushed all changes to GitHub, and Xcode Cloud successfully created a new build. However, App Store Connect and TestFlight still seem to show the old icon in some places. In Xcode, the new icon is visible, and the asset catalog appears to be correct. I have already tried: Replacing the PNG files. Checking the Contents.json file. Committing and pushing all changes to GitHub. Creating new Xcode Cloud builds. Deleting and downloading the project again. Has anyone experienced a similar issue? Is there any caching mechanism in App Store Connect or Xcode Cloud that could cause the old icon to remain visible? Any suggestions would be greatly appreciated. Thank you!

Hello, I am looking for guidance on how to pre-provision TCC permissions for automated desktop app testing on the macOS 27 beta. We have maintained a CI testing setup by saving snapshots of VMs with pre-configured user TCC databases. This allowed our UI tests to run without being blocked by permission prompts. This included permissions like screen recording, full disk access or apple events. On the macOS 27 beta, this workflow appears completely broken. While the system TCC database seems to function as it used to, the user TCC database has been moved into a ProtectedSystem container. Direct modifications to the user database now seem impossible. Is there any officially supported way to pre-provision user-level TCC permissions on macOS 27 VMs for automated CI environments? Is Apple's intention here that the system DB is the only one that's actually editable (with SIP disabled)? How does Apple recommend CI platforms handle user-level permission prompts in headless or automated VM environments moving forward? Any insights or recommended alternative workflows would be greatly appreciated. Thank you!

Hi everyone, I've been working on a problem that I think many of us building AI in Swift are facing: how do you debug why an AI agent behaves differently between runs? Traditional logging tells you what happened. But when a model skips a step, changes its reasoning order, or produces a different output with identical input — you're left staring at walls of logs with no clear answer to why. I've released DProvenanceKit — a reasoning observability framework for Swift that lets you: Record every reasoning step an agent takes (non-blocking, async-safe) Query for reasoning patterns ("find runs where X happened but Y didn't") Diff two executions to see structural differences Detect regressions automatically with rule-based validation Think of it as Git for AI logic. Example: Swift // Record an execution try await DProvenanceKit.run(contextID: "case-123", store: store) { DProvenanceKit.record(.documentEvaluated(documentID: "DocA", score: 0.95)) DProvenanceKit.record(.conflictDetected(reason: "timeline_inconsistency")) DProvenanceKit.record(.finalDecisionMade(approved: false)) } // Query for suspicious patterns let suspiciousRuns = try await store.queryRuns( TraceQueryDSL() .requiring(step: "conflictDetected") .missing(step: "documentEvaluated") // Find runs where conflict was reported but no docs evaluated ) // Diff two runs let diff = engine.diff(base: runA, comparison: runB) print(diff.changes) // See exactly which steps appeared, disappeared, or moved The design: Built specifically for on-device AI (macOS/iOS) with Apple Foundation Models, MLX, or Core ML Non-blocking recording (touches only in-memory buffer) Durable, crash-safe persistence with SQLite WAL Works with async/await context propagation Status: Experimental (core engine complete, actively evolving). Free for development/testing under BSL 1.1. GitHub: https://github.com/Therealdk8890/DProvenanceKit I'm curious if this resonates with anyone here building AI in Swift. What debugging/observability challenges are you facing with AI systems?

Earlier from the apple documentation, there was an option to get the API difference between OS. That option is no longer present. How do we get the API difference now. Is there anyway we can get this.

There are two beta restore files for A16, both are for ipad15,8. Please post one for ipad15,7

When resizing using Device Hub, it becomes completely black and gets stuck at 2560 × 1440.

i'am still getting crash while testing dotnetmaui my app, here is my environment info and crash report @shanselman macOS Tahoe 26.5, macOS Rider 2026.1.2 dotnet workload list Workload version: 10.0.300.3 Installed Workload Id Manifest Version Installation Source ios 26.5.10284/10.0.100 SDK 10.0.300 maccatalyst 26.5.10284/10.0.100 SDK 10.0.300 maui-android 10.0.20/10.0.100 SDK 10.0.300 maui-ios 10.0.20/10.0.100 SDK 10.0.300 xcodebuild -version Xcode 26.5 Build version 17F42 crash-report.txt

I can’t make or edit new feedback or drafts, this just shows up or it takes too long to load.

https://developer.apple.com/download/foundation-models-adapter/ Download link to toolkit is borked: https://developer.apple.com/services-account/download?path=/Developer_Tools/Foundation_Models_Framework_Adapter_Toolkit/adapter_training_toolkit_v0_1_0.zip

I have a notarized Apple Silicon application running on macOS Tahoe 26.5.1, and in File Info's General section it reports 'Kind: Application (Apple Silicon)'. In its Info.plist, NSPrincipalClass is set to 'NSApplication'. Running lipo on each of the app's executables reports 'arm64'. In the Software | Applications section of System Information, though, it is shown as 'Kind: iOS'. Can anyone suggest why this might be? The application is not built using Xcode, rather it is built on the command-line using make etc. Thanks for any advice!

Hello there everyone. I've got numerous support projects using old school development. Things from Objective-C to RxSwift and UIKit. I've tried the LLM/Agents and they just destroy the codebase over time, so I have given up. The final straw was trying to get it to fix a POSTCODE validation issue which was using some novel ways to provide validation in place using RxSwift. Has anyone had any luck with these LLMs on Legacy codebases? Would love to hear tips.

I can run v1 of Parallax Previewer just fine, but v2 pops up an error on open. In console I can see a crash log that states that CoreRe.framework is looking for _FigSTSCreate inside the system's MediaToolbox.framework. I guess Tahoe doesn't have that. Is there a new version coming that works on Tahoe? or a workaround? I couldn't find an existing discussion about this. thanks.

Platform and Version Platform: iOS iOS Version: 17.0+ Development Environment: .NET MAUI (C#, .NET 9) Network Layer: HttpClient with HttpClientHandler Description of the Problem We are facing an issue where HttpClientHandler.ServerCertificateCustomValidationCallback is not being invoked when the app is in a terminated (kill) state. In normal app lifecycle states (foreground/background), the callback is triggered as expected and allows us to handle server certificate validation (e.g., for certificate pinning or custom validation logic). However, when the app is in a killed state and is relaunched due to a notification action, the callback does not execute. We would like to understand: Why ServerCertificateCustomValidationCallback is not invoked in this scenario Whether this behavior is expected within iOS networking/runtime constraints Any recommended approach or workaround to ensure certificate validation still occurs when handling notification-triggered flows from a terminated state Steps to Reproduce Ensure the app is force-terminated (kill mode) Configure a push notification with category: "INVITE_CATEGORY" Include custom notification action buttons Tap one of the custom actions This triggers app launch and network call using HttpClient Expected Behavior ServerCertificateCustomValidationCallback should be invoked during the network request initiated after tapping the notification action, allowing custom certificate validation.

I added a dummy view - copy paste directly from the Apple Developer Documentation, in a swift package using swift 6 and got concurency error. The fix is to switch to swift 5

Hi, anyone managed to make this work? https://developer.apple.com/documentation/backgroundassets Trying for past few days and can't make it work. Following their official documentation, also this video https://www.youtube.com/watch?v=M3jpgZrB1uo, but it seems I am stuck at: try await AssetPackManager.shared.ensureLocalAvailability(of: assetPack) What I did: Manifest files created, info.plist configured, asset pack created and uploaded to appstoreconnect via transporter, successfully assigned to app and ready for internal testing. Added to my code: let assetPack = try await AssetPackManager.shared.assetPack(withID: "Tutorial") try await AssetPackManager.shared.ensureLocalAvailability(of: assetPack) let videoData = try AssetPackManager.shared.contents(at: "Videos/Introduction.m4v") but no luck at all.... is anywhere any demo project available to download to compare with my project?

I used to develop iPhone apps about a decade ago and am now back at it with an iPhone and companion Apple Watch app. Why does it suck so bad? I a must be doing something wrong, but what I am doing is out of the box. The majority of the time when I go to build on the watch I get: Previous preparation error: A connection to this device could not be established.; Timed out while attempting to establish tunnel using negotiated network parameters. Which I then first try to force quit the app on the watch and if that does not work, reboot the watch (which is pretty ridiculous). I tried Gemini and it gave me the following explanation: This is arguably the single most frustrating error in the entire watchOS development ecosystem. As an expert, I can tell you that you are not doing anything wrong; you are fighting a fragile architecture. Here is the technical breakdown of why this happens and a workflow to mitigate it without constant reboots. The Technical "Why" This error message reveals that the issue lies in the CoreDevice (and formerly usbmuxd) infrastructure, specifically in the secure transport layer. The "Tunnel" Failure: Xcode attempts to establish a secure, encrypted tunnel (DTXConnection) to the Apple Watch to push the debugger and the app binary. Unlike the iPhone, which can sustain a high-bandwidth connection easily, the Watch aggressively manages its radios (Bluetooth vs. WiFi vs. AWDL) to save battery. The "Handshake" Timeout: If the Watch is on Bluetooth (Low Energy) when Xcode initiates the tunnel, the bandwidth is insufficient. The system tries to escalate the connection to WiFi (or Apple Wireless Direct Link). If this negotiation takes even a few milliseconds too long—due to 2.4GHz interference, router mDNS configuration, or the Watch CPU being throttled—the handshake times out. The "Previous Preparation Error": This is the insidious part. Once the handshake fails once, Xcode’s device service caches that failure state for the device UUID. It marks the device as "unreachable" to prevent the IDE from hanging indefinitely on subsequent tries. Why you see it constantly: You aren't actually triggering a new connection attempt; you are hitting the cached "failed" state immediately. Unfortunately, the solutions it gives me are: The "Wired Proxy" Method (Most Reliable) This is the gold standard for watchOS debugging. Do not rely on "Connect via Network" for the Watch directly if you can avoid it. Disable WiFi on your Mac (temporarily) or ensure the Mac and iPhone are on the exact same SSID. Plug your iPhone into the Mac via USB. Ensure the Watch is paired to that iPhone. Result: Xcode will tunnel the instructions through the USB connection to the Phone, and the Phone acts as a high-bandwidth proxy to the Watch. This eliminates the "Mac-to-Watch" WiFi negotiation failure point. Do you hit this regularly? What do you do to make for a smooth development and deployment process? Or is it really this fragile? Thanks for any help! Bryan

I'm a solo developer and owner of my companies account. I'm trying to sign on to my Mac so I can use my developer account to get a certificate for wallet use and to select the correct developer account for applications in Xcode. I'm am brand new to all this so apologize if I'm missing the simple solution. I'm not able to edit the roles of my developer account but being an Admin I should already have all the necessary access...I think. I get an error when trying to logon as a work account: Searching for the long error doesn't provide a solution in the forum or through search engines. AI says to check the roles.