Search results for

“column”

2,137 results found

Post

Replies

Boosts

Views

Activity

Reply to Is anyone can tell me where is wrong that my wrote?

I wrote some codes by advices of Deepseek You'd probably better try first to understand the code you are writing. navigationDestination should come after the List: NavigationSplitView { List{ NavigationLink(Account,value: 1) NavigationLink(Chat,value: 2) NavigationLink(Project,value: 3) NavigationLink(Enviroments,value: 4) } .navigationDestination(for: Int.self) { number in switch number { case 1: AccountView() case 2: ChatView() case 3: ProjectView() case 4: EnvView() default: Text(未知页面) } } On what device are you testing ? NavigationSplitView shrinks down to a single column when there is not enough room, such as iPhone.

UI Frameworks SwiftUI

TestFlight builds complete processing but can't test them

My latest TestFlight build has processed, and normally it pretty much immediately becomes available for testing. But today it's just been hanging, now for over an hour, with no 'Groups' column or any way of assigning it to a group. The status column shows the 'expiring in X days' text but no 'Ready to test' or 'Testing' text. It's almost like it's stuck in limbo. Anyone else having issues?

App Store Distribution & Marketing TestFlight

547

Reply to TestFlight builds complete processing but can't test them

Same here, and it's blocking me completely. What I'm seeing: Builds process fine and show Expires in 90 days, but never reach Ready to Test or Ready to Submit No Groups column and no way to assign a build to a tester group The Add button is greyed out from both the group page and the build detail page I also cannot expire builds any more What I've tried, none of which helped: Created a brand new internal group with Enable automatic distribution unticked, then tried to add the build to it. Add still greyed out. Uploaded additional builds with incremented build numbers In my case it started right after I manually expired an older build that had active testers, so I initially assumed I'd broken something myself. Seeing the reports here, it looks like the same underlying issue rather than anything account specific. Developer system status is still showing everything green. Boosting.

App Store Distribution & Marketing TestFlight

UICollectionView list: leading swipe overshoots in expanded split view for .plain/.grouped; .insetGrouped OK (iPadOS 26 b5–b8) [FB19785883]

Hi all, Sharing a reproducible UIKit issue I’m seeing across multiple iPadOS 26 betas, with a tiny sample attached and a short video. Short video https://youtu.be/QekYNnHsfYk Tiny project https://github.com/yoasha/ListSwipeOvershootReproSwift Summary In a UISplitViewController (.doubleColumn), a UICollectionView using list layout shows a large leading-swipe overshoot when the split view is expanded (isCollapsed == false). The cell content translates roughly 3–4× the action width. Repros with appearance = .plain and .grouped Does not repro with .insetGrouped Independent of trailing provider (issue persists when trailing provider is nil) Collapsed split (compact width) behaves correctly Environment Devices: iPad Air (3rd gen), iPadOS 26.0 (23A5326a) → Repro Simulators: iPad Pro 11-inch (M4), iPadOS 26.0 beta 6 → Repro Also tested on device: iPadOS 26 beta 5, 6, 7, 8 Xcode: 26.0 beta 6 (17A5305f) Steps to reproduce Launch the sample; ensure the split is expanded (isCollapsed == false). In the secondary list, set

UI Frameworks UIKit Beta iPadOS

394

How can I determine which side of a RoomPlan wall surface contains the wall thickness?

I am using Apple RoomPlan and working with CapturedRoom.Surface objects representing walls. From RoomPlan, I can get information such as: transform dimensions polygonCorners completedEdges However, I am not sure how the returned wall surface should be interpreted geometrically. Is the wall surface returned by RoomPlan: the centerline of the physical wall; the interior face of the wall; the exterior face of the wall; or simply an estimated 2D surface without any guarantee about wall thickness? If I want to create a wall with thickness, for example when converting RoomPlan data to IFC or another BIM format, how can I determine which side of the returned surface the wall should be extruded toward? Does RoomPlan provide any information such as: wall thickness; interior or exterior wall side; inward or outward normal; wall centerline; a full 3D wall boundary; or the opposite face of the wall? I can calculate the surface normal from the third column of the wall transform and obtain the wall-face boundary u

Graphics & Games SceneKit RoomPlan

350

Did VisionOS27 get the LazyVGrid Performance Updates?

Did VisionOS get the LazyVGrid Performance Updates that other platforms received? I’m observing that a LazyVGrid that works well on iPhone, iPad, and Mac appears to hitch and jitter as cells exit and renter the lazyVGrid on VisionOS. It really feels like it did not get the same behavior changes as the other platforms. I observe the scrollbar expands as cells leave the top of the grid, and each “exit” of a row seems to cause a hitch. I’ve got rigidly defined cell frames, rigidly defined columns. I don’t think any cells frames are being invalidated during scroll… (there’s no way to check this with instruments, right?) I‘ve made several analysis passes myself and threw the Xcode Agent with Codex at it just to scan for stuff, but it’s starting to just guess at things. Any known issues with VisionOS?

