“eskimo”

[quote='905863022, galenqqqq, /thread/726936?answerId=905863022#905863022, /profile/galenqqqq'] Seems to be still broken from my side. [/quote] Well, “broken” isn’t the word I’d use, in that it’s working as designed but we (that is, you, me, and the other folks on this thread) would like the design to change. But, yeah, AFAIK there’s been no changed in this space. The best way to track the issue is to file a bug and ask that it be marked as a dup of the bug we’re using to track this internally (r. 103863792). Our bug system will then notify you if things change significantly. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

[quote='906004022, MatteoMonizza, /thread/805681?answerId=906004022#906004022, /profile/MatteoMonizza'] I can reproduce in my app. [/quote] Good to know. [quote='906004022, MatteoMonizza, /thread/805681?answerId=906004022#906004022, /profile/MatteoMonizza'] I've opened … FB24065741 [/quote] Thanks for that. Does it still reproduce in iOS 27.2b1 (24B5084k)? Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

[quote='905862022, mklnz5, /thread/679370?answerId=905862022#905862022, /profile/mklnz5'] Is there really no way to do this in 2026? [/quote] The situation with app group containers hasn’t changed. Well, the situation with app group and their containers has changed a lot in the last five years, but there’s still no way to set up a container that’s shared by your sysex and its container app. If you’re curious about the evolution app groups in general, I have a long post about that: App Groups: macOS vs iOS: Working Towards Harmony [quote='905862022, mklnz5, /thread/679370?answerId=905862022#905862022, /profile/mklnz5'] I have some files which the system extension needs at runtime which is updated by the main app. [/quote] That’s not a good idea security-wise. Your sysex runs as root and the container app doesn’t, so having the sysex trust data written by the app represents a privilege inversion. The best way to approach this depends on the nature of these files: If the app downloads them from the ’net then you

I think we are, again [1], very much in implementation detail territory here. When I add productbuild to the ACL for a key, it ends up using the apple: as the partition ID, but I don’t think behaviour is actually documented anywhere. Although, weirdly, the security man page specifically lists apple: as appropriate for codesign, so you could reasonably file a bug requesting that we document that it’s appropriate for productbuild as well. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com [1] For those following along at home, fortens-dev has been asking a bunch of questions like this and they’re definitely bumping into the boundaries of what’s considered API. See my reply here for more context.

[quote='847152021, fortens-dev, /thread/847152, /profile/fortens-dev'] Can a custom macOS .pkg be signed with a cloud-managed Developer ID Installer identity … ? [/quote] No. This came up about a year ago and that resulted in an ER (FB20115488) that remains unresolved. In that case the developer was able to hack their way around this limitation, but their approach wasn’t based on cloud signing. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

Lemme start by dropping a link to the older thread on this topic. The obvious path here is to release the app with its base feature set and then apply for this access. That has a couple of benefits: You start getting real world experience with your app sooner. It’d help the Apple folks looking at your request understand that request in context. However, I don’t think there’s anything stopping you from applying before your app is released. Once you register your app record, the app name and App Store URL are both available in App Store Connect (for the latter, go to the app record, select Distribution at the top and App Information on the left, and then scroll to the bottom and look for the View on App Store link). Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

Let’s discuss your situation on your specific thread. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

[quote='847166021, mvduin, /thread/847166, /profile/mvduin'] Unfortunately it's not clear how to properly report this [/quote] Via Feedback Assistant. [quote='847166021, mvduin, /thread/847166, /profile/mvduin'] feedback assistant doesn't seem to have applicable options for this. [/quote] Select Developer Tools & Resources > Open Source. I have a bunch of hints and tips on this topic in Bug Reporting: How and Why? Please post your bug number, just for the record. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

[quote='847171021, MostlyStable, /thread/847171, /profile/MostlyStable'] I have already submitted a comprehensive sysdiagnose archive and wireless diagnostic log package directly to Apple … FB24842970 [/quote] Thanks. That’s the best path for this. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

[quote='847164021, jrchestang, /thread/847164, /profile/jrchestang'] Filed as FB24843805. [/quote] Thanks. That’s the right path for this. Did this change in the late betas? Or did you only just start testing it? Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

From that other thread it looks like you resolved this by adopting SMAppService, which is something I actively recommend. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

You’ve asked questions about a bunch of different protocols, and they all have the same general answer: These protocols exist to support the desired features of the new Network framework API. Let’s take at BelowProtocol as a specific example. It’s an associated type on NetworkProtocolOptions. When a type conforms to NetworkProtocolOptions, it tells the compiler which type is ‘below’ this type in the protocol stack. For example, the TLS struct conforms to StreamProtocol which in turns conforms to NetworkProtocolOptions. TLS sets its BelowProtocol to TCP, indicating that TLS has to be layered on top of TCP. So, you can write code like this: let connection = NetworkConnection(to: endpoint) { TLS { TCP() } } but if do this you get an error: let connection = NetworkConnection(to: endpoint) { TLS { UDP() // ^ Cannot convert value of type 'UDP' to expected argument type 'TCP' } } The above means that this question: [quote='847233021, CTMacUser, /thread/847233, /profile/CTMacUser'] I can't determine if I should use t

Remember that the goal of DevForums is to help developers build products for Apple platforms. Given that, I can answer the implicit question here, namely, “Should I ship an installer package that relies on the the Apple installer following symlinks?” And the answer to that is, as I’m sure you’re aware, “No.” If that’s not the question you want answered, feel free to reply back here with more details, but please keep in mind tip 3 of Quinn’s Top Ten DevForums Tips. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

This is working for me. Specifically: Using Xcode 27.0 on macOS 26.6.1, I created a new project from the macOS > Command Line Tool template, choosing C as the language. I updated main.c to look like the code at the end of this reply. In the scheme editor, I selected Terminal from the Console popup. I ran the app, it opened Terminal, and I was able to interact with the program … lots of stuff elided … OSLOG-21DD5FFC-1D59-4DB9-B000-EB48DC9FE9F1 7 80 I 0 {version:2} Initialization successful Enter world type: Cruel Hello Cruel World Process exited with status 0 Saving session... ...copying shared history... ...saving history...truncating history files... ...completed. [Process completed] What version of macOS are you testing this on? If you run through the above steps, do you see the same problem? Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com #include #include #include #include int main(int argc, const char * argv[])

[quote='847249021, flyOfYW, /thread/847249, /profile/flyOfYW'] We have reviewed the documentation for identifierForVendor and App Transfer, but we could not find … [/quote] Right, and that kinda tells you all you need to know. The identifierForVendor docs quite detailed, so if they don’t cover your specific case then you should follow the advice at the end of the docs: you should gracefully handle situations where the identifier changes. If I were in your shoes I’d use something else to associate this instance of your app with your back end. The key attribute of identifierForVendor is that it’s shared between all the vendor’s apps on the device, and if you don’t need that then you can avoid this complexity but, say, generating a random UUID and storing that in a file in your app’s container. That will definitely persist across app transfer. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com