“DTiPhoneSimulatorErrorDomain Code 2”

Thank you for the clarification. I’ve submitted FB22758653. Regarding the suggestion to migrate the data with custom code, could you elaborate more on the approach? Do you mean: Implementing a custom Core Data migration flow? My understanding is that fetch indexes may still be recreated because Core Data still detects the entity’s version hash change. Directly managing the underlying SQLite schema manually? If so, how would Core Data become compatible with the updated store afterward? I’d appreciate any additional guidance on the recommended approach here.

@ppwqgtl No confirmed solution yet, unfortunately. Reinstalling or rebooting is the only workaround we've found so far, but like you, we're worried the app could lose trust again later. To give a sense of scale: it's intermittent but extremely frequent - today ~10 people were TestFlight testing the watch app and it hit 3 of them. (I still need to get system diagnosis logs out of their watches and phones.) That said, if this were happening to most watchOS apps in TestFlight we'd expect to see far more public reports than just us. Our working theory is that being a dependent companion watch app - rather than an independent watchOS app - is what puts us on an edge-case code path. There are no public numbers on the dependent-vs-independent split, so we can't be sure, but directionally it's plausible. In 2026 independent watch apps could far outnumber dependent watch apps. One clue from our iPhone sysdiagnose: AppConduit / ACXRemoteAppList errors around the failure window, specifically App database is out

Any pointer to the correct invocation (or a Configuration Profile to enable DriverKit verbose logging) would unblock me. Two points here: I have a post here about IOLog's oddness which is worth reviewing. That post also has the macro that's supposed to log publicly, so you can confirm your logging is doing what it's supposed to do. There was one developer post about DriverKit logging weirdness, which we never heard back on. IF you determine that this is some kind of system bug, then I'd appreciate you filing a bug on this. Quinn's Your Friend the System Log and Recording Private Data in the System Log both cover how you can manage logging redaction in more detail. One detail that alluded to there is that the SystemLogging.System payload lets you disable ALL private data redaction system wide. Expanding on that last point, while I wouldn't leave redaction disabled, particularly on any machine your actually using, that does provide a quick and easy way to see exactly what data was being logged. That ca

Are you attempting to materialize the dataless file of a snapshot? That's a weird edge case where I'm honestly not sure what would happen. True. I was sure I saw the same ETIMEDOUT behavior whether or not I was using an APFS snapshot, but I can't seem to reproduce that anymore. We'll stop attempting to materialize dataless files in APFS snapshots. Yeah... There's a WHOLE lot of weird here that I'm not sure how the system would unwind. The most obvious issue is that the snapshot doesn't have any writable storage it can materialize too, but the other issue is that this entire mechanism relies on FileProviders registering the folders they manage... but the snapshot isn't going to mount at a target the file provider would have recognized as their's. In terms of blaming snapshots, I think the key point is here: 1-2 milliseconds when calling read() on a file in the APFS snapshot. Another indicator that using the APFS snapshot here is a bad idea. ...which is WAY too fast for any real processing to have occu

To anyone who stumbles across this thread in the future, I've locked this thread so it doesn't turn into a long collection of team specific issues. If your team: Has already been approved for one or more DriverKit entitlements. AND You believe there is a technical issue with the configuration you were granted (see above as an example). ...then the best way to handle that is to file a code-level support request. In that request, make sure you include the following: Your team ID. The entitlement you believe is misconfigured and a description of how it was misconfigured. A link to this post. That will get your request to me, at which point I'll sort things out without cluttering up the forums. Please note: DTS does NOT handle standard DEXT entitlement requests and is not the escalation point for general concerns or rejections. This is specifically for sorting out odd technical mistakes or edge cases, not as a general escalation point. If you receive a reply from DTS redirecting you to the forums, that’s

We have conducted performance stress tests using an LSI 3108 RAID controller via Thunderbolt 3, configured with 4 HDDs in RAID 5. The results from AJA System Test Lite (4GB, 10-bit RGB) and fio (BS=1M, iodepth=32, Direct=1) show that I/O throughput in Bundled Mode remains at approximately 800 MB/s, which is identical to the performance measured in Legacy Mode. Do either of these tests generate parallel I/O (meaning, multiple threads are generating I/O to the same target)? More specifically, I'd look at: Parallel I/O within the test itself. I/O targeting different partitions on the same target. I/O targeting unrelated targets on the same controller. Also, what does your overall I/O flow look like? Is your card receiving commands fast enough that it's processing them in parallel, even though they arrived as separate commands? What's your peak simultaneous task count? Analysis of the driver logs during these tests reveals that the count parameter in UserProcessBundledParallelTasks is consistently 1, even under h

Thanks for the post, I would recommend to put the output of the console errors on the body of the message as well will easier to see and warning and errors to that point The error I see at the last screen may happen when Xcode attempts to install your app onto a physical device, but the app or probably one of its embedded 3rd party frameworks lacks a valid code signature? If you haven't set up code signing yet, the easiest way to fix this is to let Xcode handle it. Look first at the app team dropdown and make sure everything is valid. Go to the Signing & Capabilities tab and check the box for Automatically manage signing. In the team dropdown, select your Apple Developer account/team. If your main app is signed but a third-party library or framework is not, Xcode will throw this exact error. In General, scroll down to Frameworks, Libraries, and Embedded Content. Look at the Embed column for your frameworks. If you have dynamic frameworks like .framework or .xcframework files that are not