“DTiPhoneSimulatorErrorDomain Code 2”

You are correct that nested virtualisation is not supported with macOS guests. Beyond that, I’m not sure if there’s much useful info I can give you. Let’s look at your remaining questions: [quote='827663021, trukhinyuri, /thread/827663, /profile/trukhinyuri'] 2- If not, should this be treated as an intentional current limitation … ? [/quote] Yes. [quote='827663021, trukhinyuri, /thread/827663, /profile/trukhinyuri'] 3- Is there a supported host-side API or validation behavior to detect this limitation before creating or starting the VM? [/quote] I don’t understand this question. As you’ve pointed at, the nested virtualisation properties are on VZGenericPlatformConfiguration rather than VZMacPlatformConfiguration, and creating a macOS guest requires the latter. Thus this lack of support is visible to you at compile time. There’s no need for dynamic validation. One consequence of this is that, if support for this were added in the future, it would require new API. If and when that happens, you’ll be ab

I have had this exact issue off and on over the past few months. I am using Codex to help code my app and finally after some extensive debugging and setting up a simple test App specifically to test CloudKit syncs, Codex came up with a fix for me. In summary: Fixed CloudKit sync wakeups by replacing the shared SyncSignal subscription with per-device subscriptions. After this simple change, all the data sync between my MacBook Air, iPhone, and iPad has been rock-solid. Hope this helps someone.

Thanks, @DTS Engineer. I haven’t tried that exact workaround, but I expect it works. Defining the label differently also avoids the issue with less code, so there are multiple workarounds. The bigger issue is the tap feedback. Tapping outside the SF Symbol but inside the visible button can show the normal bounce animation without triggering the action. If the action doesn’t run, the button shouldn’t look like it accepted the tap. This feels related to another issue I reported, where a disabled button still bounces like an active button:

Is AppTransaction.shared expected to work for macOS apps distributed through TestFlight? Yes. If yes, what does StoreKitError code=2 indicate in this context, and what setup might be missing? It represents networkError(URLError), which indicates that a network error occurred. You can find it by handling the error in your code do { let result = try await AppTransaction.shared ....... } catch let error as StoreKitError { print(error.localizedDescription) } For more information, see Handling errors and Error Handling. For macOS apps that need a device-bound trust signal comparable to iOS App Attest, is AppStore.deviceVerificationID intended to be used without AppTransaction.shared, or should these APIs be used together? AppStore.deviceVerificationID is used for transaction verification. For more information, see deviceVerificationID.

Thanks for the post. When you use a custom label: closure containing only an Image, SwiftUI sizes the button exactly to the intrinsic bounds of that image. If the image is small, like a standard SF Symbol, the minimum tap target size of 44x44. You can explicitly define a minimum frame for the image. However, when you expand the frame of an image, the empty space around it might not register taps. To fix this, apply .contentShape(Rectangle()) to tell SwiftUI that the entire bounding box should be interactive. In place code using your code above without using Xcode. Button { print(Button 3 tapped) } label: { Image(systemName: 3.square.fill) .frame(minWidth: 44, minHeight: 44) .contentShape(Rectangle()) } Albert
  Worldwide Developer Relations.

I’m still hoping that someone can explain under what circumstances xCode or KeyChain Access would generate a new certificate and private key that are not paired (code signed). My M4 Mac Mini was setup using a Time Machine backup but I lost the private key. I used Claude and Gemini AI to guide me but none of their ‘solutions’ worked. Their latest suggestion was to create this post. A complete factory reset and rebuild of my Mac Mini without using a Time Machine backup would probably solve the problem but without understanding what caused it.

Thanks for your post. Could you please provide additional details about the bug? If possible, please include the code that reproduces the issue. This information will be invaluable in identifying a workaround or a fix promptly. Do you get the same results with just the relevant code in a small test project? If so, please share a link to your test project. That'll help us better understand what's going on. If you're not familiar with preparing a test project, take a look at Creating a test project. I'm sure many engineers here are looking forward to your simple focused project. Albert
  Worldwide Developer Relations.

Could this be related to how file permissions or attributes are set during createItem? Yes, absolutely. FSKit and the VFS layer may be using this data, but even if they weren’t, many tools/apps preflight operations before they perform them. Related to that point, this kind of real world testing: Terminal command: rm -rf /path/to/mounted/file option + cmd + delete to remove the file in Finder ...isn't all that useful when you're trying to get a file system working. A simple tool like rm is 600+ lines of code, but that's ignoring the fact that it's built on fts which pulls in even more code. For diagnostic purposes, you want to know exactly which syscalls occurred and what/how they failed, but either of those tests is FAR too high a level to determine that. The better approach here is to write your own very basic test tool, so you can see exactly what's going on. Looking at specific details: entitlements required for removeItem to be invoked? No, nothing like that is required. Similarly: Is th

Alright, I'll just have to try that but, is there a camera app out there that can set custom filename or watermarks but that uses the similar or same camera codes that native ios system camera uses ?