“eskimo”

[quote='878184022, peterho, /thread/817501?answerId=878184022#878184022, /profile/peterho'] And a kernel extension certificate is used to sign the passthrough file system extension. [/quote] I’m not sure how you came to that conclusion. There is such a thing as a KEXT-enabled code-signing identity [1], but that’s irrelevant to this discussion. [quote='878184022, peterho, /thread/817501?answerId=878184022#878184022, /profile/peterho'] Does it need to be signed? [/quote] Yes. FSKit modules must be signed with the com.apple.developer.fskit.fsmodule entitlement. That’s a restricted entitlement, which means it must be authorised by a provisioning profile [2] [3]. To create that profile, you’ll need to be a member of a paid team. Based on our records it looks like you are a member of a paid team. Given that, you should be able to get this working as follows: Sign into with your Apple Account in Xcode > Apple Accounts. In the sample code project, for each target, go to the Signing & Capabilities editor and se

[quote='878226022, danseals, /thread/807112?answerId=878226022#878226022, /profile/danseals'] Filed FB22119525 with detailed unified log captures and a minimal reproducer. [/quote] Thanks for that, and for the detailed analysis. I had a look at your bug, and the earlier FB20987979, and they’ll both likely end up duplicated to a bug filed by another developer, FB21639147. However, I’ve updated that ‘lead’ bug to highlight the analysis in your bug. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

Thanks for that info. Based on that, I created a small test project to exercise my normalisation theory: Using Xcode 26.3 on macOS 26.2, I created a new project. I added LSSupportsOpeningDocumentsInPlace and UIFileSharingEnabled to its Info.plist [1]. I wired up a button to my test code, which I’ve pasted in at the end of this reply. I ran the app on an iOS 26.2 device. I tapped my test button. It was able to create the files. I switched to the Files app. And navigated to On My iPhone > My App Name. I tapped test, then test dec (naïve), then test pre (naïve). The first two worked; the last one failed as you described. The difference between these file names is that the test dec (naïve) uses a decomposed ï (NFD) whereas test pre (naïve) uses a precomposed one (NFC). Clearly, that’s causing problems for Quick Look in the Files app and elsewhere. So, there are two things for you to do here: Please file a bug against iOS about this. It should be able to handle both normal forms equivalently. Once you’re done,

[quote='878218022, rbmanian75, /thread/815676?answerId=878218022#878218022, /profile/rbmanian75'] It seems to be that the bug is fixed in Tahoe 26.4 beta 3 release. [/quote] Yay! Best of luck with your next round of review. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

[quote='878362022, Pushpak-Ambadkar123, /thread/816877?answerId=878362022#878362022, /profile/Pushpak-Ambadkar123'] it means I cannot distribute content filter solution on normal devices via App Store? [/quote] Yes. Well, it does depends on what you by “normal devices”. The Screen Time exception has no constraints on the device itself, but it does have constraints on the device’s user. Also note that this applies to all distribution channels, that is, App Store, TestFlight, Ad Hoc, and In-House (Enterprise). THat last one usually isn’t a big concern because the device is either supervised, or the device manager can configure your filter in per-app mode. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

do I need to create a new app in App Store Connect for each extension for a new Apple App ID? Or can I just use the main app's Apple App ID? These questions suggest you’ve misunderstood what these terms mean. I have a lot more details in Code Signing Identifiers Explained, but just to summarise here: Your main app has an App ID. And does each of its embedded app extensions. Each App ID ends with a Bundle ID. You main app has an Apple ID. But your extensions don’t. The form has App Apple ID and Bundle ID fields. You use the same Apple ID for each submission and vary the bundle ID for your app and each relevant app extension. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

For those reading along at home, I helped one of ADietz’s colleagues with this issue a few years back, so I have some inside knowledge. For example, I know that they filed a bug about this back then (FB12846267). I just checked on it, and there’s nothing helpful to share on that front. [quote='817792021, ADietz, /thread/817792, /profile/ADietz'] It’s clever and kludgey. [/quote] Yeah, and unfortunately it has come unstuck. That’s why I was hoping that we’d provide a real fix for this issue, but that hasn’t happened )-: I’d like to confirm that this is tied to the OS version rather than the Xcode version. If you use Xcode 26.3 to run this test on iOS 26.2 and 26.3, it works on 26.2 but fails on 26.3. Right? Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

