“Xcode”

Resolved. Of course I did it to myself, but #Xcode could have warned me. Package dependencies either direct or indirect in my project are A <- B <- C <- D <- E <- App where x <- y means x is a dependency of y. I was writing tests for package C. To make test setup easier I called functions in package D and E, adding D and E as dependencies to C. Oops. Don't do that. Apparently adding C and C_C is how Xcode handles circular dependencies.

The find command returns nothing when the app is built with XCode 26.3 or XCode 26.2. Is there a build setting that ensures that libswiftCompatibilitySpan.dylib gets included? I've tried copying it in build phases, but that crashes the main app. I do have Always Embed Swift Standard Libraries set to yes in the main app. Including the sample code in the helper (NB: the helper tool doesn't have an app delegate - it's a command line tool) also doesn't resolve the crash. If it's helpful, here's the relevant piece of the crash log from the helper: Termination Reason: Namespace DYLD, Code 1 Library missing Library not loaded: @rpath/libswiftCompatibilitySpan.dylib Referenced from: <91AD8720-25FD-3ABB-B10A-6A7630E7BA48> /Users/USER/Library/Developer/Xcode/DerivedData/MyApp-hapnwyzmnoqmoybwzlybjoupeflc/Build/Products/Debug/MyApp.app/Contents/MacOS/com.micromat.TTDaemon Reason: tried: '/usr/lib/swift/libswiftCompatibilitySpan.dylib' (no such file, not in dyld cache), '/System/Volumes/P

Thanks. It works after developer account is added into Xcode project

Hello - Please review this documentation with details for Sandbox testing in a TestFlight build of your app: https://developer.apple.com/documentation/storekit/testing-in-app-purchases-with-sandbox#Sign-in-to-your-Sandbox-Apple-Account-for-a-TestFlight-app Related documentation to review: Overview of testing in Sandbox Enabling developer mode on a device Testing at all stages of development with Xcode and the sandbox Testing subscriptions and in-app purchases in TestFlight Please let us know if you have any additional questions or need further assistance. Thank you.

Xcode 26.2 + iPadOS 26.3.1 = broken Xcode 26.3 + iPados 26.2.1 = works Xcode 26.3 + iPadOS 26.3 = broken Xcode 26.3 + iPadOS 26.3.1 = broken

The combinations we've confirmed are: Xcode 16.x + iPadOS 18.x.x = works Xcode 26.2 + iPadOS 18.x.x = works. Xcode 26.2 + iPadOS 26.2.1 = works. Xcode 26.2 + iPadOS 26.3 = broken. Have we tried Xcode 26.3? No - honestly I was neck deep in troubleshooting when Xcode 26.3 came out last week. And we're a med device company so we typically don't rush to update tools because we need to maintain specific development environments. I know you're thinking what could it hurt at this point? lol. I'll test that today.

[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 edit

It seems to be QUIC explicitly. And it's not us using it but some dependency we include - and yes, I am aware of https://developer.apple.com/documentation/Xcode/verifying-the-origin-of-your-xcframeworks :)

System version: 26.2 (25C56) Xcode version: Version 26.2 (17C52) My attempt to mount to the /Volumes directory was also denied due to permissions. Providing the user with a mount point also resulted in permission denial. detailed_log.log simple log : 默认 20:12:14.201225+0800 NetAuthSysAgent Process 54430 is sandboxed and is allowed to mount a shared volume because it has the proper permissions. 默认 20:12:14.201351+0800 NetAuthSysAgent Mount URL: request C78993FC-5F67-4D47-B394-23AEE1F33FF1 from MyNavm (54430) 默认 20:12:14.237651+0800 NetAuthSysAgent GetServerInfo serverParamsDict = { NoMountAuthentication = 1; ServerDisplayName = 192.168.139.236; SupportsGuest = 0; } 默认 20:12:14.266567+0800 NetAuthSysAgent (31) /Applications/Mountain Duck.app 默认 20:12:14.267956+0800 NetAuthSysAgent (31) /Applications/Mountain Duck.app 默认 20:12:14.269373+0800 NetAuthSysAgent (31) /Applications/Mountain Duck.app 默认 20:12:14.270843+0800 NetAuthSysAgent (31) /Applications/Mountain Duck.app 默认 20:12:14.271325+0800 NetAuthSys

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’