“eskimo”

[quote='905656022, Tom-chen, /thread/845979?answerId=905656022#905656022, /profile/Tom-chen'] I have provided the complete crash JSON file. [/quote] No you haven’t. That’s a human reasonable crash report (.crash) and I was looking for JSON one (.ips). It’s also truncated )-: However, it’ll probably do. Your crashing thread backtrace looks like this: Thread 0 Crashed: 0 CoreFoundation … __CFRunLoopServiceMachPort.cold.1 + 64 1 CoreFoundation … __CFRunLoopServiceMachPort + 416 2 CoreFoundation … __CFRunLoopRun + 1188 3 CoreFoundation … _CFRunLoopRunSpecificWithOptions + 532 4 GraphicsServices … GSEventRunModal + 120 5 UIKitCore … -[UIApplication _run] + 796 6 UIKitCore … UIApplicationMain + 332 7 KMMVideo … 0x104304000 + 5218892 8 dyld … start + 6928 Frame 0 and the crash type itself (EXC_BREAKPOINT) strongly suggest that you’ve hit this line. That is, CFRunLoop got back an unexpected error from Mach messaging and trapped. The crash report also includes this: Application Specific Information: (ipc/rcv) invalid

Thanks for sharing the background to your request. [quote='905643022, FxFactory, /thread/846017?answerId=905643022#905643022, /profile/FxFactory'] I presume maybe incorrectly that PlugInKit is sitting on top of ExtensionKit [/quote] Not really. PluginKit predates ExtensionKit by many years. It’s the infrastructure that underlies the original NSExtension based app extensions. ExtensionKit is kinda like version 2 of that idea, being both more modern and more capable. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

I’m not going to comment on other developers specifically, but I can confirm that a wonky main executable UUID can cause problems for local network privacy. We call that out in TN3179. And TN3178 Checking for and resolving build UUID problems has a more info about this general topic. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

I’m making good progress on this. I need to do some due diligence at my end before I say anything definitive, but there is one bit of info that’s clearly public and thus I can pass along… If you look in the Signing & Capabilities editor in Xcode 27.0 you’ll see that it has a new Cross-architecture Compatibility Framework capability. If you add that to your app, Xcode updates your project to add a claim for the com.apple.developer.cross-architecture-support entitlement and approval to use that entitlement in your provisioning profile. AFAICT we don’t have any official docs about that yet, hence the caution I opened this response with, but if you search the ’net you’ll find other folks talking about the entitlement. I hope to have another update here early next week. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

[quote='846474021, HirohikoKihara, /thread/846474, /profile/HirohikoKihara'] Too many levels of symbolic links [/quote] That’s a known issue. I’m not sure if your Intel-only plug-in is relevant here — as far as I know the other folks who’ve hit this have plug-ins with Intel and Apple silicon code — but, regardless, that’s something you need to fix. We’re rapidly approaching the end of Rosetta 2. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

[quote='846505021, fortens-dev, /thread/846505, /profile/fortens-dev'] Is there a public and supported API … that can enumerate the complete … authorization state … in a file-based Keychain? [/quote] No. There are a bunch of APIs that let you dig into the details here, but you eventually run into the limits of what’s documented. For example: If you use the public API to dig deep enough into a SecAccess object, you’ll find two ACL entries whose authorisations (SecACLCopyAuthorizations) are kSecACLAuthorizationIntegrity and kSecACLAuthorizationPartitionID. Those entries encode important state in their description property! There’s no reasonable way to interpret those descriptions without straying way off the supported path, and the second one is critical to your goal. It’s easy to interpret the bytes returned by SecTrustedApplicationCopyData (it’s basically a path) but that’s not the only state held by a trusted application object. If you rummage through the Darwin open source you’ll find that these objects als

This is an intentional change. It’s implemented by MAC, as explained in On File System Permissions. Honestly, I’m not sure whether Full Disk Answer will get around this. Regardless, you can find my general take on issues like this here. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

I can answer this from the perspective of a Network Extension URL filter, but I believe the same logic applies to Live Caller ID Lookup. In the 27.2 beta SDKs we deprecated the URL configuration Swift properties in favour of equivalent properties in your Info.plist. For example, the pirServerURL Swift property is now deprecated in favour of the NSPIRConfiguration > PIRServerURL property in your Info.plist. This mapping is straightforward, as explained here. We’ve announced that a future release will no longer honour the Swift properties and only honour the Info.plist ones. The purpose of this configuration profile is to allow you to test your code on 27.2 beta to make sure it will work properly on that future release. Download the profile from Developer > Downloads > More. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

Just a quick note to let you know that I’m not ignoring you here. I’ve been researching this internally and I’ll update this thread when I know more. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

[quote='905480022, FUELBuilder, /thread/845944?answerId=905480022#905480022, /profile/FUELBuilder'] So I’m trying to establish whether a per-user launchd job [/quote] If there were such a thing, it would be in launchd. However, launchd doesn’t have anything that’ll meet your specific requirements. You can use an XPC service to tie the lifetime of the ‘child’ to the lifetime of the ‘parent’ (in quotes because there is not a child/parent relationship in this case) but launchd will automatically terminate the service when the ‘parent’ terminates. You can avoid that by using a launchd agent, but in that case there’s no way to tell launchd to limit the runtime of the job [1]. You could add code to the program itself to do that — finally a use for SIGALRM (-: — but such code can never be 100% effective. Moreover, using a launchd job has other consequences: You have to figure out a way to remove it when you’re done, or live with the fact that the job will be present always [2]. The system alerts the user to apps ins

[quote='905453022, ControlAV, /thread/814226?answerId=905453022#905453022, /profile/ControlAV'] Local Network permissions STILL seem to be broken for some on the release version of macOS 27. [/quote] That doesn’t surprise me. If you want to help improve this, I have a bunch of suggestions in my earlier reply. One good bits of news on this front is that we’ll soon have a supported way to add and remove apps from the local network privacy list. See this reply. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

The best way to deal with this problem is to avoid creating duplicate entries. You do that by giving your program a persistent code signing identity. For day-to-day development that means signing code with an Apple Development code-signing identity. In Xcode you get that by enabling “Automatically manage signing” and then selecting your team from the Team popup. Note If you’re not a member of a paid team, you can enter any Apple Account into Xcode > Settings > Apple Accounts and use that as a Personal Team. This has significant limitations, but those are less restrictive on macOS than iOS. For the details, see Developer > Support > Choosing a Membership. If you have unwanted entries there’s no supported way to get rid of them on currently shipping systems. However, that’s changing. The first seed of macOS 27.2 beta adds (+) and remove (-) buttons below the list in Settings. Yay! For lots of other local network privacy hints and tips, see TN3179 Understanding local network privacy. Share and Enjoy

Thanks for the clarification. is cellular line selection entirely controlled by iOS Yes. And IMO it should always default to the user’s chosen line. If you’re seeing different behaviour then I encourage that you file a bug about that. Please post your bug number, just for the record. ps It’s better to reply as a reply, rather than in the comments; see Quinn’s Top Ten DevForums Tips for this and other titbits. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

[quote='905530022, EdASRQ, /thread/845743?answerId=905530022#905530022, /profile/EdASRQ'] MAYBE automating as many tasks as possible. [/quote] Good luck! But don’t let that stop you from playing with Swift in other environments. For example, I recently discovered the Cadova project [1] and I’m having all sorts of fun using it to create 3D printed artefacts (-: Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com [1] https://github.com/tomasf/Cadova