What platform are you on? Oh, and are you using QUIC via HTTP/3? Or explicitly? Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

Consider this: Exception Type: EXC_BAD_ACCESS (SIGBUS) Exception Subtype: KERN_MEMORY_ERROR at 0x000000010844eb40 and this: Thread 0 crashed with X86 Thread State (64-bit): … rip: 0x000000010844eb40 … (In Intel, RIP is the PC register.) Your program has crashed to an unmapped memory exception and the crashing address is the PC. That is, the program has jumped to a bad address. That’s why you get this: Thread 0 Crashed:: Dispatch queue: com.apple.main-thread 0 ??? 0x10844eb40 ??? because there is no code mapped at that location. Notably, let’s look at more of that backtrace: Thread 0 Crashed:: Dispatch queue: com.apple.main-thread 0 ??? 0x10844eb40 ??? 1 CoreFoundation 0x7ff80f155518 __CFNOTIFICATIONCENTER_IS_CALLING_OUT_TO_AN_OBSERVER__ + 137 2 CoreFoundation 0x7ff80f1b864e ___CFXRegistrationPost_block_invoke + 88 3 CoreFoundation 0x7ff80f1b85a2 _CFXRegistrationPost + 515 4 CoreFoundation 0x7ff80f134dd6 _CFXNotificationPost + 763 5 Foundation 0x7ff810e22752 -[NSNotificationCenter postNotificationName:object:u

That page seems pretty clear to me: If your certificate expires, users can still install packages that were signed with this certificate as long as the package includes a trusted timestamp. However, I encourage you to test this for yourself: Make sure your package has a notarisation ticket stapled to it. Set up a VM. Download your package to it in a way that sets quarantine. Disable networking on the VM. (This is why stapling the ticket is important.) Use System Settings to change the time to well after your package’s expiry date. Try installing it. I expect to work, but I’d love to hear your experience either way. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

[quote='817831021, nikhil2701, /thread/817831, /profile/nikhil2701'] does the browser and advertiser browse and listen on all available interface types? [/quote] Yes. At least by default. If you don’t want that behaviour, you can limit it to a specific interface type or a specific interface. The exact mechanism you use depends on which Network framework API you’re using. You mentioned the run(_:) method which suggests you’re using the shiny new one. In that case, the droids you’re looking for are listed here (search that page for interface). Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

Your questions are quite hard to read. See Quinn’s Top Ten DevForums Tips for advice on how to improve this going forward. Also, you asked questions about four very different technologies: User defaults, Core Data, the file system, and widgets. I have a good handle on the first and the third. I can offer some general advice about the second but, if you want more then you should start a follow-up thread in App & System Services > iCloud & Data with the Core Data tag. Similarly for the fourth, but with the App & System Services > Widgets & Live Activities subtopic. With that out of the way, let’s look at your questions. User defaults has a last-write-wins synchronisation policy, with the caveat that the definition of “last” is last change to hit the daemon that manages this stuff. The answers to your question fall out of that policy: [quote='817725021, gabrielsoria, /thread/817725, /profile/gabrielsoria'] If multiple processes (app + multiple widget instances) read and write the same share

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

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

[quote='878114022, Pushpak-Ambadkar123, /thread/816877?answerId=878114022#878114022, /profile/Pushpak-Ambadkar123'] But as I uploaded the app to test flight then I do not see any setting related to content filtering in the Settings App [/quote] Right. You’re bumping into distribution restrictions that are not related to entitlements. NE lets you save a content filter configuration directly when your app is development signed. This is great for testing. However, when you go to distribute your app, that no longer works. Rather, the filter must be configured via a configuration profile. Except it’s not quite as simple as that. TN3134 Network Extension provider deployment has all the details. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com