file uri scheme

Hi @iOS-LI, Please file a feedback at https://feedbackassitant.apple.com and post the number back here. You should expect the first time you connect to any device to take a bit of extra time to load symbols but that should only happen once. From your description it sounds like it happens quite often. A feedback will help us track down and prioritize your findings. Thank you

Hi Kevin, Thank you for the suggestions. We have conducted a test of your third proposal regarding the IOKit User Client Class Temporary Exception. Our test procedure was as follows: We started from a known-good baseline commit where our DEXT loads correctly and the/dev/diskX node appears (though it reports 0 bytes, which is a separate issue we are debugging). We made only one change: we updated our App's .entitlements file to include the temporary exception. For absolute clarity, the exact content of the .entitlements file used for this test was: com.apple.security.temporary-exception.iokit-user-client-class IOUserUserClient com.apple.security.app-sandbox com.apple.developer.system-extension.install After a full clean, build, and reboot, the IOServiceGetMatchingService(DriverKitAcxxx) call still fails at runtime, returning IO_OBJECT_NULL. This result seems to indicate that the temporary exception entitlement is not sufficient to grant our app visibility of the active IOKit service on

Hello @alexander295, It would be helpful to file a feedback for this issue at https://feedbackassitant.apple.com. Once you do, please post the number here. Thank you

Thanks for the reply, yes Radar filed with ID: FB20611108

When a Binary Data attribute is marked as “Allows External Storage”, large image files are stored as separate files on the device rather than inline in the SQLite store. That is correct. There is a threshold when the data will get stored in external files next to the SQLite database, similar to the approach that you described with URLs, but that process is managed by CoreData and transparent to your app you. How effective is this mechanism in keeping the Core Data store size small on the device? It depends on what you mean by the store. The SQLite file will be smaller, but the files are still stored on the device. Are there any recommended size thresholds or known limits for how many externally stored blobs can safely be managed this way? There is in general no limit. CoreData will decide when it's worth using an external file. If the blob you are storing is only a few bytes, it'll remain inline. If you expect to have a lot of assets, you should consider h

OK, noticed the difference in animation / no animation between the 2 OS versions. Is it a constraint due to liquid glass (would be bad news). Did you file a bug report, at least against documentation if that's on purpose ? Please note reference here.

Thank you for your reply. I see you filed a bug, you have provided some code in the bug, thanks for that, but may I ask to upload a focused project showing the issue? I’ve already attached code that reproduces the issue in the first post of this thread. Please note that the issue only occurs on iOS 26 when the device is set to Dark Mode and Reduce Transparency is enabled. I have also uploaded the Xcode project for this sample code to GitHub: https://github.com/hmuronaka/iOS26NavigationTitleSample If so, please share a link to your test project or better upload it into the FB issue I’ve also uploaded the link to the project in the FB report (FB20370553) as well. Thank you for your support

I’ve been working on this for the past two days, but in a UIKit Mac Catalyst context. I managed to get it working, though I believe this might actually be a bug in Mac Catalyst. I was about to file a report when I came across your post. Did you already submit one? The workaround I found is to assign an instance of NSToolbar to the windowScene's titlebar like this: // Inside SceneDelegate.swift #if targetEnvironment(macCatalyst) let toolbar = NSToolbar() toolbar.displayMode = .iconOnly // reduces toolbar height self.window?.windowScene?.titlebar?.toolbar = toolbar #endif This setup gives you the unified sidebar and toolbar, but there’s still quite a bit of empty space at the top, even with displayMode set to .iconOnly. Since I didn’t actually need a toolbar in my case, I fixed it by applying a negative top safe area inset. That gave me the look I wanted: let splitViewController = UISplitViewController(style: .doubleColumn) let sidebarNavigationController = KNavigationController(rootViewController: Sid