“eskimo”

[quote='885236022, tanmingwei, /thread/134115?answerId=885236022#885236022, /profile/tanmingwei'] Is this still not supported? [/quote] Which bit? As I mentioned above, I think the best way forward would be for Apple to enhance macOS to support something like an iOS keyboard extension, where the input method is packaged as an app extension, ideally one that’s supported in the App Store. If you agree, I encourage you to file an enhancement request explaining your use case. And please do post your bug number, just for the record. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

Thanks for confirming. And it turns out that this is easy to reproduce: Using Xcode 26.4, create a new project from the macOS > Library template, and choose to create a Cocoa static library. In the resulting .h file, remove the whole @interface block. And in the .m file, convert the @implementation block to a category. For example: @implementation NSUUID (Foo) - (void)test { } @end Choose Product > Build. This issues the following warning: libtool: warning: 'Foo.o' has no symbols This actually makes some degree of sense: Xcode has run libtool to convert the various object (.o) files in the target into a static library (.a). There’s only one object file. It only contains a category. Objective-C categories don’t publish any symbols. Consider this: % nm …/Foo.o 0000000000000000 t -[NSUUID(Foo) test] U _OBJC_CLASS_$_NSUUID 0000000000000028 s __OBJC_$_CATEGORY_INSTANCE_METHODS_NSUUID_$_Foo 0000000000000048 s __OBJC_$_CATEGORY_NSUUID_$_Foo 0000000000000014 s l_OBJC_CLASS_NAME_ 0000000000000088 s l_OBJC_LABEL_

[quote='885147022, Quappi, /thread/812973?answerId=885147022#885147022, /profile/Quappi'] It would be great if that behavior could be re-evaluated [/quote] To recap my advice from this post: We already have an ER on file for general, macOS-style support. If you have specific requirements — ones with constraints that might them easier to achieve — I encourage you to file your own ER describing them. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

[quote='885107022, vishalsehgal, /thread/821116?answerId=885107022#885107022, /profile/vishalsehgal'] Based on this, my current understanding is [three bullet points] [/quote] Your three bullet points are all correct. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

[quote='885167022, kunal_a, /thread/817264?answerId=885167022#885167022, /profile/kunal_a'] As of now the 25F5053d is not yet available [/quote] It’s not longer available. Here’s a quick summary of the releases: Version | Build | Date ------- | ----- | ---- macOS 26.5b1 | 25F5042g | 2026-03-30 macOS 26.5b2 | 25F5053d | 2026-04-13 macOS 26.5b3 | 25F5058e | 2026-04-21 We released 26.5b3 between when I replied yesterday and when you checked, and hence b2 had disappeared by the time you went looking. [quote='885167022, kunal_a, /thread/817264?answerId=885167022#885167022, /profile/kunal_a'] 23F5043g did not fix the issue [/quote] That’s an iOS build number (note the leading 23). At this point I recommend that you re-test with macOS 26.5b3 and then reply back here with the results. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

