“column”

I am porting my app to SwiftUI and I am hitting a wall when using ScrollView. In my application, I have nested scrollViews to represent a scheduler. outer vertical scroll view inner horizontal scroll view that allows to horizontally scroll multiple columns in the scheduler each column in the inner scroll view is a view that needs to allow for a drag to initiate the creation of a new appointment on macOS, I do a mouse-down drag, so it does not affect the scroll view and works fine on iOS, if I add a drag gesture to the column, it short circuits the scroll view and scrolling becomes disabled. To initiate the drag, there is a long-press, and that gesture is fine, only the subsequent drag gesture is problematic. I have attached URL to a test app. The UI allows you to toggle the drag gesture. Hopefully, someone can help to get it to work since I would eventually like to port the macOS target to Catalyst. Download Test App

Hi everyone 👋 I’m fairly new to iOS development and I’ve been stuck on a SwiftUI issue for a while now, so I’m hoping someone here can spot what I’m doing wrong. I’m using navigationTransition(.zoom) together with matchedTransitionSource to animate navigation between views. The UI consists of a grid of items (currently a LazyVGrid, though the issue seems unrelated to laziness). Tapping an item zooms it into its detail view, which is structurally the same view type and can contain further items. All good expect that interactive swipe-back sometimes causes the item to disappear from the grid once the parent view is revealed. This only happens when dismissing via the drag gesture; it does not occur when using the back button. I’ve attached a short demo showing the issue and the Swift file containing the relevant view code. Is there something obvious I’m doing wrong with navigationTransition / matchedTransitionSource, or is this a known limitation or bug with interactive swipe-back? Thanks in advance. import Swi

Hi team, In the Apple Music Feed datasets, we've noticed some unexpected values in the song and album tables. The primaryartists column from either song or album may contain a non-default artist name such as the katakana name shown in the example below: select id, name, namedefault, primaryartists from amf_song where id = '1698723329' id | name | namedefault | primaryartists ---------------------------------------- 1698723329 | {default=California} | California | [{id=1264818718, name=チャペル・ローン}] select * from amf_artist where id = '1264818718' id | name | namedefault | namepronunciation | ---------------------------------------------- 1264818718 | {default=Chappell Roan, ja=チャペル・ローン} | Chappell Roan | {ja=チャペルローン} | Shouldn't the primaryartists column be showing the namedefault instead of the Japanese language version? When can we expect this bug to resolved? Thanks,

When adding buttons to a sheet, on tvOS the text is blurred in the buttons, making it illegible. Feedback: FB21228496 (used GPT to extract an example from my project for a test project to attach here) // ButtonBlurTestView.swift // Icarus // // Test view to reproduce blurred button issue on tvOS // import SwiftUI struct ButtonBlurTestView: View { @State private var showSheet = false @State private var selectedTags: [Int] = [] @State private var newTagName: String = // Hardcoded test data private let testTags = [ TestTag(id: 1, label: Action), TestTag(id: 2, label: Comedy), TestTag(id: 3, label: Drama), TestTag(id: 4, label: Sci-Fi), TestTag(id: 5, label: Thriller) ] var body: some View { NavigationStack { VStack { Text(Button Blur Test) .font(.title) .padding() Button(Show Test Sheet) { showSheet = true } .buttonStyle(.borderedProminent) .padding() Text(Tap the button above to open a sheet with buttons inside a Form.) .font(.caption) .foregroundColor(.secondary) .multilineTextAlignment(.center) .padding() }

It seems to be that the functionality of the method setViewController:forColumn: in the column-style layout of a UISplitViewController has changed. iOS 18: setViewController:forColumn: pushes a new view controller onto the UINavigationController if it existed before the call. iOS 26: setViewController:forColumn: sets or replaces the view controller with a new view controller as a root of a new UINavigationController. My questions: what is the intended behavior? I did not find any documentation about a change. how do I replace in iOS 18 the old view controller with the new view controller passed to setViewController:forColumn:?

When trying to print an email with eM Client, the dialogue box pops up and the preview show the email's subject, To, and From lines in a long vertical column. This seems to only occur within the eM Client app and only on my Macbook Pro. I use the same email client on my Air with no issues. This is a recent development. I'm on Tahoe Beta 26.2.

Hi, We can easily get drive throughput using the iostat command, but it only outputs plain text that needs to be parsed, and I’m not sure if the format or column order is consistent across macOS versions. Is there any API that provides the same disk I/O metrics that iostat reports, but in a way that can be safely called from a notarized app?

I'm running a swift script that is emitting warning lines like this /Users/work/Documents/QuGame/QuGame/BoardTurnView.swift:1:1: warning: [dead-code] Debug-only symbol static SimpleTurn.== infix(SimpleTurn, SimpleTurn) -> Swift.Bool /Users/work/Documents/QuGame/QuGame/DataNotifications+PreviewData.swift:1:1: warning: [dead-code] Debug-only symbol DataNotifications.(addConversation)(to: QUBoardModel, local: GKPlayer, opponent: GKPlayer, texts: [Swift.String]) -> () /Users/work/Documents/QuGame/QuGame/DataNotifications+PreviewData.swift:1:1: warning: [dead-code] Debug-only symbol DataNotifications.loadBlankBoard() -> () These are correctly formatted for Xcode to detect the filename, line and columns. ` Showing Recent Issues [dead-code] Debug-only symbol static SimpleTurn.== infix(SimpleTurn, SimpleTurn) -> Swift.Bool [dead-code] Debug-only symbol DataNotifications.(addConversation)(to: QUBoardModel, local: GKPlayer, opponent: GKPlayer, texts: [Swift.String]) -> () [dead-code] Debug-only

I'm trying to create a UI with two button bars (top and bottom) inside the detail view of a NavigationSplitView, instead of using the built-in .toolbar() modifier. I'm using .ignoresSafeArea(.container, edges: .vertical) so the detail view can reach into that area. However, in macOS and iOS 26 the top button is not clickable/tappable because it is behind an invisible View created by the non-existent toolbar. Interestingly enough, if I apply .buttonStyle(.borderless) to the top button it becomes clickable (in macOS). On the iPad the behavior is different depending on the iPad OS version. In iOS 26, the button is tappable only by the bottom half. In iOS 18 the button is always tappable. Here's the code for the screenshot: import SwiftUI struct ContentView2: View { @State private var sidebarSelection: String? @State private var contentSelection: String? @State private var showContentColumn = true @State private var showBars = true var body: some View { NavigationSplitView { // Sidebar List(selection: $sidebarSel

At a high level, my app’s view hierarchy is a UISplitViewController, where the secondary column contains a UITabBarController that contains several UINavigationControllers. With this particular setup, I’m noticing every time a view controller is pushed, the navigation bar animation glitches. Notice how the back button and navigation title slightly slide left on each push, before abruptly resetting their positions. This issue only occurs when Liquid Glass is enabled. The issue does not occur if the UIDesignRequiresCompatibility key is added with a value of YES. I assume this is a UIKit bug, so I’ve filed FB20751418. But wondering if anyone is aware of any workarounds in the meantime as this animation glitch is quite distracting.