“DTiPhoneSimulatorErrorDomain Code 2”

You'll have to provide a whole lot more background here. What are you coding in Perl? An app? How is Perl related to it? I'm unaware of any environment variables being blocked. If you're trying to integrate something like Perl into an app, you aren't going to be able to use basic techniques like you would in a bash or zsh shell. There is more than one way to do it, but it depends on detailed answers to those questions above.

[quote='887338022, Nickkk, /thread/825481?answerId=887338022#887338022, /profile/Nickkk'] should I then extract the sysdiagnose and look in the system_logs.logarchive file? [/quote] Yes. Alternatively, if this happens on a Mac you control, you can generate a log snapshot like so: % sude log collect [quote='887338022, Nickkk, /thread/825481?answerId=887338022#887338022, /profile/Nickkk'] In the sysdiagnose I uploaded to Feedback Assistant I can only see the last 5 minutes, is that correct? [/quote] If you open the log in Console, it defaults to showing the last 5 minutes. The Showing popup between the two panes lets you control that filter. See the screenshot in this post. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

So I’m asking by a perspective as a consumer level of using VM apps built by other developers. Thanks for that clarification. The Apple Developer Forums are primarily focused on helping developer with code-level questions, so you’re not really in the right place. Having said that, I can provide some insight. macOS has two virtualisation APIs: Virtualization is a high-level API that makes it very easy to run a VM. Hypervisor is a low-level API for developers who need a lot of control. Neither has support for battery pass through. It’s feasible for a developer using Hypervisor to support battery pass through to guests that aren’t running macOS. Doing that for macOS guests would almost certainly require a bunch of unsupported reverse engineering. If you were a developer using these APIs then I’d recommend that you file an enhancement request for this feature. However, as a user of VM apps then that’s probably not the best path forward. It’s fine for users to file ERs for user-level stuff, but i

SOLVED but this needs to be addressed by engineers - both the actual issue and the incorrect auto-generated App Review response that led us on a wild chase. I reproduced the install failure on a physical iOS device through TestFlight, and the real blocking error is not UIRequiredDeviceCapabilities. The device installation log shows MIInstallerErrorDomain Code 152 with AppexBundleContainsClassOrStoryboard, because the [APPNAME]DeviceActivityReport.appex for com.apple.deviceactivityui.report-extension contains NSExtensionMainStoryboard or NSExtensionPrincipalClass, which iOS says is not allowed for that extension point. This seems to be a known issue reproducible on iOS 18 and 26. This creates a validation conflict: removing NSExtensionPrincipalClass makes App Store Connect reject the upload with “Missing Info.plist values. No values for NSExtensionMainStoryboard or NSExtensionPrincipalClass found,” but including it causes the install to fail on device. In other words, there is no plist configuration t

Hi Kevin, Hi Quinn Thank you very much for the very quick replies. Almost an honor to hear from two literal dev forum legends so quickly. Much appreciated. Thanks in advance. I will add all the requested detailed info into the feedback app, asap. Hopefully as early as Monday when i'm in the office. In the meantime I can give you some reply already, should you guys chose to already be working/looking at it over the weekend (who knows). To correct a statement of mine: With Wi-Fi off I meant via the control center. Naive me forgot completely that it doesn't really turn off the wifi interface. Obviously, turning it off completely via the Settings app will result in noop for the framework and that makes obviously sense. So please ignore that statement, i made a mess there. Some answers I can give you already though (Based on Kevins list): Our apps mainly work on iPads. And it affects ALL iPad devices on/since iOS 26 as far as we can tell. Theoretically theres not much more detail needed other than attempt

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.