smb big sur

@DTS Engineer Updated to RC and sadly, no changes on the big screensaver bugs. FB19204084 is by far the worst. Our workaround for it is imperfect and I had reports from users where in some circumstances, something gets messed up and after that macOS will just refuse to try to launch the 3rd party screensaver (giving users a black screen). Only fix in those scenarios is to restart macOS, which is the worse thing I can tell a mac user to do.

@gravity_gunner I’ve run into exactly the same issue when trying to list the contents of a folder selected through the document picker on an SMB share. I noticed you had mentioned filing a bug report about it, but unfortunately the links you shared don’t open for me, so I can’t check the status. Have there been any updates on this problem, or a known workaround?

Here is a simple view to demonstrate the issue struct ContentView: View { @State private var isPresented = false var body: some View { VStack { Button(Test) { isPresented = true } } .alert(Test, isPresented: $isPresented, actions: { Button(Delete All, role: .destructive) {} }, message: { Text(Are You Sure?) }) .padding() } } Which results in The destructive button is almost unreadable. WCAG score is 1.4, far below the minimum recommended 4.5. I found this post on SO going back to Big Sur, but not on this forum. Any known workarounds (except for building my own dialogs, which I am trying to avoid)? Using confirmationDialog instead of alert does not make a difference.

Seeing the same issue on beta 9. This is a big blocker for us.

[quote='856714022, pnelson, /thread/798550?answerId=856714022#856714022, /profile/pnelson'] I think this is just how macOS 15 and 26 work. [/quote] Ah, cool. I thought we’d broken something in macOS 26 (which wouldn’t come as a big surprise). [quote='856714022, pnelson, /thread/798550?answerId=856714022#856714022, /profile/pnelson'] Not sure why its UI stays up. [/quote] Yeah, that’s just weird, and I do think it’s worth you filing a bug about it. Please post your bug number, just for the record. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

Bug number: FB20072274 Title: (SMB Disconnect Causes macOS Disk I/O Call open () to Hang for 10 Minutes). I don't think the system will prevent you from reading or writing to a file that's been opened with O_EVENTONLY (assuming you pass in the necessary option). The main risk is exactly what you'd expect, namely that it won't prevent unmount, which could risk data loss. I tried that. The I/O does happen even with the O_EVENTONLY flag, but it still doesn't solve the timeout problem. I think that's the only option if you're specifically using the pattern of opening the file handle and performing I/O to it over time. In addition to reading whole file, I have a use case to read stream of data and not the entire file at once.

First off, as a quick confirmation, do you see this behavior when you’re using another Mac as the SMB server? I don't think you will, but that's worth confirming. Even with a different Mac running as a server, a 10 min timeout was observed. OK. Please file a bug on this and post the bug number back here. I think passing O_EVTONLY into open would work; however, I'm not sure that's really usable for I/O. O_EVENTONLY is only used for watching files like file modification, file renamed, deleted, etc. It can't be used in this context. I don't think the system will prevent you from reading or writing to a file that's been opened with O_EVENTONLY (assuming you pass in the necessary option). The main risk is exactly what you'd expect, namely that it won't prevent unmount, which could risk data loss. Note that the other option here would also be to pass in O_NONBLOCK and shift to non-blocking I/O. I'm currently using blocking I/O. Shifting to non-blocking I/O is the only way for faster timeouts? I think that'

I'm now lamenting ever supporting the iPad. It seems that device is just not playing nice. In SwiftUI you're supposed to be able to use .windowResizability(.contentSize). On macOS, I use that along with modifying my main view with .frame(idealWidth: 1024, idealHeight: 768) and this forces the window to have a content area of that size. tvOS is a non-issue since you're always dealing with 1920 pt x 1080 pt screens. iPhone also a non-issue at least for my games. But with iPad and iOS 26, even if attempting something similar as for macOS, you really don't have ultimate control. I was able to at least set a min of 360 and max of around 500 for the iPad window. But attempting say 720 x 720 will fail since a user and/or system can resize the window. And even when using Canvas, content will now be offscreen. Example (see attached). The actual window height is around 560 pt. So querying the size parameter to Canvas seems to be useless if wanted to use to drive how big to render things. Apple made a huge mist

First off, as a quick confirmation, do you see this behavior when you’re using another Mac as the SMB server? I don't think you will, but that's worth confirming. Even with a different Mac running as a server, 10 min timeout was observed. I think passing O_EVTONLY into open would work; however, I'm not sure that's really usable for I/O. O_EVENTONLY is only used for watching files like file modification, file renamed, deleted etc. It can't be used in this context. Note that the other option here would also be to pass in O_NONBLOCK and shift to non-blocking I/O. I'm currently using blocking I/O. Shifting to non-blocking I/O is the only way for faster timeouts?

Following the topic of intercepting file access events: could you suggest other technologies that are better suited to achieve this goal? So, I think the big question here is what are you actually trying to do“? The core problem here is that: Read I/O is REALLY frequent, so the system doesn't want to do anything that would make it slower/more complicated. Memory mapping makes the idea of tracking reads somewhat... questionable. As the most extreme example of this, take the file that's the backing libsystem.dylib. EVERY (yes, EVERY) process in the system has mapped it into memory and is accessing it very frequently. Tying any I/O activity on that file to any specific process isn't really possible or meaningful. Even if you could track actual I/O activity (meaning, read from disks) and tie it to a particular process, all that would tell you is which process happened to ask for a page I didn't have. It wouldn't tell you anything about the other X processes that accessed the data directly from VM without

First off, as a quick confirmation, do you see this behavior when you’re using another Mac as the SMB server? I don't think you will, but that's worth confirming. Is there any other way to set the timeout for obtaining these durable handles for macOS? Just to be clear, I'm guessing that the durable handle timeout is what's involved here, but I don't know for sure. However, assuming this is a non-Mac SMB server, then I would start by looking at the configuration the server presents to the Mac. Or is there a way to obtain a non-durable handle? I think passing O_EVTONLY into open would work; however, I'm not sure that's really usable for I/O. Note that the other option here would also be to pass in O_NONBLOCK and shift to non-blocking I/O. __ Kevin Elliott DTS Engineer, CoreOS/Hardware

Nice to know that the original issue goes away in the latest Beta. Regarding the crash triggered by the access to Item.children, if you can provide a runnable code snippet to demo the issue, I'll take another look. You have mentioned a few classes with inheritance, and so I think it is probably worth mentioning that over-using inheritance may impact your app's performance negatively. Concretely, with today's default store (DefaultStore), all the types in an inheritance hierarchy are persisted with one single table in SQLite. If your inheritance hierarchy has many classes, the table (columns and data) can be quite big, which can slow down the performance of fetching and inserting data. That being said, when adopting SwiftData inheritance, you might examine if that is a right use case. This WWDC25 session(starting from around 4:25) covers this topic a bit. You can take a look, if haven't yet. Best, —— Ziqiao Chen  Worldwide Developer Relations.