Search results for

“smb big sur”

11,971 results found

Post

Replies

Boosts

Views

Activity

Reply to Recursively walk a directory using File Coordination
I think using Task() for I/O work like this is probably a mistake. Ah, my mistake. I should’ve clarified that this would all be running inside a single actor, so the resulting behavior should be equivalent to an NSOperationQueue with a width of 1. OK. SO, FYI, I did some very rough performance testing with the code I posted yesterday, and a queue width of 4 was ~4x faster than #1. However, the big question here is the nature of the data you're expecting to process. While we generally talk about it as I/O bound (and it technically is), I think that term can be somewhat misleading, particularly when you're talking about the devices’ local storage or other fast SSDs. The issue here is that, in practice, much of the volume’s catalog data is either already in memory or WILL be streamed into memory fairly quickly as you start iterating over the device. That means that in many cases, the real bottleneck isn't disk I/O but is actually how fast you can make syscalls into the kernel. Using multiple threads let
Topic: App & System Services SubTopic: Processes & Concurrency Tags:
Oct ’25
Weird transparency in sidebar in iPad app
I have an iPad app with a classic sidebar. It's been working fine for years. Now with iPadOS 26 the sidebar sometime gets this fake transparency that makes it really hard to quickly grok. A part of Liquid Glass seems to be to sometimes (but not always) take whatever is in the secondary area (the main big content), blur it, mirror it and then use as the background for the sidebar. This is silly and does not work at all for an app like mine. It maybe looks decent if your background is a photo or similar, but not for an app that manages data. Not all views cause the sidebar to get this ugly unreadable background. In most of the cases the sidebar keeps its normal opaque background that it has always had. See this example for how it looks when it's really bad: This is how it should look. Notice that the content of the main view is pretty similar to the case where it gets the ugly background. The difference is the segmented thing at the top, ie. a different root view. Is there some good way for me to force
Topic: UI Frameworks SubTopic: SwiftUI Tags:
4
0
293
Oct ’25
NSViewController, awakeFromNib, Tahoe and hangs
Mostly a heads up, maybe this will help other people. I had a very simple test app for MacOS, just a ViewController with an OutlineView that had two columns, and the column data was initialized in awakeFromNib of the NSViewController like this: override func awakeFromNib() { if dataArray.count == 0 { dataArray.append( Node( firstname: John, lastname: Doe ) ) dataArray.append( Node( firstname: Mary, lastname: Smith ) ) } self.content = dataArray } There's also a toolbar with a button and a search field. This worked perfectly fine on Sequoia and Xcode 16, but since I updated to Tahoe and Xcode 26, if I try to run/debug the app from Xcode it hangs and eventually crashes. If Debug Executable is enabled in the scheme the crash is in libMainThreadChecker with EXC_BAD_ACCESS, and without debug it's a crash report with Thread stack size exceeded due to excessive recursion. I found that if I moved the self.content assignment inside the if block the problems went away: override func awakeFromNib() { if dataArray.count
Topic: Developer Tools & Services SubTopic: Xcode
0
0
108
Oct ’25
Reply to Instructions for debugging recent macos kernel versions?
For now, I will just write up these steps and share here. For future reference, I've now written it up here https://jaitechwriteups.blogspot.com/2025/10/boot-custom-macos-kernel-on-macos-apple.html It's been a very long time since I've done this, but the main thing I remember is that you need to be very careful to ensure that you've exactly matched up versions so that everything is the same exact version (kernel source, KDK, developer tools, etc.). Thank you Kevin for that hint. I suspected it wouldn't be straightforward. It's still on my TODO list to experiment with that and hopefully get it to work in the coming weeks. If it does, then it will help in a big way in debugging (and reporting) some of the issues we have been running into recently.
Topic: App & System Services SubTopic: Core OS Tags:
Oct ’25
Reply to How to handle required @relationship optionals in SwiftData CloudKit?
SwiftData + CloudKit uses NSPersistentCloudKitContainer under the hood, which requires all relationships must be optional. For more information, see Creating a Core Data Model for CloudKit. The requirement exists because of the latency of the synchronization: When you create an object graph in device A, which is being synchronized to device B, the system doesn't guarantee to synchronize the whole graph all at once. As a result, it's possible that an object is synchronized but its relationship is not. This situation is expressed as the relationship being nil. By checking if the relationship is nil, the app instance running on device B can consume the object appropriately. In your case, wrapping a relationship with a computed property to return an empty array if nil makes sense to me, if the other part of your app prefers to consume an empty array. It doesn't matter if the data is big or small. Best, —— Ziqiao Chen  Worldwide Developer Relations.
Topic: App & System Services SubTopic: iCloud & Data Tags:
Oct ’25
Reply to "Build input file cannot be found" error occurs in Archive.
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
Topic: Developer Tools & Services SubTopic: Xcode Tags:
Oct ’25
Background GPU access in iOS 26 for iPhones
We build mobile apps for creators to edit their videos. Post editing the video, the creator has to export the video so that it can be uploaded to Youtube. The export is a time consuming and GPU intensive process. The creator can exit the app due to various reasons like receiving the call, putting the app in background etc. This causes the export to fail :( Keeping this limitation in mind there was an announcement from Apple that with the IOS 26 launch would start to support background GPU access. Here is the official documentation: https://developer.apple.com/documentation/BundleResources/Entitlements/com.apple.developer.background-tasks.continued-processing.gpu When we tried using this feature, we were not able to get it to work on IOS 26. We stumbled upon this ticket(https://developer.apple.com/forums/thread/797538?answerId=854825022#854825022) in the Apple Developer forum, in which possibly an Apple engineer claims it is supported ONLY for iPadOS 26. This is a very big bummer for us. 96% of the us
Topic: Media Technologies SubTopic: Video
1
0
254
Oct ’25
AsyncRenderer causes crashes in ForEach when in Swift 6 language mode
Hi! We've recently done a big migration to Swift 6 language mode in our app and are now getting reports of crashes occurring due to closures in our SwiftUI code (most often the view builder in ForEach) not running on the main queue but instead running on the queue com.apple.SwiftUI.AsyncRenderer. One example of a call stack (ScheduleListView is our view that is in Swift 6 mode): Thread 16 #0 (null) in _dispatch_assert_queue_fail () #1 (null) in dispatch_assert_queue$V2.cold.1 () #2 (null) in dispatch_assert_queue () #3 (null) in swift_task_isCurrentExecutorWithFlagsImpl(swift::SerialExecutorRef, swift::swift_task_is_current_executor_flag) () #4 (null) in closure #2 in closure #1 in closure #1 in ScheduleListView.body.getter () #5 (null) in closure #1 in ForEachState.item(at:offset:) () #6 (null) in partial apply for closure #1 in ForEachState.item(at:offset:) () #8 (null) in partial apply for closure #1 in _withObservation(do:) () .... (We have many other crashes with similar crash reports but in oth
Topic: UI Frameworks SubTopic: SwiftUI
3
0
366
Oct ’25
How to handle required @relationship optionals in SwiftData CloudKit?
Hi all, As you know, when using SwiftData Cloudkit, all relationships are required to be optional. In my app, which is a list app, I have a model class Project that contains an array of Subproject model objects. A Subproject also contains an array of another type of model class and this chain goes on and on. In this type of pattern, it becomes really taxxing to handle the optionals the correct way, i.e. unwrap them as late as possible and display an error to the user if unable to. It seems like most developers don't even bother, they just wrap the array in a computed property that returns an empty array if nil. I'm just wondering what is the recommended way by Apple to handle these optionals. I'm not really familiar with how the CloudKit backend works, but if you have a simple list app that only saves to the users private iCloud, can I just handwave the optionals like so many do? Is it only big data apps that need to worry? Or should we always strive to handle them the correct way? If that's the case
Topic: App & System Services SubTopic: iCloud & Data Tags:
3
0
199
Oct ’25
Reply to Issue when creating Bookmark with security scope on macOS 26 RC
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
Topic: App & System Services SubTopic: Core OS Tags:
Sep ’25
Reply to BGContinuedProcessingTask launchHandler invocation
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
Topic: App & System Services SubTopic: Processes & Concurrency Tags:
Sep ’25
Reply to Understanding deep sleep
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
Topic: Privacy & Security SubTopic: General Tags:
Sep ’25
Reply to macOS 26 Launch Constraints
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.
Topic: Code Signing SubTopic: General Tags:
Sep ’25
Reply to Recursively walk a directory using File Coordination
I think using Task() for I/O work like this is probably a mistake. Ah, my mistake. I should’ve clarified that this would all be running inside a single actor, so the resulting behavior should be equivalent to an NSOperationQueue with a width of 1. OK. SO, FYI, I did some very rough performance testing with the code I posted yesterday, and a queue width of 4 was ~4x faster than #1. However, the big question here is the nature of the data you're expecting to process. While we generally talk about it as I/O bound (and it technically is), I think that term can be somewhat misleading, particularly when you're talking about the devices’ local storage or other fast SSDs. The issue here is that, in practice, much of the volume’s catalog data is either already in memory or WILL be streamed into memory fairly quickly as you start iterating over the device. That means that in many cases, the real bottleneck isn't disk I/O but is actually how fast you can make syscalls into the kernel. Using multiple threads let
Topic: App & System Services SubTopic: Processes & Concurrency Tags:
Replies
Boosts
Views
Activity
Oct ’25
Weird transparency in sidebar in iPad app
I have an iPad app with a classic sidebar. It's been working fine for years. Now with iPadOS 26 the sidebar sometime gets this fake transparency that makes it really hard to quickly grok. A part of Liquid Glass seems to be to sometimes (but not always) take whatever is in the secondary area (the main big content), blur it, mirror it and then use as the background for the sidebar. This is silly and does not work at all for an app like mine. It maybe looks decent if your background is a photo or similar, but not for an app that manages data. Not all views cause the sidebar to get this ugly unreadable background. In most of the cases the sidebar keeps its normal opaque background that it has always had. See this example for how it looks when it's really bad: This is how it should look. Notice that the content of the main view is pretty similar to the case where it gets the ugly background. The difference is the segmented thing at the top, ie. a different root view. Is there some good way for me to force
Topic: UI Frameworks SubTopic: SwiftUI Tags:
Replies
4
Boosts
0
Views
293
Activity
Oct ’25
NSViewController, awakeFromNib, Tahoe and hangs
Mostly a heads up, maybe this will help other people. I had a very simple test app for MacOS, just a ViewController with an OutlineView that had two columns, and the column data was initialized in awakeFromNib of the NSViewController like this: override func awakeFromNib() { if dataArray.count == 0 { dataArray.append( Node( firstname: John, lastname: Doe ) ) dataArray.append( Node( firstname: Mary, lastname: Smith ) ) } self.content = dataArray } There's also a toolbar with a button and a search field. This worked perfectly fine on Sequoia and Xcode 16, but since I updated to Tahoe and Xcode 26, if I try to run/debug the app from Xcode it hangs and eventually crashes. If Debug Executable is enabled in the scheme the crash is in libMainThreadChecker with EXC_BAD_ACCESS, and without debug it's a crash report with Thread stack size exceeded due to excessive recursion. I found that if I moved the self.content assignment inside the if block the problems went away: override func awakeFromNib() { if dataArray.count
Topic: Developer Tools & Services SubTopic: Xcode
Replies
0
Boosts
0
Views
108
Activity
Oct ’25
Reply to Instructions for debugging recent macos kernel versions?
For now, I will just write up these steps and share here. For future reference, I've now written it up here https://jaitechwriteups.blogspot.com/2025/10/boot-custom-macos-kernel-on-macos-apple.html It's been a very long time since I've done this, but the main thing I remember is that you need to be very careful to ensure that you've exactly matched up versions so that everything is the same exact version (kernel source, KDK, developer tools, etc.). Thank you Kevin for that hint. I suspected it wouldn't be straightforward. It's still on my TODO list to experiment with that and hopefully get it to work in the coming weeks. If it does, then it will help in a big way in debugging (and reporting) some of the issues we have been running into recently.
Topic: App & System Services SubTopic: Core OS Tags:
Replies
Boosts
Views
Activity
Oct ’25
Reply to How to handle required @relationship optionals in SwiftData CloudKit?
SwiftData + CloudKit uses NSPersistentCloudKitContainer under the hood, which requires all relationships must be optional. For more information, see Creating a Core Data Model for CloudKit. The requirement exists because of the latency of the synchronization: When you create an object graph in device A, which is being synchronized to device B, the system doesn't guarantee to synchronize the whole graph all at once. As a result, it's possible that an object is synchronized but its relationship is not. This situation is expressed as the relationship being nil. By checking if the relationship is nil, the app instance running on device B can consume the object appropriately. In your case, wrapping a relationship with a computed property to return an empty array if nil makes sense to me, if the other part of your app prefers to consume an empty array. It doesn't matter if the data is big or small. Best, —— Ziqiao Chen  Worldwide Developer Relations.
Topic: App & System Services SubTopic: iCloud & Data Tags:
Replies
Boosts
Views
Activity
Oct ’25
Reply to "Build input file cannot be found" error occurs in Archive.
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
Topic: Developer Tools & Services SubTopic: Xcode Tags:
Replies
Boosts
Views
Activity
Oct ’25
Background GPU access in iOS 26 for iPhones
We build mobile apps for creators to edit their videos. Post editing the video, the creator has to export the video so that it can be uploaded to Youtube. The export is a time consuming and GPU intensive process. The creator can exit the app due to various reasons like receiving the call, putting the app in background etc. This causes the export to fail :( Keeping this limitation in mind there was an announcement from Apple that with the IOS 26 launch would start to support background GPU access. Here is the official documentation: https://developer.apple.com/documentation/BundleResources/Entitlements/com.apple.developer.background-tasks.continued-processing.gpu When we tried using this feature, we were not able to get it to work on IOS 26. We stumbled upon this ticket(https://developer.apple.com/forums/thread/797538?answerId=854825022#854825022) in the Apple Developer forum, in which possibly an Apple engineer claims it is supported ONLY for iPadOS 26. This is a very big bummer for us. 96% of the us
Topic: Media Technologies SubTopic: Video
Replies
1
Boosts
0
Views
254
Activity
Oct ’25
Calls, Contacts, Messages App cant run after installing IOS26.1beta
This is my first time installing the developer beta, and i found Calls, Contacts, Messages App keep no response for most of the time, only can run sometime after i have reboot my iphone 16 pro… I forgot to back up my phone before installing the 26.1beta, what can i do now as it is a big problem for cant receiving calls and messages most of the time…
Topic: Community SubTopic: Apple Developers
Replies
0
Boosts
0
Views
176
Activity
Oct ’25
AsyncRenderer causes crashes in ForEach when in Swift 6 language mode
Hi! We've recently done a big migration to Swift 6 language mode in our app and are now getting reports of crashes occurring due to closures in our SwiftUI code (most often the view builder in ForEach) not running on the main queue but instead running on the queue com.apple.SwiftUI.AsyncRenderer. One example of a call stack (ScheduleListView is our view that is in Swift 6 mode): Thread 16 #0 (null) in _dispatch_assert_queue_fail () #1 (null) in dispatch_assert_queue$V2.cold.1 () #2 (null) in dispatch_assert_queue () #3 (null) in swift_task_isCurrentExecutorWithFlagsImpl(swift::SerialExecutorRef, swift::swift_task_is_current_executor_flag) () #4 (null) in closure #2 in closure #1 in closure #1 in ScheduleListView.body.getter () #5 (null) in closure #1 in ForEachState.item(at:offset:) () #6 (null) in partial apply for closure #1 in ForEachState.item(at:offset:) () #8 (null) in partial apply for closure #1 in _withObservation(do:) () .... (We have many other crashes with similar crash reports but in oth
Topic: UI Frameworks SubTopic: SwiftUI
Replies
3
Boosts
0
Views
366
Activity
Oct ’25
How to handle required @relationship optionals in SwiftData CloudKit?
Hi all, As you know, when using SwiftData Cloudkit, all relationships are required to be optional. In my app, which is a list app, I have a model class Project that contains an array of Subproject model objects. A Subproject also contains an array of another type of model class and this chain goes on and on. In this type of pattern, it becomes really taxxing to handle the optionals the correct way, i.e. unwrap them as late as possible and display an error to the user if unable to. It seems like most developers don't even bother, they just wrap the array in a computed property that returns an empty array if nil. I'm just wondering what is the recommended way by Apple to handle these optionals. I'm not really familiar with how the CloudKit backend works, but if you have a simple list app that only saves to the users private iCloud, can I just handwave the optionals like so many do? Is it only big data apps that need to worry? Or should we always strive to handle them the correct way? If that's the case
Topic: App & System Services SubTopic: iCloud & Data Tags:
Replies
3
Boosts
0
Views
199
Activity
Oct ’25
Reply to Issue when creating Bookmark with security scope on macOS 26 RC
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
Topic: App & System Services SubTopic: Core OS Tags:
Replies
Boosts
Views
Activity
Sep ’25
Sufficient mac for Xcode web app development project
Hi, I was looking for advice on the suitable mac to get for a web app development project for university . Would an Apple MacBook Air 2020 M1 8GB RAM 256GB SSD 13.3 macOS Big Sur, be sufficient ?? Or would I need a newer version !
Topic: Business & Education SubTopic: General
Replies
2
Boosts
0
Views
511
Activity
Sep ’25
Reply to BGContinuedProcessingTask launchHandler invocation
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
Topic: App & System Services SubTopic: Processes & Concurrency Tags:
Replies
Boosts
Views
Activity
Sep ’25
Reply to Understanding deep sleep
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
Topic: Privacy & Security SubTopic: General Tags:
Replies
Boosts
Views
Activity
Sep ’25
Reply to macOS 26 Launch Constraints
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.
Topic: Code Signing SubTopic: General Tags:
Replies
Boosts
Views
Activity
Sep ’25