Search results for

smb big sur

11,802 results found

Post

Replies

Boosts

Views

Activity

Reply to Huge timeout values from a failed DiskIO call
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.
Topic: App & System Services SubTopic: Core OS Tags:
Sep ’25
Reply to Huge timeout values from a failed DiskIO call
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'
Topic: App & System Services SubTopic: Core OS Tags:
Sep ’25
Sheet-like presentation on the side on iPad
Is there a way to get a sheet on the side over an interactive view with a proper glass background on iPad? Ideally, including being able to drag the sheet between medium/large-height sizes (like a sheet with presentationDetents on iPhone), similar to the Maps app: I tried the NavigationSplitView like in the NavigationCookbook example. This is somewhat like it, but it's too narrow (sidebar-like) and doesn't get the full navigation bar: I also played around with .sheet and .presentationDetents and the related modifiers, thinking I could make the sheet appear to the side; but no luck here. It seems to have all the correct behaviors, but it's always presented form-like in the center: Example code for the sheet: import SwiftUI import MapKit struct ContentView: View { var body: some View { Map() .sheet(isPresented: .constant(true)) { NavigationStack { VStack { Text(Hello) NavigationLink(Show Foo) { Text(Foo) .navigationTitle(Foo) .containerBackground(Color.clear, for: .navigation) } } } .presentationDetents([.mediu
Topic: UI Frameworks SubTopic: SwiftUI
3
0
299
Sep ’25
Reply to UIRequiresFullScreen Deprecation
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
Topic: UI Frameworks SubTopic: UIKit Tags:
Sep ’25
Reply to Huge timeout values from a failed DiskIO call
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?
Topic: App & System Services SubTopic: Core OS Tags:
Sep ’25
Reply to Capturing file read events in Endpoint Security client
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
Topic: App & System Services SubTopic: Core OS Tags:
Aug ’25
AppIntent, StartWorkoutIntent, and Siri
I'm a bit confused as to what we're supposed to be doing to support starting a workout using Siri in iOS/watchOS 26. On one hand, I see a big push to move towards App Intents and shortcuts rather than SiriKit. On the other hand, I see that some of the things I would expect to work with App Intents well... don't work. BUT - I'm also not sure it isn't just developer error on my part. Here are some assertions that I'm hoping someone more skilled and knowledgable can correct me on: Currently the StartWorkoutIntent only serves the Action button on the Watch Ultra. It cannot be used to register Shortcuts, nor does Siri respond to it. I can use objects inherited from AppIntent to create shortcuts, but this requires an additional permission to run a shortcut if a user starts a workout with Siri. AppIntent shortcuts requires the user to say Start a workout in - if the user leaves out the in part, Siri will not prompt the user to select my app. If I want to allow the user to simply say Start a Workout and ha
1
0
124
Aug ’25
Reply to Huge timeout values from a failed DiskIO call
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
Topic: App & System Services SubTopic: Core OS Tags:
Aug ’25
Different toolbar item placement for iPhone vs iPad
On iPhone, I would like to have a more button at the top right of the navigation bar, a search field in the bottom toolbar, and a plus button to the right of the search field. I've achieved this via the code below. But on iPad they should be in the navigation bar at the trailing edge from left to right: plus, more, search field. Just like the Shortcuts app, if there's not enough horizontal space, the search field should collapse into a button, and with even smaller space the search bar should become full-width under the navigation bar. Right now on iPad the search bar is full width under the navigation bar, more at top right, plus at bottom middle, no matter how big the window is. How can I achieve that? Any way to specify them for the system to more automatically do the right thing, or would I need to check specifically for iPhone vs iPad UIDevice to change the code? struct ContentView: View { @State private var searchText = var body: some View { NavigationStack { VStack { Text(Hello, world!) } .na
3
0
112
Aug ’25
Reply to SwiftData Inheritance Query Specialized Model
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.
Aug ’25
Icon Composer's minimum window size is too big for smaller MacBook video modes
I've filed a FB already through standard channels (FB ID: FB19032008) but I'll post it here in case it may get some attention from others experiencing similar issues. On macOS 26 Beta 5 and Xcode 26 Beta 5 (and earlier revisions afaik) Icon Composer specifies a minimum window size that greatly exceeds the bounds of the 1280x800/832pt video modes available on 13in MacBooks, and which also is too large for the default 1440x900 video mode on non-notched 13in MacBook Air/Pro models as this causes a default-size 64pt dock to occlude the window. I've attached screenshots depicting this behaviour in the two above described cases. Best solution seems like reducing min window size to something that will fit reasonably in a 1280x800pt viewport including the dock and menu bar (e.g. 1000x600 or something).
2
0
94
Aug ’25
Reply to HTTPS Connection Issues Following iOS 26 Beta 6 Update
First up, I want to pass along a big “thank you” from the folks who manage our CT infrastructure. Your bug let them quickly identify the root cause of this issue, which is a configuration problem at our end O-: The timing of this is a bit tricky. I can’t predict the future, obviously, but there may be a short window (weeks not months) between the release of iOS 26 and the release of this fix where your customers are affected by the issue. If that’s likely to cause you significant grief, you’ll need a workaround. To understand the workaround I need to explain a little bit about the bug… The bug you’ve found means that iOS won’t trust certificates issued by your CA in the 8 hours between 2026-07-01 00:00:00 GMT and 2026-07-01 08:00:00 GMT. And lo! your server’s certificate just happens to expire in that range: % openssl x509 -inform der -in leaf.cer -text … Validity Not Before: May 30 06:03:02 2025 GMT Not After : Jul 1 06:03:01 2026 GMT … That’s just bad luck )-: The workaround is to ask your CA to is
Topic: Privacy & Security SubTopic: General Tags:
Aug ’25
VNOP_MONITOR+vnode_notify() operation details
After perusing the sources of Apple's SMB and NFS clients' implementation of VNOP_MONITOR, my understanding of how VNOP_MONITOR+vnode_notify() operate is as follows: A user-space process advertises an interest in monitoring a file or directory via kqueue(2)/kevent(2). VFS calls the filesystem's implementation of VNOP_MONITOR. VNOP_MONITOR forwards the commencing or terminating of monitoring events request to the filesystem server. Network filesystem client nodes call vnode_notify() to notify the underlying VFS of a filesystem event, e.g. file/directory creation/removal, etc. What I'm still vague about is how does the server communicate back to client nodes that an event of interest has occurred? I'd appreciate being enlightened on the operation of `VNOP_MONITOR+vnode_notify()' in a network filesystem setting.
1
0
99
Aug ’25
Reply to "Assertion failed: (false) function _onqueue_rdar53306264_addWaiter file TubeManager.cpp line 1042" Crash
It’s better to reply as a reply, rather than in the comments; see Quinn’s Top Ten DevForums Tips for this and other titbits. What modifications can we make to prevent this issue from reoccurring? Honestly, I’ve no idea. Earlier I wrote: [quote='854100022, DTS Engineer, /thread/796647?answerId=854100022#854100022'] Historically this crash has been triggered by a range of concurrency problems within CFNetwork [/quote] The nature of concurrency bugs is that they can come and go based on hard to understand criteria. Consider this thought experiment: CFNetwork has a concurrency bug that causes this crash. The bug is highly dependent on network timing. You see a huge uptick of crash reports in your app during late November and late December. This might be nothing to do with your code, or your infrastructure. Rather, a big chunk of your users are travelling in late November and late December due to the US Thanksgiving and Christmas holidays. While travelling they’re on WWAN rather than Wi-Fi, which disrupts
Aug ’25