Search results for

“swiftui”

17,495 results found

Post

Replies

Boosts

Views

Activity

DeviceActivityReport extension not discovered at runtime (ClientError Code=2)
Hi I am trying to implement a minimal DeviceActivityReport extension. Setup: iOS app with FamilyControls authorization (status = approved) DeviceActivityReport displayed in SwiftUI Report extension embedded in PlugIns Correct NSExtensionPointIdentifier: com.apple.deviceactivityui.report-extension No NSExtensionPrincipalClass or storyboard Entitlements: com.apple.developer.family-controls com.apple.developer.family-controls.app-and-website-usage The app installs and runs correctly. Authorization is granted. However, the extension is never loaded: No logs from the extension (init/body/makeConfiguration never called) Console shows: Failed to discover the client's extension: DeviceActivityReportService... ClientError Code=2 Environment: Xcode 16.2 iOS device running iOS 18.x (latest available) The .appex is correctly embedded and signed. Question: Is there a known issue with DeviceActivityReport extensions not being discovered at runtime with this setup? Is additional configuration required beyond NSExte
2
0
462
Apr ’26
How to Indicate Selected State for a Menu Toolbar Item (Filter) in SwiftUI?
hi, On my page’s toolbar, I have a toolbar item that is implemented as a menu. Its purpose is to filter the content displayed on the page, similar to the filtering feature in the Photos app. When a user selects a filter option, I want the toolbar item to appear highlighted to indicate the active state. I came across the following guidance in the Human Interface Guidelines: Provide a selected-state version of an interface icon only if necessary. You don’t need to provide selected and unselected appearances for an icon that’s used in standard system components such as toolbars, tab bars, and buttons. The system updates the visual appearance of the selected state automatically. An image of two toolbar buttons that share a background. The left button shows the Filter icon in a selected state, using a blue tint color for its background. The right button shows the More icon in an unselected state, using the default appearance for toolbar buttons. In a toolbar, a selected icon receives the app’s accent color. Howeve
Topic: UI Frameworks SubTopic: SwiftUI
0
0
160
Apr ’26
Reply to popoverTips don't display for toolbar menu buttons in iOS 26.1
This is the workaround that I am currently using, which is just using TipKit's model to drive a popover(). Note that these popovers, in iOS 26, use the iOS 26 LiquidGlass morphing-button popover style. import SwiftUI import TipKit extension View { func popoverTipWorkaround(_ tip: some Tip) -> some View { modifier(PopoverTipWorkaround(tip: tip)) } } private struct PopoverTipWorkaround: ViewModifier { let tip: T @State private var shouldDisplay = false func body(content: Content) -> some View { content .popover(isPresented: $shouldDisplay) { TipView(tip) .tipViewStyle(NoDismissTipStyle()) .tipBackground(.clear) .presentationCompactAdaptation(.popover) } .task { for await status in tip.statusUpdates { if status == .available { shouldDisplay = true } } } } } private struct NoDismissTipStyle: TipViewStyle { func makeBody(configuration: Configuration) -> some View { VStack(alignment: .leading) { configuration.title configuration.message } .padding() } }
Topic: UI Frameworks SubTopic: SwiftUI Tags:
Apr ’26
Reply to Drag on a Canvas with XCUICoordinate.press(...)
Thank-you for your reply. First, I want to re-iterate that the application appears run correctly and the difficulty is only with the XCUITest part. That of course does not mean that the application is put together correctly, only that it seems to work for me. I did use an explicit co-ordinate space. My SwiftUI Canvas structure employed the .coordinateSpace modifier with a .named(...) parameter specifying a character string constant. My DragGesture also used the same .named(...) parameter; as do my MagnifyGesture and my SpatialTapGesture. I'll change the code to use .local for the gesture definitions and remove the modifier to the Canvas structure. It is also the case that my Canvas structure employs an animation modifier .animation(.interactiveSpring, value: currentOffset) Did you also animate the drag in your test application? The view hierarchy is: - NavigationStack -- VStack --- Spacer --- Text --- HStack ---- Text ---- Text ---- Text ---- Text --- Text --- Spacer --- GeometryReader ---- Canvas --
Apr ’26
SwiftUI Text rendering with too small height / one line missing causing unexpected text truncation on iPhone devices
FB: FB22577211 The following trivial SwiftUI Text rendering causes wrong text layout and truncated text. The text should take the required height to render the text without truncation. Adding fixedSize does also not solve this. This bug only happens on devices and not on the simulator. Confirmed with iPhone 15 and iOS 26.4.1 but my colleague used another iPhone so it’s multiple iPhone devices. import SwiftUI let txt = Es sollte die erste Japan-Tournee von vielen werden, kein anderes Land – abgesehen von Österreich und der Schweiz – bereisten die Berliner Philharmoniker häufiger. Wie kam es zu dem überschäumend herzlichen Empfang, der dem Orchester bei seinem ersten Gastspiel in Tokio bereitet wurde und wie wurde das Land zu einer »zweiten Heimat« für die Berliner? Ein konkreter historischer Grundstein für das hohe Ansehen klassischer Musik »made in Germany« in Japan wurde bereits im 19. Jahrhunderts gelegt: Als Teil von umfassenden gesellschaftlichen Modernisierungsmaßnahmen vergab die Regi
10
0
1k
Apr ’26
Previews crash after making change to Swift Package version
Previews seemed to be working okay. However, I wanted to test out some changes inside of a package that I'm working on for work, but in a lighter project since in our main project (where I have the package pulled in locally for now) is just too big to have the previews render in a decent amount of time. So, I opened a small project that was already importing that package and was set to 'Up to Next Major', but I switched that to 'branch' and added my branch. This is the second time I've done that and it causes Xcode to freak out in terms of the previews. This is the code I have: import SwiftUI extension EnvironmentValues { @Entry var trailingDescriptionColorToken: Color = .secondary } extension View { func updateTrailingDescriptionColor(to colorToken: Color, when trigger: Bool) -> some View { environment(.trailingDescriptionColorToken, trigger ? colorToken : .secondary) } } // MARK: - ListItemDescription public struct ListItemDescription: View { @Environment(.trailingDescriptionColorToken) var trai
0
0
151
Apr ’26
Reply to Drag on a Canvas with XCUICoordinate.press(...)
I built a test project with a SwiftUI Canvas that draws a simple network graph and pans via a DragGesture. I added UI tests that use XCUICoordinate.press(forDuration:thenDragTo:) with various drag distances and compared the requested distance against the content offset the app reported. In every case the values matched 1:1 — a 200-point drag moved the content exactly 200 points. This suggests the mismatch you're seeing is specific to your view hierarchy or how you apply the drag translation. A few things to check: Scale transforms: If you apply a scale to the Canvas or a parent view (for example, pinch-to-zoom), the gesture translation arrives in screen points while the content moves in scaled coordinates. A 2x scale would make the content appear to move twice as far as expected. Coordinate space: If your DragGesture specifies a coordinateSpace other than .local, the translation values are reported in that space, which may not match the Canvas coordinate system. Nested scroll views or gesture-interce
Apr ’26
Reply to segmented picker style causes runtime warning
Thanks so much for this very interesting post. I used the latest beta of Xcode and I do not see this warning with Version 26.5 beta 2. I believe, but haven’t seen this before, maybe a known issue in SwiftUI on macOS. It occurs because of how SwiftUI bridges AppKit's NSSegmentedControl to the .segmented picker style. That's why changing it to .automatic does not provide you this warning. But please do try the latest beta. Let me know if you can try that Xcode Version. Albert
  Worldwide Developer Relations.
