“eskimo”

I discuss the most common causes of problems like this in Resolving App Sandbox Inheritance Problems. However, those are all 100% reproducible. A given executable will either crash on launch or not. An intermittent problem like this is much less common. The crash report you posted has this: The code signature is not valid: Impossibile completare l’operazione. (Errore OSStatus -67034). where error -67034 is errSecCSStaticCodeChanged. That suggests that you’re hitting the issue described in Updating Mac Software, or something like it. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

The Apple Developer Forums are focused on supported techniques, and this sort of thing is most definitely not supported. There are other sites on the ’net where you’ll find folks interested in topics like this, and I suspect you’ll get better results by engaging there. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

What Kevin said plus: If you’re doing this for day-to-day testing, don’t use Developer ID signing. Developer ID is best reserved for distribution. See The Care and Feeding of Developer ID for more about this. Rather, use Apple Development signing. See Debugging a Network Extension Provider for advice on how to set up that workflow. Make sure you get the Apple Development process sorted out first. Once that’s working, then move on to Developer ID. And when you do that, be aware of the issue discussed in Exporting a Developer ID Network Extension. ps Your post is quite hard to read. See tip 5 in Quinn’s Top Ten DevForums Tips for advice on that front, especially the stuff about code blocks. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

AFAIK Mac Catalyst apps can access the microphone. However, you have to keep in mind that a Mac Catalyst app is pretty much a Mac app, so you have to follow the Mac rules: If you have the hardened runtime enabled, you need to sign your app with the com.apple.security.device.audio-input entitlement. If you have the App Sandbox enabled, you need to sign your app with the com.apple.security.device.microphone entitlement. You have to add NSMicrophoneUsageDescription to your Info.plist [1]. Please try this out and let me know how you get along. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com [1] There are some cases where the Info.plist properties use different keys on the Mac vs other platforms. I don’t think that’s the case here. It’s NSAlwaysAllowMicrophoneModeControl for everyone.

[quote='825515021, rbmanian75, /thread/825515, /profile/rbmanian75'] when i tried it with multiple displays it does not work. [/quote] Correct. Multiple displays are not currently supported. [quote='825515021, rbmanian75, /thread/825515, /profile/rbmanian75'] Why do we have it as an array if it does not support multiple displays? [/quote] Normally I avoid answering why questions — see tip 3 in Quinn’s Top Ten DevForums Tips — but in this case it’s not much of a stretch: If, at some point, we add support for multiple displays, we won’t need to change the API. It matches the other xyzDevices properties on VZVirtualMachineConfiguration, which are all arrays. If you have a specific need for multiple displays, please do file an enhancement request that describes your requirements. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

I’m not really a Linux person, but I suspect that you can make progress on this by playing with the commandLine property in the VZBootLoader VZLinuxBootLoader. ps I’d appreciate you creating your virtualisation questions in App & System Services > Core OS. When you created them in Developer Tools & Services > Developer Forums, I have to move them over by hand. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

You created two threads for very similar issues, this one and SF Authorization Plugin View Not Receiving Focus on macOS Tahoe 26.4.1. My question is: Is this issue also a 26.4 regression? That is, if you run the same test on, for example, macOS 26.2, do you see the same problem? Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

You’re not the first developer to notice this 26.4 regression. See this thread. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

