“column”

Hi, It seems like it expected behavior. From the demo I can assume that it's not for those type of document. Imagine that you have a normal document, where you have a 2 columns of text. You wouldn't want to read it line by line like you want to do with receipts Unfortunately I try to do the same thing, so I have to stay with simple previous iOS OCR solution and trying to connect those in lines by my own (not very good) algorithm.

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.

Hi Ziqiao, the problem is that when you want to use SwiftData for an enterprise app, the user needs proper navigation. In such apps, you usually have more than one screen or form. I did some additional tests with your code and replaced the NavigationStack with a NavigationView. The reason is that I need the automatic two-column split for a sidebar menu and a detail view, not just a single view. The NavigationSplitView doesn’t seem to work as expected. Using it as a root view with an embedded TabView was my first attempt, but that didn’t work either. That’s why I tried embedding the NavigationSplitViews inside the TabView. When I replace your NavigationStack with a NavigationView, I get the automatic two-column view on iPad — but with a second navigation view below the DocumentGroup navigation view. This looks bugged. The NavigationSplitView also has issues with the back button and the document title in sheets. I’ll file a feedback report for now as you suggested and try to find a workaround

Can we bundle our app with our own version of SQLite with extensions that we want. Yes, and you should do that. The version that Apple includes depends on the iOS version (see https://github.com/yapstudios/YapDatabase/wiki/SQLite-version-(bundled-with-OS) for a table). If you use the Apple version, there's a danger that your app will break after an iOS update, or will not function on an older iOS version that you are still trying to support but don't test on as well as you should. I was caught out by the latter issue because the sqlite in iOS 14 doesn't support on conflict without a column list.

While I can't predict the future or comment on anything future looking, I'd like to color in some details of the complier so you have a more complete understanding of how things work, in hopes that you can use this information to inform your own decisions around adopting Swift 6. If you take a look at the Xcode support page and look at the table of Xcode versions, you'll notice the Swift column has two sets of data — the complier version, and language modes. As you stated, Swift 6 was released with Xcode 16, and you can see that in the version number of the complier in the chart. Every Xcode release has one version of the Swift complier, and so that means every app that has compiled with Xcode 16 or newer has already compiled with the Swift 6 complier. Your question here is better stated as what is the longevity of the Swift 5 language mode? The language mode (which you'll find in your project as the SWIFT_VERSION build setting) is the version of the language the compiler is using for its compilation

I have the same issue, I'm not able to reach the same side bar appearance as the Settings app with UISplitViewController (tested on iOS 26 Beta 4). I've created a very basic double column split view controller and there isn't the Liquid Glass effect around the edges of the primary view controller. Interestingly, it does work if one uses the SwiftUI equivalent NavigationSplitView. So either it's a bug in UISplitViewController, or it's not planned for it to support that appearance (hopefully not!).

Is there a modifier to make section headers non-sticky? You can use the automatic .listStyle(.automatic) or opt for a lazy stack instead and apply your decorators. For examples, refer to Grouping data with lazy stack views. .listStyle(.automatic) results in in .insetGrouped, so that's a different look. I tried the LazyVStack approach and this worked well for a screen that was pretty custom-styled anyway. Side note: LazyVStack made me a little upset by applying the spacing not only between rows, but also after the section header; requiring dancing around with the spacing and paddings to get the correct look; I wished for a separation of spacing between sections, spacing between rows and spacing between [section header/rows/section footer]. But I'm wondering if this is a well-rounded approach for Views that just want a plain styled data list. It's certainly more feasible with the delicate separators-going-all-the-way-through-to-the-edge-of-the-screen gone in iOS 26, but still, custom-rebuilding all the Views wi

So, my current experience with this. I am advertising my ios app with Google Ads app campaign. Whenever user does this one thing on the app, I log an event to Firebase/Google Analytics. That event there shows up fine with proper count. Then I export this event to Google Ads, and also make a SKAdNetwork mapping. This event shows up in Google Ads as a conversion action definition, but with status No recent conversions. I want it to show Active. I have also set AppsFlyer to receive winning SKAN postback copies (its a bit easier to read them there in the SKAN Overview section). I do see the app instals there, meaning I am getting SKAN postback copies, but the column Null conversion value rate is always 100% - meaning, each received postback has conversion value as NULL. Now, it is my understanding, that in order to update that Conversion Value (CV), we have 2 approaches: Directly: SKAdNetwork.updatePostbackConversionValue(5) { error in if let error = error { // Report production error to Sentry } } Indir