smb big sur

The problem still persists with iOS 26.2 beta 3. This is becoming a big problem that has not been resolved for a long time and is affecting a large number of users on my application. It forces us to consider custom solutions for this problem in the future.

Users of my different apps started reporting an issue that could be related to the ones discussed in this other post: paths on an external volume, such as one mounted by NTFS for Mac, or a path on a Synology volume, are converted to / (Macintosh HD) after going through laundry (creating the security-scoped bookmark, resolving the URL from it, and using this new URL instead of the one returned by the open pane). Clarifying slightly, the bug happens with file systems which don't provide native persistent identifiers, so this does not affect APFS or HFS+. The behavior on smb volumes will depend on the specifics of the smb server. I created FB21002290. I believe this issue has been fixed in the most recent seed, macOS 26.2 beta 3 (25C5048a). __ Kevin Elliott DTS Engineer, CoreOS/Hardware

@DTS Engineer - Is there a bug report for this / do you know if its being addressed soon (MacOS 26.2) ?? Its a big productivity blocker for me :-(

So I had to pepper a few of these around: // NSButton image scaling changed in 26.1 with certain SF symbols? if (@available(macOS 26.1, *)) { // looks better on 26.1 button.imageScaling = NSImageScaleProportionallyDown; } else { // looks better on 26.0. button.imageScaling = NSImageScaleProportionallyUpOrDown; } And one of these for a symbol image... NSImageSymbolScale symbolScale; if (@available(macOS 26.1, *)) { // large is too big on on 26.1 so let's go down to medium symbolScale = NSImageSymbolScaleMedium; } else { // need large on 26.0 symbolScale = NSImageSymbolScaleLarge; } NSImage *symbol = // make image with symbolScale and use it in a NSButton

[quote='807134021, captadoh, /thread/807134, /profile/captadoh'] This guy stands out to me Networking failed: -11992 [/quote] I’m not sure what’s going on with the big picture here, but you can find an explanation of that error in this post. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

Absolutely, although it is not much of a test project: https://github.com/martonfarago/documentPickerTest Using this, I can pick a folder on an SMB share just fine under 18.7 but cannot under 26.1. I've downloaded your sample project and, with two exceptions, I'm not able to replicate what you're describing. The two exceptions I found were: When you initially navigate into a server, the list of shared returned can't be opened. This happens because that list is artificially generated and doesn't actually exist in the file system. I'm not sure what the exact criteria we're applying is, but I think what's happening is that we're only enabling Open in directories you can write to. I'm not sure if #2 is new behavior or not, as I don't have an iOS 18 device handy to test it with, nor have I been able to find a specific bug/change that would have changed the behavior. So, a few points here: Is the share you're testing with coming from macOS? If it's not macOS, what is it? Note that one of the issues here is

[quote='865440022, Engineer, /thread/806702?answerId=865440022#865440022'] However, in your example, since those environment variables wouldn't likely update very frequently (they're not really in a hot path) the cost of putting them in the environment is probably negligible. [/quote] Indeed, and now that I know that every write to any environment variable is not as egregious as I initially thought, then I'm a bit less concerned about this issue. That said, I do want to revisit this a bit. In your demo, you were worried about writes in the hot path during a critical operation like scrolling. What I'm finding on macOS isn't that I have hot paths but rather I have a lot of views being updated because of a very small change. These might be infrequent, the cost is high and noticeable. An example would be keeping track of a selected objects on a canvas such that a bunch of inspector panels and other panes need to update their state based as the selection changes. Selection changes are relatively infrequent (compar

Is our understanding correct? Have other developers of high-performance storage drivers or peripherals also observed a similar performance ceiling for external storage on Apple Silicon Macs, when compared to high-end Intel Macs? SO, I have two response to this: If you haven't already, please file a bug on this and post the bug number back here. I'd like to discuss this with the engineering team and it's helpful to have a external bug to anchor that conversation. If you're using the original UserProcessParallelTask architecture, then switching to UserProcessBundledParallelTasks will probably provide significant performance benefits. Finally, one other comment here: Since the KEXT and external hardware are identical in both tests, we believe this performance difference is not a bug but a fundamental platform architecture distinction. One thing I'm not sure about here is how the configuration from UserReportHBAConstraints and UserGetDMASpecification configuration described here effect overall performance. Concep

Unfortunately, users of my different apps also started reporting another issue that could be related: paths on an external volume, such as one mounted by NTFS for Mac, or a path on a Synology volume, are converted to / (Macintosh HD) after going through laundry. Could someone at Apple confirm whether this is also a known issue? I'm not sure. There was an issue (fixed in macOS 26.1*) that prevented SMB volumes from remounting during bookmark resolution, however: I believe resolution simply failed; it didn't lead back to /. The issue effected remounting the volume, not the full resolution. *Note that the bookmark will need to be recreated. That also wouldn't explain NTFS for Mac, as that's a local volume mount which presents very different issues. __ Kevin Elliott DTS Engineer, CoreOS/Hardware

Absolutely, although it is not much of a test project: https://github.com/martonfarago/documentPickerTest Using this I can pick a folder on an SMB share just fine under 18.7 but can not under 26.1. Thanks for the help.

Yeah, it will be a really big surprise if using .glassEffect(_:in:) triggers a crash in the latest iOS. So as @darkpaw said, providing more details about your issue will help clarify. Regarding #available, you can definitely use it to check the OS version. The following code behaves differently on iOS 26.1 and later: if #available(iOS 26.1, *) { print(iOS 26.1 and later) } else { print(Before iOS 26.1) } Best, —— Ziqiao Chen  Worldwide Developer Relations.

@DTS Engineer It concerns SMB shares of NTFS volumes hosted on Windows PCs. The starting URL could for example be file:///Volumes/Videos/, but the resolved URL is file:///. This happens immediately after resolving the bookmark data, even if that data has been created in the same code context. To be clear, only in macOS 26.1. In older macOS versions the starting URL and resolved URL are identical. FB20917638 contains instructions and a sample project to reproduce the issue.