UI Frameworks SwiftUI SwiftUI

218

Reply to macOS Tahoe 26.5.1: Mac Catalyst App Crashes at Launch with EXC_BREAKPOINT in libsystem_secinit due to Container Integrity Check Failure

Thanks for confirming. I had a look at the source of this failed integrity checks for container error and it’s not as complicated as I first thought. Moreover, each of the integrity checks that it runs has an accompanying log point, so you should be able to learn more from the system log. Try this: Run Console and start stream log entries. Reproduce the problem. Switch to Console and pause the log. Search the log for log entries from the secinitd process (past process:secinitd into the search field) where the Subsystem column is blank and the Category column says [1]. What do you see? For example, in my tests I did this: I created a sandboxed test app. I ran it. I quit it. I replaced its Data/Library/Images directory with a file (mwa ha ha!). % rm -r ~/Library/Containers/com.example.apple-samplecode.Test836638/Data/Library/Images % touch ~/Library/Containers/com.example.apple-samplecode.Test836638/Data/Library/Images I ran the app. It crashed, with the crash report saying: failed integrity

App & System Services Core OS

Reordering API crashes when if #available or .popover present

I've encountered crashes when trying to reorder items using the new reordering API. Fatal error: Unexpected identifier type. Expected UUID, got UUID To reproduce, simply run one of the 2 first tests and comment out the others: import SwiftUI @main struct MyApp: App { var body: some Scene { WindowGroup { ContentView() } } } struct Task: Identifiable { let id = UUID() var title: String } struct ContentView: View { @State private var tasks = [ Task(title: Design Invoice), Task(title: Send Proposal), Task(title: Review Feedback), Task(title: Publish Update) ] @State private var showingPopover: Bool = false var body: some View { ScrollView { LazyVGrid( columns: [ GridItem(.adaptive(minimum: 100)) ] ) { ForEach(tasks) { task in // Test 1: This will crash when reordering if #available(iOS 26.0, macOS 26, *) { Text(task.title) .frame(maxWidth: .infinity) .padding() .background(.blue.opacity(0.1)) .clipShape(.rect(cornerRadius: 12)) } else { Text(task.title) .frame(maxWidth: .infinity) .padding() .background(

UI Frameworks SwiftUI

111

Reply to Code Signing (I think)

In Xcode > Settings > Apple Accounts, make sure you’re signed in with the Apple Account associated with your paid developer team. Then, in the Signing & Capabilities editor, make sure that this team is selected for each target. The error you’re seeing: [quote='836943021, Newebie, /thread/836943, /profile/Newebie'] Personal development teams … do not support the Accessory Setup Extension capability. [/quote] suggests that you’re signed with an Apple Account that’s not a member of a paid developer team, that is, you’re using a Personal Team). This lets you do basic stuff, but it doesn’t let you use the Accessory Setup Extension capability. In Developer Account Help > Reference > Supported capabilities (iOS) you’ll find a table of which capabilities are supported by which programme types. The first column is what you get when you’re a member of a paid developer team (Individual or Organization). The second column in what you get when you’re using your Personal Team. While Access

Code Signing General

Reply to How to style SwiftUI sidebar row selections like native macOS apps (Finder, Photos)

Hello @Moretheus, You have a good start! While I can't confirm exactly how Apple achieved a certain goal, I can show you how you can get the same result in your starting project. What you are noticing is that NSOutlineView.style = .sourceList displays the selection highlight using the system accent color. To set your own color, first disable the built-selection highlight by setting outline.selectionHighlightStyle = .none in makeNSView. Then create a separate view for the row that you can style to your liking. I used drawBackground to paint the selection and interiorBackgroundStyle to disable the SF symbol inverting to white when selected. final class SidebarRowView: NSTableRowView { override var isSelected: Bool { didSet { needsDisplay = true } } override func drawBackground(in dirtyRect: NSRect) { if isSelected { NSColor.systemGray .withAlphaComponent(0.2) .setFill() NSBezierPath(roundedRect: bounds.insetBy(dx: 8, dy: 1), xRadius: 5, yRadius: 5).fill() } } override var interiorBackgroundStyle: NSView.Backgro

UI Frameworks SwiftUI

Jul ’26

Reply to OS27 LazyVGrid hops like crazy on scroll up.

