smb big sur

Can you share the full build report? To collect it: Choose View > Navigators > Reports. Select the report associated with your app’s build in the navigator. Using the filter bar at the top of the build report, select the filter buttons for All and All Messages. Click Export in the filter bar to save the detailed build report. Depending on the size of your app, the report may be too big to attach to a post here in the forums. If that's the case, providing a URL where we can see a copy would also be fine. — Ed Ford,  DTS Engineer

First off, on the bug front, these issues should be resolved in macOS 26.1, which we released to beta last week (25B5042k). Please test on that beta, and if you find any problem, file a new bug and post the bug number back here. Are we actually talking about the same bug though? Yes, I believe so. Coe 256 seems to be an issue only for the root drive of exFAT. The issue here was actually introduced as part of a security fix (r.151029665) and it affected exFAT, some SMB mounts, and the / AFPS mount. In both cases, the high-level issue is the same (basically, stat wasn't returning what it expected), but the underlying cause was different. In the case of exFAT, the file system is basically “too simple, so it's basically returning a synthetic (invented) value because the file system doesn't really have an alternative it can provide. In the case of APFS, the issue is that the way that data and system volumes are merged means that you can get different values for the same object, depending on exactly how yo

the launchHandler is there to tell you the task has started and provide you the BGTask object you use to manage that work. No task type actually requires the work to occur inside the task. Thanks Kevin! So I need to think about this a little differently then. Instead of performing the work once you get a BGContinuedProcessingTask, just begin performing the work (the exact same way you do in iOS 18), if a BGContinuedProcessingTask starts persist it and update it as the work completes, and reset state when the work finishes or gets canceled. Basically, something like this: 1-6 I put together code to demonstrate this approach. Did I understand correctly, this should be all good with this simple counting demo? class ViewController: UIViewController { private let taskIdentifier = (Bundle.main.bundleIdentifier!).count_task private let countToNumber: Int64 = 100 private var currentBackgroundContinuedProcessingTask: BGContinuedProcessingTask? private var shouldStopCounting = false @IBOutlet var progressLabel: UILabel

When will we configure Hibernate 25? Is it valid for M series MacBooks? Is Hibernate 25 called deep sleep mode? So, let me start by quoting the man page for pmset: hibernatemode = 3 by default on portables. The system will store a copy of memory to persistent storage (the disk), and will power memory during sleep. The system will wake from memory, unless a power loss forces it to restore from hibernate image. ... hibernatemode = 25 is only settable via pmset. The system will store a copy of memory to persistent storage (the disk), and will remove power to memory. The system will restore from disk image. If you want hibernation - slower sleeps, slower wakes, and better battery life, you should use this setting. The thing to understand here is that the difference between those two ISN'T about how either mode “prepares for sleep. Both of them do exactly the same thing— that is, they flush all memory to disk, ensuring that power loss won't lose any data. The difference is that having done that flush, Hibernate 25

The problem ended up being solved by calling: sfltool resetbtm in Terminal, followed of course by a restart on each affected machine. Interesting that it occurred across several machines all running macOS 13 and 14 right when we updated to Xcode 26. It does seem like the system will occasionally get upset with big changes to the app through the development cycle.

Please check the crash files as attached. So, this is a great example of why I always ask for a crash log, as the problem here doesn't actually have anything to do with the audio system itself. The problem is that your app is stuck in an infinite loop. For future reference, the most direct proof of this is that the number of stack frames on the crashing thread is very high (860) and that the base of the stack ISN'T a valid entry point for a thread. For the main thread, this would be main, but other threads would be thread_start or a similar entry point in libpthread. Crash collection system artificially limits the number of frames it collects (otherwise you'd potentially have 1000s+ of lines of repeating frames), so you aren't actually getting the true bottom of the stack. 858 <...> closure #1 in DeviceManager.init() + 80 859 <...> partial apply for closure #1 in DeviceManager.init() + 24 (/:0) 860 <...> closure #1 in NSNotificationCenter.addObserver(forType:object:queue:using:) + 232 (GaiaN

I have also just seen the height is way too big issue on Tahoe 26.0. I had recreated all my icons as all-vector PDFs with a large size and the toolbar grew to a huge depth (I presume the same size as the icon's files). Changing the page size of the PDFs to 32 (expressed in pixels in Affinity Designer) calmed this down but the icons are scaled to different sizes (mostly too small) if the sizing is left as Automatic. I had just changed them all from explicit sizes of 24-32 pix and it was all perfect on Sequoia/15.6. I though explicit sizes were deprecated so I had changed them as derisking action for Tahoe :-( Has anyone found any up-to-date documentation on NSToolbar? The only docs I have are very old.

Heyo Greg! That fixed it! Something has changed though, because that code block hasn't changed since 2023 according to Git...but it was importing AVFoundation. So I guess now you have to use the Kit, not the Foundation! Cool with me as long as I know now! Big thanks Greg I really appreciate it.

This is the third time you’ve posted pretty much the same question [1]. Folks have tried to help you on your other threads, but I wanna take a step back and look at the big picture here. It’s unlikely that other folks on the forums have access to the specific book you’re working from. Given that, quoting an exercise from that book doesn’t help because other folks can’t look that up. You have a couple of choices: Switch to a different tutorial, one that’s publicly available. This is what Claud31 suggested here. Provide more context, so that folks can understand your question without having access to that specific tutorial. This is what darkpaw suggested here. I’m going to add a third option: Look for a support channel for your specific tutorial. For example, it’s not uncommon for book authors to set up a Discord channel to encourage conversation between folks who are using the book as a tutorial. Good luck! Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskim