Post

Replies

Boosts

Views

Activity

Reply to Bug: Xcode 26.2 wants `ENABLE_DEBUG_DYLIB`: How do I enable that in `Package.swift`?
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?
3w
Reply to how to mount a network share in Swift
Mapping to an SMB file share is something I'm working on now. I understand from other threads that instead of specifying a mount path of "/Volumes/mountdir", which for some reason is not allowed, you can use "/../Volumes/mountdir" which is both not the same (it is allowed) and the same..(it does what you wanted to do originally)
Topic: App & System Services SubTopic: Core OS Tags:
Jun ’26
Reply to Importing Data into SwiftData in the Background Using ModelActor and @Query
As of Xcode 16.3 beta 2, this issue is still not resolved. Additionally, updating the id (however that is achieved), as per the workaround in this thread, no longer triggers the Query to refresh;- I just added a button to the form that updates the id, and, after performing updates via a background modelActor, pushing the button did not trigger a refresh.
Topic: App & System Services SubTopic: iCloud Tags:
Mar ’25
Reply to Xcode 16 Beta: Animatable + non isolated protocol requirement errors.
Interestingly enough, you can get animatableData to work if you mark the computed variable as nonisolated. Xcode will fail at previewing the result, but a live run shows it working.. struct ContentView: View { static let bigAngle = 60.0 static let smallAngle = 10.0 @State var angle = Self.bigAngle var body: some View { MyShape(angle: angle) .foregroundStyle(.tint) .frame(width: 300, height: 200) .animation(.smooth(duration: 1.0), value: angle) .onTapGesture { angle = angle == Self.bigAngle ? Self.smallAngle : Self.bigAngle } } } struct MyShape: Shape { init(angle: Double) { self.angle = angle } var angle: Double nonisolated var animatableData: Double { get {angle} set {angle = newValue } } func path(in rect: CGRect) -> Path { Path { path in path.move(to: CGPoint(x: 0, y: 0)) // top left path.addLine(to: CGPoint(x: max(0,rect.width - rect.height*tan(angle * .pi/180)), y: 0)) // top right (or top left if the angle is large enough) path.addLine(to: CGPoint(x: rect.width, y: rect.height)) //bottom right path.addLine(to: CGPoint(x: 0, y: rect.height)) // bottom left path.closeSubpath() // Close (back to top left) } } }
Topic: UI Frameworks SubTopic: SwiftUI Tags:
Jul ’24
Reply to Bug: Xcode 26.2 wants `ENABLE_DEBUG_DYLIB`: How do I enable that in `Package.swift`?
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?
Replies
Boosts
Views
Activity
3w
Reply to how to mount a network share in Swift
Mapping to an SMB file share is something I'm working on now. I understand from other threads that instead of specifying a mount path of "/Volumes/mountdir", which for some reason is not allowed, you can use "/../Volumes/mountdir" which is both not the same (it is allowed) and the same..(it does what you wanted to do originally)
Topic: App & System Services SubTopic: Core OS Tags:
Replies
Boosts
Views
Activity
Jun ’26
Reply to Importing Data into SwiftData in the Background Using ModelActor and @Query
As of Xcode 16.3 beta 2, this issue is still not resolved. Additionally, updating the id (however that is achieved), as per the workaround in this thread, no longer triggers the Query to refresh;- I just added a button to the form that updates the id, and, after performing updates via a background modelActor, pushing the button did not trigger a refresh.
Topic: App & System Services SubTopic: iCloud Tags:
Replies
Boosts
Views
Activity
Mar ’25
Reply to Xcode 16 Beta: Animatable + non isolated protocol requirement errors.
Interestingly enough, you can get animatableData to work if you mark the computed variable as nonisolated. Xcode will fail at previewing the result, but a live run shows it working.. struct ContentView: View { static let bigAngle = 60.0 static let smallAngle = 10.0 @State var angle = Self.bigAngle var body: some View { MyShape(angle: angle) .foregroundStyle(.tint) .frame(width: 300, height: 200) .animation(.smooth(duration: 1.0), value: angle) .onTapGesture { angle = angle == Self.bigAngle ? Self.smallAngle : Self.bigAngle } } } struct MyShape: Shape { init(angle: Double) { self.angle = angle } var angle: Double nonisolated var animatableData: Double { get {angle} set {angle = newValue } } func path(in rect: CGRect) -> Path { Path { path in path.move(to: CGPoint(x: 0, y: 0)) // top left path.addLine(to: CGPoint(x: max(0,rect.width - rect.height*tan(angle * .pi/180)), y: 0)) // top right (or top left if the angle is large enough) path.addLine(to: CGPoint(x: rect.width, y: rect.height)) //bottom right path.addLine(to: CGPoint(x: 0, y: rect.height)) // bottom left path.closeSubpath() // Close (back to top left) } } }
Topic: UI Frameworks SubTopic: SwiftUI Tags:
Replies
Boosts
Views
Activity
Jul ’24
Reply to Xcode 16 Beta: Animatable + non isolated protocol requirement errors.
ideally the protocols would be updated and restricted to main actor, but I don’t hold out much hope for that based on other threads I have read.
Topic: UI Frameworks SubTopic: SwiftUI Tags:
Replies
Boosts
Views
Activity
Jul ’24