@DTS Engineer This sample project shows one LazyVGrid in a ScrollView, that looks fine – I'm curious to see if you find yourself needing to nest lazy stacks, there might be other ways to achieve the same result. I tried nesting lazyVgrids cause I wanted to try to have per-section column layouts. It was mess, though, with entire sections disappearing on scroll. Suggestion for perSection columns here: FB23162564 This exact situation is covered in our WWDC26 session I have watched this video. It is hard for me to know what about my views is not stable enough. The cells in my feedback project (FB23182374) are either a VStack or HStack, and that's not changed at run time in the project. It's compiled to always be VStack. Does that matter to the internal mechanisms of LazyVGrid if that VStack never changes? I will experiment with this in my more complex app. Given the VStack never changes, the cell body always contains an image display area that has an .aspectRatio modifier on it (giving it a stab

UI Frameworks SwiftUI

Jun ’26

Reply to NSTableView: checking for mouse-driven selection changes on macOS 27

Interesting. I can't get in on macOS 27 yet. A bit too early for me and I have couple of things that need to get finished first. Hard for an indy dev to keep up! In one app I already have my own gesture recognizers I added for Force Touch trackpads years ago and it didn't interfere with the usual mouse stuff. I still override mouseDown: mouseDragged: -mouseUp: in all the 'big Appkit controls (like NSCollectionView,NSOutlineView,NSBrowser). It's been awhile since I looked at that Force Touch gesture code so I wonder how this transition will affect that codebase. My biggest concern is Apple's most neglected control NSBrowser. Currently you have to use deprecated API to even get a dragging session to work. NSBrowser has some really old peculiar behaviors like posting live resize notifications for the window when only a column is being resized. And a lot of the browser stuff is done in the private table views which are still cell based. I think I put a hack gesture recognizer on the browser that helps me

UI Frameworks AppKit

Jun ’26

Reply to Requesting Network Extension Capability

@DTS Engineer This link is not working, do we have any sample service or documentation? So that we can refer to it for an implementation purpose. I'm not sure what's going on there. I know the link worked yesterday because that's how I found it, but I also watched it fail as I started writing your post... and now it appears to be working again. You can try the link above again or you can get to the same place by starting at the pir-service-example (note that this is the example project itself) page and clicking on Documentation in the right-hand column. The Anonymous Authentication article is the first article in the articles list on the left-hand side of the documentation page. I'm not sure if which of those links will work for you, but hopefully that's enough to get you to the right places. __ Kevin Elliott DTS Engineer, CoreOS/Hardware

App & System Services Networking

Jun ’26

Reply to Push new views to sidebar when using NavigationPath

Hello @agorski, Thank you for your post. SwiftUI's NavigationSplitView is designed to catch and route links to content or detail. If using these columns don't work for you, create a sidebar that manages its own state: struct SidebarView: View { @State private var selected: ... Or use a different navigation design pattern that does not route links to detail. In my testing, I was able to get a TabView or the following code to code to work: enum Item: String, CaseIterable { case indigoView, tealView, orangeView, pinkView, greenView, purpleView, yellowView var color: Color { switch self { case .indigoView: .indigo case .tealView: .teal case .orangeView: .orange case .pinkView: .pink case .greenView: .green case .purpleView: .purple case .yellowView: .yellow } } } struct ContentView: View { var body: some View { NavigationSplitView { SidebarView() } detail: { ContentUnavailableView(Static Detail View, systemImage: paintpalette) } } } struct SidebarView: View { var body: some View { NavigationStack { List(

UI Frameworks SwiftUI

Jun ’26

Zoom transition source tile lags after back navigation when LazyVGrid is scrolled immediately

[Submitted as FB21961572] When navigating from a tile in a scrolling LazyVGrid to a child view using .navigationTransition(.zoom) and then returning, the source tile can lag behind the rest of the grid if scrolling starts immediately after returning. The lag becomes more pronounced as tile content gets more complex; in this simplified sample, it can seem subtle, but in production-style tiles (as used in both of my apps), it is clearly visible and noticeable. This may be related to another issue I recently filed: Source item disappears after swipe-back with .navigationTransition(.zoom) CONFIGURATION Platform: iOS Simulator and physical device Navigation APIs: matchedTransitionSource + navigationTransition(.zoom) Container: ScrollView + LazyVGrid Sample project: ZoomTransition (DisappearingTile).zip REPRO STEPS Create a new iOS project and replace ContentView with the code below. Run the app in sim or physical device Tap any tile in the scrolling grid to navigate to the child view. Return to the grid (back butt

UI Frameworks SwiftUI

602

Jun ’26

Reply to Is anyone can tell me where is wrong that my wrote?

UI Frameworks SwiftUI