“DTiPhoneSimulatorErrorDomain Code 2”

Hi new_bee, Thanks for the response...point by point: I use the default 100 value for resultsLimit I am pretty sure that initWithCursor is hit repeatedly - see #1 qualityOfService=userInitiated PublicDatabase is used. But only my team members and people with a server-to-server key have access to the PublicDatabase unless they are accessing it through the app's code. So what's the security issue? Besides, there is almost no private information in the database queryCompletionBlock is not deprecated in Objective C and queryResultsBlock is only available in Swift - don't get me started in what a nasty thing Apple has done by converting to Swift. But none of this matters - note that the response for one Record Type differs from the response for other Record Types. This is not a programming error, it is a database maintenance issue (aka indexing).

@DTS Engineer It's still not fixed but Docker has commented on this issue via https://github.com/docker/desktop-feedback/issues/168#issuecomment-4410608279. ctalledo 16 hours ago · edited by ctalledo Hey, wanted to share some context on what's likely happening here. When VirtioFS serves the guest, Apple's Virtualization framework acts as the host-side virtiofsd — it's the one opening and holding host file descriptors on behalf of the VM. When a container stops, the guest kernel sends FUSE_RELEASE messages to signal those fds can be closed, but Apple's framework doesn't appear to be honoring them reliably. The fds accumulate until the host hits its limit, and only a Docker restart clears them because that tears down the entire VM. The gRPC FUSE workaround works precisely because it bypasses Apple's framework entirely — Docker's own Go server handles the fd management, and it closes fds correctly on FUSE_RELEASE. That the workaround is effective here suggests the issue is in Apple's Virtualization framework rat

Hi everyone! Is there an update on this issue or the posted feedback? I still run into the same in with the Xcode 25.5 RC and iOS 26.5 RC. What I do is: Rename the first model from Model to ModelV1 Copy the ModelV1 to ModelV2 Add new properties in ModelV2 Create NSStagedMigrationManager All entities are with manual/none generation. As I've already introduced usage of into: context when creating new objects, they are fine. Now the @FetchRequests fail (the one the views) with: Thread 1: executeFetchRequest:error: A fetch request must have an entity.. These are 'solvable' by creating a FetchRequest with an entity: https://developer.apple.com/documentation/swiftui/fetchrequest/init(entity:sortdescriptors:predicate:animation:). However this requires passing around the context and adding inits in a lot of places. These are two WWDC meetings with more info: https://developer.apple.com/videos/play/wwdc2023/10186 https://developer.apple.com/videos/play/wwdc2022/10120 However they don't contain clues what migh

The solution is describe here: https://developer.apple.com/forums/thread/763757. The x axis marks are causing the issue. I was able to implement a solution by following the suggested code. Now I don't have a performance issue when scrolling in charts.

I fixed the error in the actor by using this code: private var backgroundCompletionHandler: (() async -> Void)? and func getBackgroundCompletionHandler() -> ((() async -> Void)?) { return backgroundCompletionHandler } func setBackgroundCompletionHandler(_ h: (() -> Void)?){ backgroundCompletionHandler=h } func executeCompletionHandler() async{ await backgroundCompletionHandler?() } Yet my error on the app delegate at: func application( _ application: UIApplication, handleEventsForBackgroundURLSession identifier: String, completionHandler: @escaping () -> Void) { let runCompletionHandler = {@MainActor in completionHandler() } Task.init{ await GeoreferenceQueue.shared.setBackgroundCompletionHandler(runCompletionHandler) } } Converting function value of type '@MainActor @Sendable () -> Void' to '() -> Void' loses global actor 'MainActor' is still there. Now I set all functions in the actor to MainActor as well the variable storing the completion: @MainActor private var backgroundCom

[quote='887014022, dverevkin, /thread/786223?answerId=887014022#887014022, /profile/dverevkin'] that does not appear to be the case [/quote] Agreed. Since I posted that my understanding of how this stuff works has shifted, meaning that I no longer believe that the key is tied to your App ID. When you think about this it kinda makes sense. When you store a SE-protected key in the keychain, you have the option to put it in a keychain access group that’s accessible by multiple apps. If the key bytes were tied to your App ID, those other apps wouldn’t be able to use the key. So, I repeated you tests here in my office, and I see the same results. I’m able to successfully pass an SE-protected key between two apps (running on iOS 26.4.2). Pasted in below are the code snippets I used for this. Thanks for setting things straight here! Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com For the source app: func generateAndSaveKey() throw

I managed to perform multiple tests on the physical Apple Watch and I can confirm that the root cause of this problem is the app intent shared between watchOS and widget extension target. Having this file in a single target solves the issue. However, this approach can’t be used to workaround this issue because the widget configuration intent is by design supposed to be used in these two targets. Otherwise, tapping on a widget produces silent errors, which I included in the previous post. Also, sharing intents is necessary to be able to perform ClockKit complications migration and to check widgets configuration from the watchOS app. So we found the root cause, but we don’t have any suitable workaround yet. This problem is clearly watchOS bug. Additionally, I also observed that sharing the intent between iOS app and widget extension doesn’t cause this issue. So it happens only when the intent is shared between watchOS app and widget extension. Also, the problem isn’t caused by sharing the localization

I’ve responded over on that other thread because there’s no point having two threads going concurrently. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

[quote='887212022, fbartolom, /thread/825703?answerId=887212022#887212022, /profile/fbartolom'] Unfortunately using your code … produces … Sending 'completionHandler' risks causing data races [/quote] Hmmm, it didn’t when I tested it. Lemme try that again: Using Xcode 26.4, I created a new project from the iOS > App template template. As part of that, I selected Storyboard from the Interface popup. I changed the Swift Language Version build setting to Swift 6. I added GeoreferenceQueue.swift and copied my GeoreferenceQueue to it. I added my application(_:handleEventsForBackgroundURLSession:completionHandler:) method to the AppDelegate class. It built without error. But keep in mind that my example was meant to be an expedient option. I agree with Etresoft’s comments [1] that you should step back and consider whether you want to change your overall approach. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com [1] Well, the comments he

same case for me, long time to wait but no responses by email, for 2 fa auth, this may help https://appuals.com/this-phone-number-cannot-be-used-at-this-time-try-again-later-cannot-verify-phone-number-in-apple-id/