column

Hi allI have put my first app on TestFlight for beta testing and have approximately 20 testers who have joined anonymously. When I look at the All Testers page I can see that several of them have submitted feedback ( there is a number in the feedback column), however I have not received any of this email.I have had some peope who are known to me try sending feedback via the Send Beta Feedback button in TestFlight and these emails are coming through to me fine so I think my email is configured ok. I seem to be missing something very basic here - I was wondering if someone could tell me how I can access the feedback related to the number shown in the feedback column on the All Testers page? Is this an iOS 13 functionality??Many thanks and best wishes

I have a Catalyst app that I'm adding a sidebar to via UISplitViewController. I have a toolbar on the window with buttons that I want to be enabled or disabled based on the state of the view controller in the split view's secondary column. But it seems to want to check the primary view controller instead. In the Catalyst tutorial Adding a Toolbar, this exact approach is demonstrated. The RecipeDetailViewController has methods for toggleFavorite and editRecipe, and the toolbar items are set up to reference those selectors in the ToolbarDelegate class. In the screenshots in the tutorial, the buttons are shown as enabled based on RecipeDetailViewController.canPerformAction. But when I download and run the complete project on my computer (macOS 14.4.1), the toolbar items are disabled. And if I add the methods to the RecipeListViewController (which is in the primary column of the UISplitViewController, the toolbar items get enabled. Is there a way to make the system ask the correct split view column

Bug in iOS 18 beta? .onAppear of a NavSplitView-DetailView is called repeatedly after dismissing the view. The app gets unresponsive and can only be killed and cold-restartet. What happens: I update a Binding property in .onAppear of a NavigationSplitView-DetailView. Whenever I leave the DetailView going back to the ListView (the NavSplitView’s first column), the DetailView's .onAppear get’s triggered in an endless loop. This blocks the main thread and freezes the app. This behaviour is only appearing in iOS 18 betas (simulators and devices) and not on iOS 17.x releases. If I remove the code updating the Binding, the .onAppear loop does not happen. Another way of triggering the same unexpected behaviour is by updating an OberservedObject appState.shared singleton, e.g. by a timer. Has anybody come across this type of behaviour? Is this a know change of iOS 18 behaviour or a bug even?

I have an iPad app using the new UITabBarController on iPadOS18, which is suffering from a new issue from the new layout. Within my tabs, I have a UISplitViewController, with a 2 column layout. If I load the app, it works ok, but if I put the app in the background, and then bring it to foreground, the navigation bar buttons and title just disappear from the splitView controller’s primary view controller. Before going to background: After coming back from background: I also get the following layout issues posted in the debugger consoler: Unable to simultaneously satisfy constraints. Probably at least one of the constraints in the following list is one you don't want. Try this: (1) look at each constraint and try to figure out which you don't expect; (2) find the code that added the unwanted constraint or constraints and fix it. ( , , , = UILayoutGuide:0x600003b00a80'TabBarGuide(0x103d18810)'.trailing (active)>, , ) Will attempt to recover by breaking constraint Make a symbolic breakpoint at UIVie

Xcode prompts the error at var body: some View. I cannot understand what's wrong here because there was no changes after the last successful build. To solve I have already done: Clean Build Folder for several times Restart Xcode Nothing worked. import SwiftUI struct HomeView: View { @StateObject private var viewModel = HomeViewModel() @State var tabSelection: Int = 0 var body: some View { TabView { NavigationStack { Group { if viewModel.entries.isEmpty { EmptyStateView() } else { EntriesGridView(entries: viewModel.entries, tags: viewModel.tags, selectedTag: $viewModel.selectedTags) } } } .tabItem { Label(Saved, systemImage: bookmark) } SettingsView() .tabItem { Label(Settings, systemImage: gear) } } .onAppear { viewModel.fetchTags() viewModel.fetchEntries() } } } #Preview { HomeView() } Other related parts without any errors: HomeViewModel.swift import SwiftUI import Firebase import FirebaseFirestore import FirebaseFirestoreSwift import os.log @MainActor class HomeViewModel: ObservableObject { @Published var

We use the triple column layout and when running our app under Sequoia Beta, the Secondary view controller's navigation bar is not shown initially. If a view is pushed inside the secondary (which contains a UINavigationController), and then popped again, the navigation bar is shown.

Is it possible to have conditional table columns for a swifui Table statement? Like for this code TableColumn(Image) { artPiece in if let imageData = artPiece.artImage.first, let image = UIImage(data: imageData!) { Image(uiImage: image) .resizable() .frame(width: 50, height: 50) } else { Image(systemName: photo) .resizable() .frame(width: 50, height: 50) } } .customizationID(Image) TableColumn(Name, value: .artName) .customizationID(Name) TableColumn (Art ID, value: .artPieceID) { artPiece in Text(String(artPiece.artPieceID)) } .customizationID(Art ID) have a conditional TableColumn for this part of my SWIFTDATA model var artDefinedFields: [ArtDefinedFields] = [] or if I change the variable string array to this var artDefinedFields: [ArtDefinedFields] = Array(repeating: ArtDefinedFields(), count: 10), initialize the array with None and only create a TableColumn when there is aArtDeginedFields value other than None

I'm developing an iOS 14 Catalyst app and I'm trying to setup the window toolbar. I created a NSToolbar and assigned to the scene window titlebar property. var toolbarDelegate = ToolbarDelegate() func scene(_ scene: UIScene, willConnectTo session: UISceneSession, options connectionOptions: UIScene.ConnectionOptions) { #if targetEnvironment(macCatalyst) guard let windowScene = scene as? UIWindowScene else { return } let toolbar = NSToolbar(identifier: main) toolbar.delegate = toolbarDelegate toolbar.displayMode = .iconOnly if let titlebar = windowScene.titlebar { titlebar.toolbar = toolbar titlebar.toolbarStyle = .unified titlebar.titleVisibility = .hidden } #endif } I then assigned some items to the toolbar via the toolbarDefaultItemIdentifiers delegate method. func toolbarDefaultItemIdentifiers(_ toolbar: NSToolbar) -> [NSToolbarItem.Identifier] { let identifiers: [NSToolbarItem.Identifier] = [ .toggleSidebar, .print, .flexibleSpace, .print ] return identifiers } This work as expected. Now, let's say that

I need the whole row (including space without content) within the NavigationLink to accept a double click gesture as well as the standard single click that will activate the row and display in the Detail View. If I use an onTapGesture(count:2) or simultaneousGesture(TapGesture(count:2) it doesn't quite work as expected. The content of the row will trigger the double click action but not the normal single click behaviour of the NavigationLink and requires clicking in an unpopulated area of the row. I have tried another onTapGesture with count:1 after the first to explicitly tell it to display the detail view which works but does not highlight the now selected row. I'd like to be able to double or single click anywhere in the list row, with a single click highlighting the row and displaying the detail view and a double click should do the same as the single click plus trigger an action. Similar to how Finder's column view works. If anyone could help with this it would be greatly appreciated.

The code for the issue is attached below. Hello, I am trying to implement a custom UICollectionViewLayout that does the following: Everything works great for the most part, however I have encountered some unexpected animations when applying a new snapshot: As you can see, any cell that contains a custom view with a height set with AutoLayout is scaled vertically before animating to it's intended height. Here is a simple Xcode project that demonstrates the issue. Tap on the plus sign in the top right corner and watch the cells. Example project: https://we.tl/t-9Y25NHzxiI Custom UICollectionViewLayout code: final class CustomLayout: UICollectionViewLayout { struct PMCardContainerLayoutCell: Equatable { var column: Int var row: Int } // Configurable properties public var numberOfColumns: Int = 6 public var cellHeight: Double = 100 public var cellSpacing: Double = 20 public var rowSpacing: Double = 20 public var sectionInsets: NSDirectionalEdgeInsets = .zero public var layoutAttributes: [IndexPath: UICol