[quote='886729022, JohannesD, /thread/825142?answerId=886729022#886729022, /profile/JohannesD'] I'm wondering why it didn't work. [/quote] It’s hard to say, but the general answer is that wrangling launchd jobs is a pain. If you can avoid that — for example, by using an XPC service — then life will be a lot easier. [quote='886729022, JohannesD, /thread/825142?answerId=886729022#886729022, /profile/JohannesD'] What is the benefit of loading the dynamic lib from the XPC service … ? [/quote] The XPC service runs in a separate process, which allows for both fault recovery and sandbox customisation. I was under the impression that the fault recovery part was the reason why you were suggesting running an executable. [quote='886729022, JohannesD, /thread/825142?answerId=886729022#886729022, /profile/JohannesD'] Or would this somehow allow me to distribute my editor app through the App Store? [/quote] That wasn’t the reason I suggested this approach. [quote='886729022, JohannesD, /thread/825142?answerId=886729022#886

[quote='886796022, rbmanian75, /thread/784051?answerId=886796022#886796022, /profile/rbmanian75'] Any update on this whether mac os 27 will have this feature? [/quote] We can’t talk about The Future™. See tip 3 in Quinn’s Top Ten DevForums Tips. If and when this changes, you should be informed via FB17582343 in Feedback Assistant. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

[quote='886834022, bvsdev, /thread/825268?answerId=886834022#886834022, /profile/bvsdev'] Are session delegate methods thread safe when running multiple downloadTasks on it? [/quote] A session always calls delegate methods from the context of the operation queue that you supply when you create the session. You can change that queue to suit your needs: If you want all the delegate callbacks for a specific session to be serialised, pass in a different serial queue for each session. If you want all delegate callbacks across all sessions to be serialised, create a single serial queue and use that for all your sessions. A good serial queue to use is .main. If you don’t want to use the main queue, create a serial queue like so: let q = OperationQueue() q.maxConcurrentOperationCount = 1 IMPORTANT If you don’t set maxConcurrentOperationCount, you get a concurrent queue, which will can be very confusing in this context. One challenge here is that these serialisation isn’t visible to the Swift compile, so you need to t

I’ve always tested this with a Personal Team because my Individual team is from work and that’s problematic for this sort of test [1]. From your post it wasn’t clear whether you tried this with a Personal Team or not? If not, please do. That’ll let us distinguish between general borkage and a Personal Team / Individual team discrepancy. [quote='886773022, sam-elegantchaos, /thread/787500?answerId=886773022#886773022, /profile/sam-elegantchaos'] The app I'm testing uses iCloud and so I can't test it using a personal team. [/quote] OK, but you can still run this test by creating a new test project that’s not tied to Xcode Cloud. Just make sure you add a restricted entitlement to the project so that you exercise the provisioning profile path. I like the Maps capability for this, because it’s one of the few capabilities that’s available to a Personal Team and unequivocally requires a restricted entitlement. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo

Regarding your overall goal, Swift concurrency really needs a good equivalent to Foundation’s Timer, but I’ve yet to see any progress on that front. That’d be a good thing to raise via Swift Evolution. Regarding your current approach, I suspect you can do a lot better than what you posted. If you want to explore improving this, my advice is that you start a thread on the Swift Forums, and specifically in Swift Forums > Using Swift area. I’ll definitely see that go by, and I’ll reply there with my own thoughts, but I’ll also be interested in hearing what the Swift experts have to say about this. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

Interesting. Consider this: % find /Applications/Xcode.app -name '*polyfills*' …/Platforms/AppleTVOS.platform/Developer/SDKs/AppleTVOS.sdk/usr/lib/libc++polyfills.a …/Platforms/DriverKit.platform/Developer/SDKs/DriverKit.sdk/System/DriverKit/usr/lib/libc++polyfills.a …/Platforms/iPhoneOS.platform/Developer/SDKs/iPhoneOS.sdk/usr/lib/libc++polyfills.a …/Platforms/WatchOS.platform/Developer/SDKs/WatchOS.sdk/usr/lib/libc++polyfills.a …/Platforms/XROS.platform/Developer/SDKs/XROS.sdk/usr/lib/libc++polyfills.a …/Platforms/MacOSX.platform/Developer/SDKs/MacOSX.sdk/usr/lib/libc++polyfills.a Note how the library is present for all the real device platforms but is missing for all the simulator platforms (like iPhoneSimulator.platform). I suspect that the root cause of this issue is that this combination simply wasn’t anticipated. However, I’d like to learn a little more about your setup before I send you off to file a bug. I tried reproducing this with a new project created from the built-in iOS > App template, but

FYI, this came up recently in another thread. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com