smb big sur

Kevin and ssmith_c for your assistance. I fortunately managed to file in the bug: FB20677188 Thank you! Looking over the bug, there was one point I wanted to comment on: For the Matter Media Device Basic Video Player Type Apple Home does support the commissioning (adding the device to the list of accessories displayed in Home App), but no controls are displayed. Not even the mandatory required controls: ... This type of Matter Device, which is part of the standard, should at least expose the mandatory controls and commands. The idea that Apple (and general ecosystem vendors more broadly) should try and support the full range of the Matter specification is, IMHO, one of those ideas which sounds reasonable on the surface but is, in fact, a very bad idea. First off, quoting myself: The Matter specification itself is sufficiently broad and complex that, in practice, I'm not sure it will ever really be possible to create a high-quality controller app* that actually supports EVERY possible accessory configuration i

Thanks so much, @tbartelmess1—this is super helpful, and really appreciated a bit more context from our app: App context (what we store) The blobs we persist will be user-generated cruise photos, we would downsize those to more manageable size as iphone format photos can be quite big, but they would still be in the 1-3 mb after downsizing Realistic volume per active user: a few hundred images/year; heavy users could reach low thousands over time. Decision: use Core Data Binary Data + “Allows External Storage” We’ll keep originals as Binary Data (Allows External Storage) so Core Data handles externalization transparently, my philosophy has always been to offload as much work to the system services as possible. We’ll keep thumbnails as well inline in coredata (let coredata decide but likely will be inline (blob)). CloudKit mirroring We’ll rely on NSPersistentCloudKitContainer mirroring; we understand CloudKit decides when an attribute becomes a CKAsset independently of Core Data’s externalization thres

Adding FBs as I find them. FB20652137 Replace button wraps unfortunately. Going through all the built in functions menu by menu (Adding print was easy enough.) Added Find and Replace to my text views in storyboard, which automagically enabled the menu item and produced this view. I don't even have Text size that big in my iPad Air 13-inch sim. Also, in trying to see if you could replicate it with built in apps I notice that the input view I get is unlike the snazzy Pages built in keyboard. I wonder if there is a way I can adopt the Pages UX? I mean, I don’t mind the glass buttons but would like to choose the color for done (blue just doesn’t go with our look and feel). Or let me change the blue which really doesn't go with our Color scheme.

While developing our driver, we've noticed that the *.ips report that contains the stack trace of the crash is not always generated. To be clear, you're talking about DEXT level users space crashes, NOT kernel panics? I've assumed below that you're dealing with standard crashes, but please let me know if I've misunderstood. I'm wondering why this report may not get generated. So, the first step here is to figure out what actually happened, which means digging through the console log. In general, there are multiple components tracking (notably, launchd) any system component (including DEXTs) and they'll be notified of your process's death, including how/why it died. If you're on development hardware then there are some tips in Your Friend the System Log that can be useful for quickly getting at this sort of data; however, I'd generally trigger a sysdiagnose and use that console archive. The big advantage of the sysdiagnose is that you capture everything, which means you're not going to miss data if so

Once, the App Store empowered indie creators - small teams could launch great apps Nothing has changed in that respect. There are more opportunities now for people to build low-quality apps by using low-quality, cross-platform frameworks and tools. But people are still able to launch great apps with discipline, intelligence, and hard work. and find users easily This part has changed. There are lots more apps to choose from, a radically different marketplace, and different user expectations. It now takes more work and more time to find users. But in 2025, that era feels long gone, with algorithms, big players, and pay-to-win discoverability reshaping everything. Many things have changed over the past 17 years. Is there still a real chance for indie iOS developers today, or has Apple’s evolving ecosystem made independent success nearly impossible? Many people are having success. They're just focused on their products and providing a great experience for their customers. Posting content on social media

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

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.