“eskimo”

Thanks for those crash reports. Are you able to find a JSON crash report (.ips) for this? If so, please post it, because it may allow me to learn more about the issue. In the absence of that then, yeah, at first blush this is looks like an Apple problem rather than a problem with your code. Consider the crashing thread from your first crash report: Thread 22 name: Thread 22 Crashed: 0 CoreFoundation … __CFCheckCFInfoPACSignature + 4 (CFRuntime.c:559) 1 CoreFoundation … CFRunLoopSourceSignal + 28 (CFRunLoop.c:4312) 2 Foundation … performQueueDequeue + 484 (NSThread.m:1063) 3 Foundation … __NSThreadPerformPerform + 88 (NSThread.m:1077) 4 CoreFoundation … __CFRUNLOOP_IS_CALLING_OUT_TO_A_SOURCE0_PERFORM_FUNCTION__ + 28 (CFRunLoop.c:1970) 5 CoreFoundation … __CFRunLoopDoSource0 + 172 (CFRunLoop.c:2014) 6 CoreFoundation … __CFRunLoopDoSources0 + 332 (CFRunLoop.c:2059) 7 CoreFoundation … __CFRunLoopRun + 840 (CFRunLoop.c:2969) 8 CoreFoundation … CFRunLoopRunSpecific + 572 (CFRunLoop.c:3434) 9 Foundation … -[NSRunLoo

Ah, I see you reanimated two different threads about this issue. I’ll respond over on the other one. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

[quote='880810022, kappie, /thread/817887?answerId=880810022#880810022, /profile/kappie'] Here's the direct download link to the installer package: [/quote] That link doesn’t work for me (I get a 404). This: [quote='880810022, kappie, /thread/817887?answerId=880810022#880810022, /profile/kappie'] The productbuild --sign does emit Warning: unable to build chain to self-signed root [/quote] is very concerning. It suggests that the signature was created without the full certificate chain, which could easily cause problems like this. When signing code, rather than an installer package, this is actually a hard failure. I talk about it in detail in Resolving errSecInternalComponent errors during code signing and the associated Fixing an untrusted code signing certificate. So: You should definitely do what you can to investigate and resolve the unable to build chain to self-signed root warning. If that doesn’t pan out, reply back here with a download link that works and I’ll take a look. Share and Enjoy — Quinn “The

[quote='880858022, KayleeSC, /thread/791352?answerId=880858022#880858022, /profile/KayleeSC'] added to the same bug [/quote] I see that. Thanks! Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

[quote='880992022, shara7, /thread/818906?answerId=880992022#880992022, /profile/shara7'] Could you tell me whether these log entries … ? [/quote] No, sorry. I have limited time to spend on the forums, and I prefer to spend that time helping folks with code-level problems. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

[quote='881033022, robonaren, /thread/819553?answerId=881033022#881033022, /profile/robonaren'] Here are the specific requirement i've tried [/quote] So anchor apple generic is definitely wrong. Consider this quote from Code Signing Requirement Language: For Apple’s own code, signed by Apple, you can use the short form anchor apple For code signed by Apple, including code signed using a signing certificate issued by Apple to other developers, use the form anchor apple generic If your goal is security, you don’t want to mix these up! [quote='881053022, robonaren, /thread/819553?answerId=881053022#881053022, /profile/robonaren'] Here are the specific requirement i'm using from the Authorization Plugin (xpc client) [/quote] From the client? Maybe I’ve misunderstood this, but that seems backwards. You want to apply these constraints on the server for connections coming from the client. Consider this: % csreq -r '=anchor apple and (identifier com.apple.authorizationhosthelper.arm64 or identifier com.apple.authoriz

The most common cause of this problem is that you’ve forgotten to include the NSFaceIDUsageDescription property in your Info.plist. If that’s not the cause here, please post a crash report so that I can look into that. See Posting a Crash Report for advice on how to do this. IMPORTANT I don’t maintain expertise in third-party tools, so I’m gonna help you as if you were working on Xcode. Hopefully we can get you to the point where we know for sure whether this is a Flutter thing or an Apple thing. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

[quote='819926021, craigc123, /thread/819926, /profile/craigc123'] is there any way to programmatically trigger “realtime” mode? [/quote] No. Well: Not as an API that’s documented to have that effect. It might be possible to find some API that does it as a side effect, but that would be an implementation detail and thus not something you’d want to rely on. And there’s the Wi-Fi Aware option, but you’ve ruled that out. I think you should create a prototype based on Wi-Fi Aware and see if it achieves the latency goals that you need. If it does, you can then factor that into your decision as to how to proceed here. And apropos that, you wrote: [quote='819926021, craigc123, /thread/819926, /profile/craigc123'] I am looking for a solution that works … on previous OS versions. [/quote] Note that Wi-Fi Aware requires iOS 26 and specific hardware. The main framework doc page has the list. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple

[quote='819975021, tiandt, /thread/819975, /profile/tiandt'] I’m seeing what looks like a compiler / macro-expansion / build-pipeline issue. [/quote] Agreed. I recommend that you file a bug about this. Please post your bug number, just for the record. If you use Xcode to expand the macro, what does it show? Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

If you set up a VM that’s never seen your app before and repeat this test on that VM [1], does it have the same problem. I’ve hunted app extension problems like this in the past, and it was always caused by weird issue on my main work Mac. Specifically, old school app extensions [2] rely PluginKit which relies on Launch Services, and it’s very common for Launch Services to behave weirdly on your main development Mac. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com [1] You don’t need to build on the VM. Rather, build on your main Mac and then copy the built app to the VM. [2] Modern app extension are based on ExtensionKit rather than PluginKit, but they also rely on Launch Services.

iOS has a limited set of Wi-Fi APIs. See TN3111 iOS Wi-Fi API overview for a summary of what’s available. Regarding signal strength specifically, I address that head on in iOS Network Signal Strength. In short, you’re unlikely to be able to achieve your goal here. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

It’s hard to answer questions like this without knowing more about: The platforms you’re targeting — Features like this aren’t part of the Swift language, but rather come from the platform on which your code is running. So you’ll get different answers on, say, Apple platforms vs Linux or Windows. The data itself — How big is it? Does it have some sort of complex structure? Your sharing scope — Do you just want to store it on the device? Or share it between devices owned by the same user? Or share it between users? The operations on that data — Do you write to it more than you read? Do you need to issue complex queries against it? The threat model — Are you trying to prevent accidental leaks? Or protect the data from government-sponsor attackers? Or something in between? Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

[quote='820017021, marrgd, /thread/820017, /profile/marrgd'] I would like to open … in Swift Playground on iPad [/quote] I don’t think there’s a good way to do that these days. The copy of The Swift Programming Language (TSPL) you’re working from, the one published via Apple Books, is very old. Specifically, it’s associated with Swift 5.7 and the latest version, available on the Swift site itself, is for Swift 6.3: The Swift Programming Language Note The Apple Books version hasn’t been updated because TSPL moved to a DocC production pipeline, and that isn’t able to easily render to the document format required by Apple Books. Given the age of that copy of the TSPL, it’s not a surprise that the link it references [1] no longer works. I went looking for the equivalent link on the most recent TSPL, but there isn’t one. Here’s the corresponding page, but the note box with the link is gone. I think you could reasonably argue that we should bring this back. Normally I’d suggest you file a bug requesting exactly tha

This isn’t something we can help you with here on the forums. Rather, you need to seek help via official channels. For the details, see this post. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

[quote='880681022, KayleeSC, /thread/791352?answerId=880681022#880681022, /profile/KayleeSC'] I guess they can install my TestFlight? [/quote] Yes [1]. [quote='880681022, KayleeSC, /thread/791352?answerId=880681022#880681022, /profile/KayleeSC'] For all I know these might be TestFlight quirks … but I can’t risk it. [/quote] I agree with you there. My experience is that TestFlight is a very accurate representation of what you see on the App Store, so if things are failing in TestFlight then you have good reason to be concerned. [quote='880681022, KayleeSC, /thread/791352?answerId=880681022#880681022, /profile/KayleeSC'] I just submitted this as FB22281393 [/quote] Thanks. You attached a sysdiagnose log to that bug, but there was no context for that. Some questions: Did you have the VPN (Network Extension) for iOS/iPadOS debug profile installed when you took that log? See our Bug Reporting > Profiles and Logs for more about that. What failure is the log showing? You list four cases where you had problems, bu