Topic: UI Frameworks SubTopic: SwiftUI Tags:
Apr ’26
segmented picker style causes runtime warning
On OSX, using a segmented picker style causes the following warning to be emitted (when a different selection is made) : Publishing changes from within view updates is not allowed, this will cause undefined behavior. The warning is not emitted using the 'Preview Canvas' only when running the app. Changing the picker style to automatic also fixes it, but the segmented style is used extensively. Tested using XCode 26.4.1 on MacOS 26.3.1 --- view --- import SwiftUI internal import Combine enum Mode : String { case one, two, three } class MyObject : ObservableObject { @Published var mode : Mode = .one } struct ContentView: View { @StateObject var obj = MyObject() var body: some View { VStack { Picker(Mode,selection: $obj.mode) { Text(One).tag(Mode.one) Text(Two).tag(Mode.two) Text(Three).tag(Mode.three) } .pickerStyle(.segmented) } .padding() } } #Preview { ContentView() } --- app --- import SwiftUI @main struct SwiftUIBugApp: App { var body: some Scene { WindowGroup { ContentView() } } }
6
0
290
Apr ’26
Reply to SwiftUI bottom bar triggers UIKitToolbar hierarchy fault and constraint errors
import SwiftUI struct ContentView: View { var body: some View { NavigationStack { Text(XX) .toolbar { ToolbarItem(placement: .bottomBar) { Text(YY) } } } } } Here is an even simpler ContentView that demonstrates the same error. This occurs for both iOS 26.4 and iPadOS 26.4 The output generated in the Xcode console is: 'UIKitToolbar' as a subview of UIHostingController.view is not supported and may result in a broken view hierarchy. Add your view above UIHostingController.view in a common superview or insert it into your SwiftUI content in a UIViewRepresentable instead.
Topic: UI Frameworks SubTopic: SwiftUI Tags:
Apr ’26
Drag on a Canvas with XCUICoordinate.press(...)
I am trying to create a test case in XCTest using the UI Test target. I have a use case where I use a SwiftUI Canvas to draw a network graph; and the user can drag the graph on the Canvas. After the drag, the user may click on a node. The application presents a popup with the information about the network node clicked. SwiftUI provides the information required for the application to translate the location of the tap into the original location prior to the drag; and so the logic behind the popup can determine which node the network graph was tapped by the user. It appears that the distance of the drag operation performed does not match distance that the image actually moved. The drag distance is always larger than the actual distance dragged. I can observe this during the test execution. The arrow starts at the correct spot but then goes further than the object being dragged. I also observe this when I am driving the application. Is there some standard and supported way to determine the dista
3
0
401
Apr ’26
Reply to SwiftUI View Not Initialized on Background Relaunch (CoreBluetooth / Cold Start?)
Argun and I have been talking about this issue privately, and he asked me to comment on this: [quote='884915022, Engineer, /thread/823017?answerId=884915022#884915022'] I will leave the discussion of why UI elements are sometimes not initialized for non-UI (background) launches to others [/quote] Yeah, that’s been confusing folks since we first introduced multitasking to iOS |-: When the system launches your app in the background, it may or may not instantiates your views. Whether it does is based on a wide range of criteria, stuff that’s changed in the past and may well change again in the future. For example, the system might want to refresh its snapshop of your app’s UI, in which case it has to instantiate your views in order to do that. Or it might be happy with its current snapshot, and thus not. Which brings us to this: [quote='884915022, Engineer, /thread/823017?answerId=884915022#884915022'] In general it is not a correct pattern to make app-wide non-UI functionality dependent on UI elements [/quote]
Topic: UI Frameworks SubTopic: SwiftUI Tags:
Apr ’26
Reply to Increase Contrast reduces List selection contrast in dark appearance in SwiftUI NavigationSplitView
I think there are two confounding issues here. The first is that the default accentColor is not intended to be used as a background color, and its high contrast versions reduce rather than increase contrast with .primary color text (in both light and dark themes). NavigationSplitView & Passwords are both using the default accentColor while Contacts and Messages are both probably using a custom color as a background, which have high contrast versions that are intended to be used as a background for .primary color text. The other issue is much more difficult to work around, which is that certain views aren't actually using the high contrast version of the color, but are further amplifying these colors programmatically, even if you do specify a high contrast color. I think this is based on whether they are contained inside other UIKit-based views, but I am very not sure. import SwiftUI @main struct HighContrastBlueDemoApp: App { var body: some Scene { WindowGroup { ContentView() } } } struct Content
Topic: UI Frameworks SubTopic: SwiftUI Tags:
Apr ’26
SwiftUI Catalyst Resizable Sheet
I am porting a macOS app to SwiftUI Catalyst and have run into a usability issue. On macOS, presented sheets are user resizable. On SwiftUI macOS, they are also resizable, but on Catalyst, they are not. Does anyone have a good reference on how to make a sheet resizable under SwiftUI Catalyst?
Topic: UI Frameworks SubTopic: SwiftUI
0
0
226
Apr ’26
DeviceActivityReport extension not discovered at runtime (ClientError Code=2)
Hi I am trying to implement a minimal DeviceActivityReport extension. Setup: iOS app with FamilyControls authorization (status = approved) DeviceActivityReport displayed in SwiftUI Report extension embedded in PlugIns Correct NSExtensionPointIdentifier: com.apple.deviceactivityui.report-extension No NSExtensionPrincipalClass or storyboard Entitlements: com.apple.developer.family-controls com.apple.developer.family-controls.app-and-website-usage The app installs and runs correctly. Authorization is granted. However, the extension is never loaded: No logs from the extension (init/body/makeConfiguration never called) Console shows: Failed to discover the client's extension: DeviceActivityReportService... ClientError Code=2 Environment: Xcode 16.2 iOS device running iOS 18.x (latest available) The .appex is correctly embedded and signed. Question: Is there a known issue with DeviceActivityReport extensions not being discovered at runtime with this setup? Is additional configuration required beyond NSExte
Replies
2
Boosts
0
Views
462
Activity
Apr ’26
How to Indicate Selected State for a Menu Toolbar Item (Filter) in SwiftUI?
hi, On my page’s toolbar, I have a toolbar item that is implemented as a menu. Its purpose is to filter the content displayed on the page, similar to the filtering feature in the Photos app. When a user selects a filter option, I want the toolbar item to appear highlighted to indicate the active state. I came across the following guidance in the Human Interface Guidelines: Provide a selected-state version of an interface icon only if necessary. You don’t need to provide selected and unselected appearances for an icon that’s used in standard system components such as toolbars, tab bars, and buttons. The system updates the visual appearance of the selected state automatically. An image of two toolbar buttons that share a background. The left button shows the Filter icon in a selected state, using a blue tint color for its background. The right button shows the More icon in an unselected state, using the default appearance for toolbar buttons. In a toolbar, a selected icon receives the app’s accent color. Howeve
Topic: UI Frameworks SubTopic: SwiftUI
Replies
0
Boosts
0
Views
160
Activity
Apr ’26
Reply to popoverTips don't display for toolbar menu buttons in iOS 26.1
This is the workaround that I am currently using, which is just using TipKit's model to drive a popover(). Note that these popovers, in iOS 26, use the iOS 26 LiquidGlass morphing-button popover style. import SwiftUI import TipKit extension View { func popoverTipWorkaround(_ tip: some Tip) -> some View { modifier(PopoverTipWorkaround(tip: tip)) } } private struct PopoverTipWorkaround: ViewModifier { let tip: T @State private var shouldDisplay = false func body(content: Content) -> some View { content .popover(isPresented: $shouldDisplay) { TipView(tip) .tipViewStyle(NoDismissTipStyle()) .tipBackground(.clear) .presentationCompactAdaptation(.popover) } .task { for await status in tip.statusUpdates { if status == .available { shouldDisplay = true } } } } } private struct NoDismissTipStyle: TipViewStyle { func makeBody(configuration: Configuration) -> some View { VStack(alignment: .leading) { configuration.title configuration.message } .padding() } }
Topic: UI Frameworks SubTopic: SwiftUI Tags:
Replies
Boosts
Views
Activity
Apr ’26
Reply to Drag on a Canvas with XCUICoordinate.press(...)
Thank-you for your reply. First, I want to re-iterate that the application appears run correctly and the difficulty is only with the XCUITest part. That of course does not mean that the application is put together correctly, only that it seems to work for me. I did use an explicit co-ordinate space. My SwiftUI Canvas structure employed the .coordinateSpace modifier with a .named(...) parameter specifying a character string constant. My DragGesture also used the same .named(...) parameter; as do my MagnifyGesture and my SpatialTapGesture. I'll change the code to use .local for the gesture definitions and remove the modifier to the Canvas structure. It is also the case that my Canvas structure employs an animation modifier .animation(.interactiveSpring, value: currentOffset) Did you also animate the drag in your test application? The view hierarchy is: - NavigationStack -- VStack --- Spacer --- Text --- HStack ---- Text ---- Text ---- Text ---- Text --- Text --- Spacer --- GeometryReader ---- Canvas --
Replies
Boosts
Views
Activity
Apr ’26
SwiftUI Text rendering with too small height / one line missing causing unexpected text truncation on iPhone devices
FB: FB22577211 The following trivial SwiftUI Text rendering causes wrong text layout and truncated text. The text should take the required height to render the text without truncation. Adding fixedSize does also not solve this. This bug only happens on devices and not on the simulator. Confirmed with iPhone 15 and iOS 26.4.1 but my colleague used another iPhone so it’s multiple iPhone devices. import SwiftUI let txt = Es sollte die erste Japan-Tournee von vielen werden, kein anderes Land – abgesehen von Österreich und der Schweiz – bereisten die Berliner Philharmoniker häufiger. Wie kam es zu dem überschäumend herzlichen Empfang, der dem Orchester bei seinem ersten Gastspiel in Tokio bereitet wurde und wie wurde das Land zu einer »zweiten Heimat« für die Berliner? Ein konkreter historischer Grundstein für das hohe Ansehen klassischer Musik »made in Germany« in Japan wurde bereits im 19. Jahrhunderts gelegt: Als Teil von umfassenden gesellschaftlichen Modernisierungsmaßnahmen vergab die Regi
Replies
10
Boosts
0
Views
1k
Activity
Apr ’26
Previews crash after making change to Swift Package version
Previews seemed to be working okay. However, I wanted to test out some changes inside of a package that I'm working on for work, but in a lighter project since in our main project (where I have the package pulled in locally for now) is just too big to have the previews render in a decent amount of time. So, I opened a small project that was already importing that package and was set to 'Up to Next Major', but I switched that to 'branch' and added my branch. This is the second time I've done that and it causes Xcode to freak out in terms of the previews. This is the code I have: import SwiftUI extension EnvironmentValues { @Entry var trailingDescriptionColorToken: Color = .secondary } extension View { func updateTrailingDescriptionColor(to colorToken: Color, when trigger: Bool) -> some View { environment(.trailingDescriptionColorToken, trigger ? colorToken : .secondary) } } // MARK: - ListItemDescription public struct ListItemDescription: View { @Environment(.trailingDescriptionColorToken) var trai
Replies
0
Boosts
0
Views
151
Activity
Apr ’26
Reply to Disabling font Anti-Aliasing in a Text in SwiftUI
Thank you for filing the feedback report, and that's a creative solution. Using a stitchable Metal shader with .colorEffect() to threshold the alpha is an elegant way to strip the anti-aliased fringe while staying entirely within SwiftUI's rendering pipeline. The results in your screenshot look great.
Topic: UI Frameworks SubTopic: SwiftUI Tags:
Replies
Boosts
Views
Activity
Apr ’26
Reply to Drag on a Canvas with XCUICoordinate.press(...)
I built a test project with a SwiftUI Canvas that draws a simple network graph and pans via a DragGesture. I added UI tests that use XCUICoordinate.press(forDuration:thenDragTo:) with various drag distances and compared the requested distance against the content offset the app reported. In every case the values matched 1:1 — a 200-point drag moved the content exactly 200 points. This suggests the mismatch you're seeing is specific to your view hierarchy or how you apply the drag translation. A few things to check: Scale transforms: If you apply a scale to the Canvas or a parent view (for example, pinch-to-zoom), the gesture translation arrives in screen points while the content moves in scaled coordinates. A 2x scale would make the content appear to move twice as far as expected. Coordinate space: If your DragGesture specifies a coordinateSpace other than .local, the translation values are reported in that space, which may not match the Canvas coordinate system. Nested scroll views or gesture-interce
Replies
Boosts
Views
Activity
Apr ’26
Reply to segmented picker style causes runtime warning
Thanks so much for this very interesting post. I used the latest beta of Xcode and I do not see this warning with Version 26.5 beta 2. I believe, but haven’t seen this before, maybe a known issue in SwiftUI on macOS. It occurs because of how SwiftUI bridges AppKit's NSSegmentedControl to the .segmented picker style. That's why changing it to .automatic does not provide you this warning. But please do try the latest beta. Let me know if you can try that Xcode Version. Albert
  Worldwide Developer Relations.
