“eskimo”

[quote='878469022, Nickkk, /thread/817724?answerId=878469022#878469022, /profile/Nickkk'] Is the unmapped memory exception also the reason why the binary image address for my app is 0x0 - 0xffffffffffffffff? [/quote] Sadly, it’s not that simple. I created a small test app with this code: - (IBAction)testAction:(id)sender { #pragma unused(sender) NSLog(@-[AppDelegate testAction:]); void * p = (void *) 0x123456789ab; typedef void (*FunctionPtr)(void); FunctionPtr f = (FunctionPtr) p; f(); } and it produces a crash report like this: Exception Type: EXC_BAD_ACCESS (SIGSEGV) Exception Subtype: KERN_INVALID_ADDRESS at 0x00000123456789ab Exception Codes: 0x0000000000000001, 0x00000123456789ab … Thread 0 Crashed:: Dispatch queue: com.apple.main-thread 0 ??? 0x123456789ab ??? 1 xxom 0x10e301bf3 -[AppDelegate testAction:] + 83 2 AppKit 0x7ff81fa612ea -[NSApplication(NSResponder) sendAction:to:from:] + 444 … Thread 0 crashed with X86 Thread State (64-bit): … rip: 0x00000123456789ab rfl: 0x0000000000010202 cr2: 0x0000012

[quote='878552022, HiddenJester, /thread/748447?answerId=878552022#878552022, /profile/HiddenJester'] The bug number is FB22140603. [/quote] Thanks! Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

[quote='878482022, Pavel, /thread/817602?answerId=878482022#878482022, /profile/Pavel'] Our IPC implementation is based on [/quote] I find it strange that this is limited to sockaddr_un. macOS is not unusual in longer paths; I don’t know about Linux, but pretty much all the BSDs work this way. [quote='878482022, Pavel, /thread/817602?answerId=878482022#878482022, /profile/Pavel'] Are there any guarantees the path returned by this function will always fit within the buffer sockaddr_un? [/quote] I’ve never seen such a guarantee. [quote='878482022, Pavel, /thread/817602?answerId=878482022#878482022, /profile/Pavel'] are there any other locations for IPC sockets that avoid this path length restriction? [/quote] The traditional location for this stuff is /var/run. See the hier man page. But if you do use that, choose an appropriately unique file name to avoid collisions with the system and other third-party products. Typically that means using reverse DNS or embedding your company or product name in the file name.

[quote='878490022, N. Holzschuch, /thread/817449?answerId=878490022#878490022, /profile/N.+Holzschuch'] I have filed a report: FB22138371 [/quote] Thanks. decomposedStringWithCanonicalMapping should work here, but Kevin would probably advise that you go via URL and then use the withUnsafeFileSystemRepresentation(_:) method instead. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

[quote='817887021, kappie, /thread/817887, /profile/kappie'] Both produce: Warning: unable to build chain to self-signed root [/quote] Hmmm, that doesn’t sound good. Have you tried testing the cross-over cases? That is: Building on macOS 26.3 and trying to install on macOS 26.2 Building on macOS 26.2 and trying to install on macOS 26.3 Those will let you determine whether this is a build problem or an install problem. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

You can expect that most uploads will be notarised quickly. Occasionally, some uploads are held for in-depth analysis and may take longer to complete. As you notarise your apps, the system will learn how to recognise them, and you should see fewer delays. For lots of additional info about notarisation, see Notarisation Resources. Specifically, it links to a Q&A with the notary service team that’s quite instructive. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

OK. When you run this command, what do you see: % find YourApp.app -name libswiftCompatibilitySpan.dylib YourApp.app/Contents/Frameworks/libswiftCompatibilitySpan.dylib libswiftCompatibilitySpan.dylib exists to provide Span support on older systems. AFAICT it’s expected to work on Intel Macs running 13.1 or later: % vtool -show-build Test817488.app/Contents/Frameworks/libswiftCompatibilitySpan.dylib Test817488.app/Contents/Frameworks/libswiftCompatibilitySpan.dylib (architecture x86_64): Load command 10 cmd LC_BUILD_VERSION cmdsize 32 platform MACOS minos 13.1 sdk 26.2 ntools 1 tool LD version 1230.1 … And I tested it here in my office, on both 26.2 (Rosetta) and 13.6.1 (real hardware), and I didn’t have a problem. However, that was from my main app, not from a privileged helper tool, so it’s possible that there’s something specific to privileged helper tools in play here. My test code is pasted in at the end of this email. If you temporarily add this to your app, does it work on the same Intel Mac? And with

[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