Search results for

smb big sur

11,798 results found

Post

Replies

Boosts

Views

Activity

Reply to Best Practices for Binary Data (“Allows External Storage”) in Core Data with CloudKit Sync
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
1w
Reply to Is there a tech note for menuBuilder?
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.
Topic: UI Frameworks SubTopic: UIKit
2w
Reply to *.ips CrashReport not always available when dext crashes
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
Topic: App & System Services SubTopic: Drivers Tags:
2w
Reply to Is It Still Possible for Indie iOS Apps to Thrive in 2025?
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
2w
Is It Still Possible for Indie iOS Apps to Thrive in 2025?
Once, the App Store empowered indie creators - small teams could launch great apps and find users easily. But in 2025, that era feels long gone, with algorithms, big players, and pay-to-win discoverability reshaping everything. Is there still a real chance for indie iOS developers today, or has Apple’s evolving ecosystem made independent success nearly impossible?
2
0
358
2w
in OS26, X Large circle uses small circle size for the maximum image sizes
Create a static widget kit based widget for watchKit. Use swiftUI and an image. IE on 42mm you can import a 141x141 image at 2x. Import a 141x141 image in the widget and load it in swiftUI. In watchOS 11.x simulator the image will allow up to the size for X Large circles, and on os26, it will not load and complain the image is too large and report the area for the smaller circle, IE 89x89 @ 2x for 41mm Also submitted a feedback ticket FB20506200 This is a big issue b/c the size difference for X large circles v the smaller circles is really large. To get existing images to load I am having to resize them down 75-80% on OS26 in the X Large complication.
1
0
46
2w
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
2w
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
4
0
129
3w
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
0
0
86
3w
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:
3w
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.
3w
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
3w
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
1
0
175
3w