“swiftui”

Unfortunately, SwiftPM does not inherit Xcode's build settings at all from a containing project. And there is no way to specify any Xcode build setting in a package manifest. Specifying an executable target with SwiftUI in a package is an interesting case. If I were in your shoes, I'd just pull everything out into another module target in the package and have the executable depend on it. Previewing in that module will work just fine. All the executable needs is the @main entry point. It doesn't need the views or previews to be in that target.

I have an executable SwiftUI target in my swift package, and have run into this error also - Previews requires ENABLE_DEBUG_DYLIB=YES to be defined. currently my package.swift has this: .executableTarget( name: ColorPickerDemo, dependencies: [ColorPicker], path: Sources/ColorPickerDemo, swiftSettings: [ .enableUpcomingFeature(ApproachableConcurrency), .define(ENABLE_DEBUG_DYLIB) ], linkerSettings: [ .unsafeFlags([ -Xlinker, -sectcreate, -Xlinker, __TEXT, -Xlinker, __info_plist, -Xlinker, Sources/ColorPickerDemo/Info.plist, ]), ] together with an info.plist for the executable, and the demo swiftui app can be launched. Clearly that isn't enough for previews though.. Any ideas?

Data point from July 2026: this appears to work now - at least on current OS versions. Setup: iPhone companion (iOS 26.5) + SwiftUI-lifecycle watchOS app (watchOS 26.5) with WidgetKit accessory complications (no ClockKit) transferCurrentComplicationUserInfo() with a small dictionary payload (~6 keys), complication active on the watch face (isComplicationEnabled == true; the transfer budget was actually consumed: remainingComplicationUserInfoTransfers went 50 → 49 → 48 → 47) Both sides instrumented with file logging; every payload carries a monotonically increasing version, and we redundantly send the same update via updateApplicationContext as a fallback - so I can attribute exactly which channel applied each change Results - 3 consecutive sends while the watch was NOT reachable (isReachable == false on the phone at send time) and the watch app was backgrounded: sent 23:10:42.5 → didReceiveUserInfo on the watch at 23:10:57.6 (15.1 s). Ambiguous: the user happened to foreground the watch app ~150 ms b

This is very interesting post hope I understand correctly what you trying to accomplish, and more about when talking about MultipleScenes and moving Scenes to external displays. To build a native iPadOS application that utilizes an external display with custom layouts while preserving pointer interaction, you must adopt a Multi-Scene Architecture. But hope other developers also provide their solution here. https://developer.apple.com/documentation/swiftui/scene Treats the external display as an extended desktop. Fully preserves native pointer interaction, hover effects, and custom interactive layouts. You cannot force the window to open full-screen on the external display automatically; the OS or the user dictates window placement, though you can programmatically request a new scene. Because your app will effectively run two independent UI hierarchies (one on the iPad, one on the external display), your architecture must strictly separate UI from state. https://developer.apple.com/documentation/uikit

Following up to say that this remains broken in macOS 27 beta 3. macOS 27.0 Beta (26A5378j) Xcode 27.0 beta 3 (27A5218g) Open Xcode, File -> New Project, macOS SwiftUI app and copy paste the code above and then run.

Has anyone found a workaround or solution? I'm seeing this behavior in Xcode 26.6 (17F113) and MacOS 26.5.2., even with Apple's own example code. import SwiftUI struct SliderViewTest: View { @State private var speed = 50.0 @State private var isEditing = false var body: some View { VStack { Slider( value: $speed, in: 0...100, step: 5 ) { Text(Speed) } minimumValueLabel: { Text(0) } maximumValueLabel: { Text(100) } onEditingChanged: { editing in isEditing = editing } Text((speed)) .foregroundColor(isEditing ? .red : .blue) } } } #Preview { SliderViewTest() .padding() }

[quote='836918021, pabugeater2, /thread/836918, /profile/pabugeater2'] find it pleasing/beneficial/productive to learn Swift/SwiftUI? [/quote] Let’s break that down: Pleasing That’s very much gonna depend on you. Beneficial Yes. Regardless of any other factors, there’s solid evidence that learning new stuff is beneficial, especially as you get older. Productive That kinda depends on what you intend to produce (-: As someone who’s not exactly young myself, I’ve started to understand that the time I have left is limited, and that I need to focus on what I enjoy. I absolutely love playing around with computers, so if and when I retire there’s no doubt I’ll continue doing that. Keep in mind that there’s a middle ground, namely using Swift to call the frameworks you already know. If you get pleasure from shipping stuff, that might be a good first step, rather than wrestling with Swift and SwiftUI at the same time. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myE

Can you try running on the simulator instead of on a real device? If you are starting new: Learn swift (https://docs.swift.org/swift-book/documentation/the-swift-programming-language/) Learning iOS development (https://cs193p.stanford.edu) - Use this as a guidance, then once you are comfortable with the basics then refer to Apple documentation / WWDC videos Learn SwiftUI (WWDC videos are pretty good)

Last year, at age 73, I decided to switch my hobby programming to Swift/SwiftUI from XOJO. I waited for SwiftUI to mature as UIKit made my eyes glaze over. After about 6 months of grinding, I successfully converted one of my XOJO apps. I now know there's a few things I did sub-optimally, so I'm continuing to learn. Jump in, the water's fine.

@ChrisDE Questions Should CarDetailViewModel be created in CarDetailView? Or should CarDetailViewModel be created in ContentView and passed to CarDetailView? Code ContentView struct ContentView: View { @State private var selectedCarID: UUID? var body: some View { NavigationSplitView { CarListView(selectedCarID: $selectedCarID) } detail: { if let selectedCarID { CarDetailView(carID: selectedCarID) } } } } CarListViewModel @Observable class CarListViewModel { let cars = [ Car(id: UUID(), name: aaa), Car(id: UUID(), name: bbb) ] } CarListView import SwiftUI struct CarListView: View { @Binding var selectedCarID: UUID? @State var model = CarListViewModel() var body: some View { List(model.cars, selection: $selectedCarID) { car in VStack(alignment: .leading) { Text(car.name) Text((car.id)) } } } } CarDetailViewModel @Observable class CarDetailViewModel { let carID: UUID init(carID: UUID) { self.carID = carID } } CarDetailView import SwiftUI struct CarDetailView: View { @State private var model: Ca