[quote='885202022, boilerla220, /thread/820379?answerId=885202022#885202022, /profile/boilerla220'] I guess worth clarifying also is what is meant by user session. [/quote] Right. I generally try to follow the terminology from TN2083 Daemons and Agents. A system extension [1] is effectively a launchd daemon and thus runs in the global context. It can’t reliably access the window server. And any XPC service it calls upon will be similarly restricted. However, the GPU lifecycle isn’t tied directly to the window server lifecycle, so there is some wiggle room there, and that’s the point I’m still working to clarify internally. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com [1] Non-DEXT system extensions. DEXTs are weird (-:

My point is that your proof-of-concept app has proved that concept during development. Once to get to the point of submitting an OHTTP relay, you’re past that point and thus your submission should be for an actual product. But, hey, that’s just my take on things. As I mentioned above, I’m not involved in the approval process for this stuff. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

Your specific questions are about App Review policy. I don’t work for App Review, and thus can’t offer definitive answers on their behalf. If you want to talk to them about their policy, you can contact them via the various channels described in Developer > Distribution > App Review [1]. However, my experience, based on conversations I’ve had with developers, is that App Review rarely approves folks to use temporary exception entitlements [2]. Depending on your app’s intended user experience, you might be able to approach this differently, as explained in Implementing Script Attachment in a Sandboxed App. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com [1] You could also start a thread here on the forums, in the App Store Distribution & Marketing > App Review subtopic, but my experience is that threads that ask questions like this tend to get redirected into one of the above-mentioned channels. [2] Which isn’t

I’m not going to be able to answer questions about FIPS compliance, which is more of a legal issue than a technical issue. You might have more luck asking this over in the Apple Support Community, run by Apple Support, and specifically in the Business and Education topic area. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

[quote='823524021, Youssef-Hammad, /thread/823524, /profile/Youssef-Hammad'] how do crash reporters work on macOS ? [/quote] They don’t )-: Well, not in all circumstances |-: I have a long and involved explanation of crash reporting techniques in Implementing Your Own Crash Reporter. On macOS you have more flexibility than you do on iOS, in that you can do crash reporting both in and out of process. Sadly, neither is a good option: With in-process crash reporting your crash reporter can fail due to the process’s state being corrupted, which is the sort of thing that triggered a crash in the first place. When working out-of-process it’s hard for the crash report to get access to the information it needs in a supported way, that is, something that’ll work in the long term. Regarding your specific issue: [quote='823524021, Youssef-Hammad, /thread/823524, /profile/Youssef-Hammad'] [can I] avoid the normal macOS dialog entirely [/quote] Not in any supported fashion. The issue here is that the exact hook used by th

How is your installer invoking SMAppService? By running the app as a command-line tool from the post-install script? Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

What Albert said plus… Most folks who ask about this are trying to satisfy some government or industry security regulation. Is that the case here? If so, which one? One example of such regulation is UPI, which has a specific affordance in the Messages UI framework, namely the -setUPIVerificationCodeSendCompletion: method. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

OK, I have some results. First up, TLS. Apple’s QUIC implementation requires TLS and there’s no special affordance for this within Wi-Fi Aware [1]. Given that, you’ll need to come up with your own TLS strategy. For a quick test you can just: Hard code the TLS digital identity on the server side. Disable TLS server trust evaluation on the client side. In a real product you’d need to do something better than that. I have a bunch of suggestions in TLS For Accessory Developers. If you want to dig into the details, I recommend that you start a new thread with your questions, because I’d prefer to keep this thread focused on the relationship between Wi-Fi Aware and QUIC. [1] It’s a much-requested feature though (r. 158253982). Apropos that, there are a couple of bugs you have to work around: Set includePeerToPeer on the parameters you use to create your Network framework objects (r. 175045182). Use the original Network framework API, rather than the one we introduced in macOS 26, meaning NWConnection rather than Ne

Sorry for the delayed reply. Your thread got lost in my to-do list )-: [quote='815830021, kaloramik, /thread/815830, /profile/kaloramik'] Or shall I file a bug here? [/quote] Yes. Well, actually an ER, but that distinction isn’t really that important. See Bug Reporting: How and Why? for advice on how to do this, and 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

Bah, again, I’ve just not had time to get back to this. If I were in your shoes I would: Create a minimal test project that illustrates the issue. That’ll ensures that there isn’t some other part of your app that’s causing problems. Run it on two devices connected over infrastructure Wi-Fi. If that doesn’t work, there’s something wrong with your code. Run it again with the devices not on infrastructure Wi-Fi, and thus relying on peer-to-peer Wi-Fi to carry the packets. If that fails, file a bug with your results. Make sure to include: Your test project. Sysdiagnose logs taken on both devices shortly after reproducing the problem… … with additional logging enabled per the Network Diagnostics for iOS/iPadOS instructions on our Bug Reporting > Profiles and Logs. 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