“DTiPhoneSimulatorErrorDomain Code 2”

I'm seeing a timestamp display issue on Apple Watch Notification Center, and I'd like to confirm whether this is a known watchOS behavior or whether there's a setup mistake on our side. I'm not aware of any issue like this, and the general behavior you’re describing sounds like a bug. Have you filed a bug on this and, if so, what's the bug number? Also, what system versions are you seeing this on and have you seen it on watchOS 26.5? For E2EE messaging apps, is there a recommended pattern to decrypt and return content from an NSE that avoids this drift on watchOS? In theory, what you're doing should just work. More specifically, by design, your extension doesn't control the time data of the notification you're returning, so what actually happens is that the UNNotificationContent your extension returned is immediately embedded into a newly created UNNotification object, which is then processed normally. How that would end up creating the situation you're describing is something I can't explain. However, this i

Thank you for the reply, Travis. To clarify, I have beta updates off, so this is occurring on the public release, macOS tahoe 26.5. The core issue is the system bypassing the 80% limit without any user notification. This is exactly why I’m suggesting the hardware-level 'Pulsing' indicators for MagSafe 4—to bridge the gap when the software fails to communicate these discrepancies. Please consider MagSafe 4, to make communicating any issues unmistakable. i am in the right place for this, as i am trying to develop the magsafe wire, and is a 2-in-1, feedback and development, so please consider this as a development for over 100 million macbook users. Thanks Alyaman

This isn't inexperience on your part — you've already done the hard work of getting each piece running individually. There isn't a public Apple sample covering your exact stack (MTKView + custom Metal renderer + SKRenderer + TCTouchController). The Touch Controller framework shipped at WWDC 2025, its public video coverage is limited to a brief mention in session 209 (Level up your games), and the framework documentation doesn't list any sample code project. That said, the pattern you're describing — individual pieces working, but the controls not drawing reliably when composed with a custom Metal + SpriteKit pipeline — is typically one of two things: a pipeline-state mismatch between TCTouchControllerDescriptor and the MTLRenderCommandEncoder you pass to render(using:), or an unset drawableSize on the touch controller. Both are worth ruling out first. Looking at the framework source, TCTouchController builds its internal Metal render pipeline state once at initialization, from the descriptor

Running a test comparing the overhead between regular open and what we do in anka: ❯ ./run.sh Creating sparse APFS image with hdiutil (2048 MiB cap, volume BenchAPFS) → /Users/nathanpierce/apfs-open-repro/disk.dmg created: /Users/nathanpierce/apfs-open-repro/disk.dmg.sparseimage Note: hdiutil wrote /Users/nathanpierce/apfs-open-repro/disk.dmg.sparseimage (-type SPARSE uses .sparseimage beside the requested name). Done. Image stats: -rw-r--r-- 1 nathanpierce staff 10M May 14 13:55 /Users/nathanpierce/apfs-open-repro/disk.dmg.sparseimage clonefile(2): /Users/nathanpierce/apfs-open-repro/disk.dmg.sparseimage → /Users/nathanpierce/apfs-open-repro/disk_clone.dmg Clone stats: -rw-r--r-- 1 nathanpierce staff 10M May 14 13:55 /Users/nathanpierce/apfs-open-repro/disk_clone.dmg ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ Original sparse image ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ === Phase 1: bare open(2) / close (baseline) ==

As of this posting, chdir(2) is now following symbolic links. As per the man page, this is NOT what it is supposed to do. As a small expansion to what Quinn said, it's also not clear to me how the system could work if it DIDN'T follow symbolic links. Theoretically, you could expect everyone to call realpath() before calling chdir, but the file system is an inherently unstable collection of race conditions[1]... so correctness would actually require looping between realpath & chdir until timing worked out such that you got a realpath[2] that happened to not include any symbolic links. UNIX's broad semantic is to make symbolic links as invisible as possible, which allows apps that choose to ignore their existence without any additional effort. You can imagine a system that didn't work that way, but the APIs for that would look much more like how bookmarks are handled than the way symbolic links work. [1] Many apps, particularly command line tools, are written in a way that ignores this rea

@DTS Engineer - I might have spoke too soon, as today I had a Kernel Panic crash after sleep and it is still happening after day 3 of being on 26.5. I can send the .panic file if needed. I ran it through Claude and the error is definitely related to a network monitoring tool. In my use case: Root Cause: Kernel panic caused by a Kernel Tag Check Fault (MTE violation) in the SentinelOne Network Monitor Extension (com.sentinelone.network-monitori, pid 725) while performing packet inspection/filtering via the NEFilterExtensionProviderContext on CPU core 5. The crash occurred shortly after the MacBook Pro M5 Pro woke from sleep. The ESR value (0x0000000096000011) confirms an ARM data abort due to a memory tag mismatch, indicating a memory safety bug (likely use-after-free or stale pointer) in the SentinelOne network extension's kernel code path. This is consistent with the previously documented N1 wireless chip / Cisco Secure Client kernel panic pattern on M5 Pro devices.

There are two type of certificates involved. The first is the MDM push certificate. An MDM server uses this to send MDM pushes to managed devices. It is associated with an Apple Account. The second is the MDM vendor certificate. The MDM vendor uses this to sign the CSR during the issuance process for an MDM push certificate. This is associated with an Apple Developer Program account or an Apple Developer Enterprise Program account. So you're asking what happens when the Apple Developer Program or Apple Developer Enterprise program account associated with an MDM vendor certificate expires?

Hello @AdrianSim Yes, please share your code here as well as in a feedback report filed through Feedback Assistant. Once you file the report reply with the feedback number here, so I can share that report with the relevant engineering team. Some things worth investigating: iOS provides a wide range of text sizes for the user to select from. When using default text styles, your app will automatically respond to the user's preferred text size. Confirm that your physical device has the same settings in Settings > Accessibility > Display & Text Size on both devices. I'm also curious if the physical device has the same Language and Region settings located in General > Location & Region, which could also have an effect here. For more information see Typography and Font.  Travis

To clarify - the two images above are from the same app. First image is 26.2 where the toolbar buttons are tinted based on the background. Second image is 26.4 where the toolbar buttons are tinted based on the appearance mode (light/dark - matching the sheet)