Topic: UI Frameworks SubTopic: SwiftUI Tags:
Replies
Boosts
Views
Activity
Apr ’26
segmented picker style causes runtime warning
On OSX, using a segmented picker style causes the following warning to be emitted (when a different selection is made) : Publishing changes from within view updates is not allowed, this will cause undefined behavior. The warning is not emitted using the 'Preview Canvas' only when running the app. Changing the picker style to automatic also fixes it, but the segmented style is used extensively. Tested using XCode 26.4.1 on MacOS 26.3.1 --- view --- import SwiftUI internal import Combine enum Mode : String { case one, two, three } class MyObject : ObservableObject { @Published var mode : Mode = .one } struct ContentView: View { @StateObject var obj = MyObject() var body: some View { VStack { Picker(Mode,selection: $obj.mode) { Text(One).tag(Mode.one) Text(Two).tag(Mode.two) Text(Three).tag(Mode.three) } .pickerStyle(.segmented) } .padding() } } #Preview { ContentView() } --- app --- import SwiftUI @main struct SwiftUIBugApp: App { var body: some Scene { WindowGroup { ContentView() } } }
Replies
6
Boosts
0
Views
290
Activity
Apr ’26
Reply to SwiftUI bottom bar triggers UIKitToolbar hierarchy fault and constraint errors
import SwiftUI struct ContentView: View { var body: some View { NavigationStack { Text(XX) .toolbar { ToolbarItem(placement: .bottomBar) { Text(YY) } } } } } Here is an even simpler ContentView that demonstrates the same error. This occurs for both iOS 26.4 and iPadOS 26.4 The output generated in the Xcode console is: 'UIKitToolbar' as a subview of UIHostingController.view is not supported and may result in a broken view hierarchy. Add your view above UIHostingController.view in a common superview or insert it into your SwiftUI content in a UIViewRepresentable instead.
Topic: UI Frameworks SubTopic: SwiftUI Tags:
Replies
Boosts
Views
Activity
Apr ’26
Drag on a Canvas with XCUICoordinate.press(...)
I am trying to create a test case in XCTest using the UI Test target. I have a use case where I use a SwiftUI Canvas to draw a network graph; and the user can drag the graph on the Canvas. After the drag, the user may click on a node. The application presents a popup with the information about the network node clicked. SwiftUI provides the information required for the application to translate the location of the tap into the original location prior to the drag; and so the logic behind the popup can determine which node the network graph was tapped by the user. It appears that the distance of the drag operation performed does not match distance that the image actually moved. The drag distance is always larger than the actual distance dragged. I can observe this during the test execution. The arrow starts at the correct spot but then goes further than the object being dragged. I also observe this when I am driving the application. Is there some standard and supported way to determine the dista
Replies
3
Boosts
0
Views
401
Activity
Apr ’26
Reply to SwiftUI View Not Initialized on Background Relaunch (CoreBluetooth / Cold Start?)
Argun and I have been talking about this issue privately, and he asked me to comment on this: [quote='884915022, Engineer, /thread/823017?answerId=884915022#884915022'] I will leave the discussion of why UI elements are sometimes not initialized for non-UI (background) launches to others [/quote] Yeah, that’s been confusing folks since we first introduced multitasking to iOS |-: When the system launches your app in the background, it may or may not instantiates your views. Whether it does is based on a wide range of criteria, stuff that’s changed in the past and may well change again in the future. For example, the system might want to refresh its snapshop of your app’s UI, in which case it has to instantiate your views in order to do that. Or it might be happy with its current snapshot, and thus not. Which brings us to this: [quote='884915022, Engineer, /thread/823017?answerId=884915022#884915022'] In general it is not a correct pattern to make app-wide non-UI functionality dependent on UI elements [/quote]
Topic: UI Frameworks SubTopic: SwiftUI Tags:
Replies
Boosts
Views
Activity
Apr ’26
Reply to Increase Contrast reduces List selection contrast in dark appearance in SwiftUI NavigationSplitView
I think there are two confounding issues here. The first is that the default accentColor is not intended to be used as a background color, and its high contrast versions reduce rather than increase contrast with .primary color text (in both light and dark themes). NavigationSplitView & Passwords are both using the default accentColor while Contacts and Messages are both probably using a custom color as a background, which have high contrast versions that are intended to be used as a background for .primary color text. The other issue is much more difficult to work around, which is that certain views aren't actually using the high contrast version of the color, but are further amplifying these colors programmatically, even if you do specify a high contrast color. I think this is based on whether they are contained inside other UIKit-based views, but I am very not sure. import SwiftUI @main struct HighContrastBlueDemoApp: App { var body: some Scene { WindowGroup { ContentView() } } } struct Content
Topic: UI Frameworks SubTopic: SwiftUI Tags:
Replies
Boosts
Views
Activity
Apr ’26
SwiftUI Catalyst Resizable Sheet
I am porting a macOS app to SwiftUI Catalyst and have run into a usability issue. On macOS, presented sheets are user resizable. On SwiftUI macOS, they are also resizable, but on Catalyst, they are not. Does anyone have a good reference on how to make a sheet resizable under SwiftUI Catalyst?
Topic: UI Frameworks SubTopic: SwiftUI
Replies
0
Boosts
0
Views
226
Activity
Apr ’26