Search results for

“swiftui”

17,353 results found

Post

Replies

Boosts

Views

Activity

Reply to How to send a message from menu item in SwiftUI App to ContentView
Views in SwiftUI are different from AppKit and UIKit in terms that they are value types, and you think about them differently. One way to implement the scenario is this: @main struct MyApp: App { @State private var displayImporter = false var body: some Scene { WindowGroup { ContentView() } .commands { CommandGroup(after:.newItem) { Button(Import…) { displayImporter = true } .fileImporter(isPresented: $displayImporter, allowedContentTypes: [/**/]) { result in /// } } } } }
Topic: UI Frameworks SubTopic: SwiftUI
3d
Reply to SwiftUI on macOS equivalent of NSSavePanel for choosing a destination URL?
It is possible to write databases with SwiftUI. The API you want to use is the one you mentioned in the original post: https://developer.apple.com/documentation/swiftui/view/fileexporter(ispresented:document:contenttype:defaultfilename:oncompletion:oncancellation:) Here's the document implementation that allows to write directly to the URL: final class MyDocument: WritableDocument { static let writableContentTypes: [UTType] = [.database] // or better, declare a custom UTType for your document type private var info: MyDatabaseInfo func writer(configuration: sending WriteConfiguration) -> sending MyWriter { MyWriter() } @MainActor func snapshot(contentType: UTType) async throws -> sending MyDatabaseInfo { info } } struct MyDatabaseInfo { } struct MyWriter: DocumentWriter { @concurrent func write( snapshot: sending MyDatabaseInfo, to destination: sending URL, previous: sending MyDatabaseInfo?, progress: consuming Subprogress ) async throws { // write the database to destination } }
Topic: UI Frameworks SubTopic: SwiftUI Tags:
3d
Using `containerRelativeFrame` in a `List` on macOS leads to crash
The following code crashes as soon as the app launches. struct ContentView: View { var body: some View { List { Rectangle() .fill(.red) .containerRelativeFrame([.horizontal, .vertical]) } .frame(width: 400, height: 800) } } I would expect the code not to crash. Note that using a ScrollView works perfectly fine: struct ContentView: View { var body: some View { ScrollView { Rectangle() .fill(.red) .containerRelativeFrame([.horizontal, .vertical]) } .frame(width: 400, height: 800) } } The documentation clearly stipulates that it should work with a list: A scrollable view like ScrollView or List Using Xcode 26.5 (17F42) and simply created a new macOS project using SwiftUI. Feedback FB23655564
1
0
58
3d
Reply to Need help with Python to apple translation, and iPad editing/runing
Apple doesn’t have any tools that can help with that. Our primary focus is Swift and SwiftUI, and for that we have the Swift Playground app. There are third-party Python IDEs available no the App Store, but I don’t have enough direct experience with them to offer a concrete recommendation. The other option is use a web-based IDE, which often work surprisingly well in Safari on the iPad [1]. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com [1] I once occupied myself during a long train ride by learning StandardML courtesy using a saved web app (-:
Topic: Programming Languages SubTopic: General Tags:
3d
Reply to How to send a message from menu item in SwiftUI App to ContentView
Problème comes from, not from command. @State public var contentView = ContentView() I have tested this very simple code to show: struct ContentView: View { public func importTerms() { print((showFileImporter)) showFileImporter = true print((showFileImporter)) } var body: some View { Button(Test) { importTerms() } } } struct ContentView2: View { @State private var content = ContentView() var body: some View { Button(Test2) { content.importTerms() } } } If I call ContentView(), and tap Test, I get the correct result. false true But If I call ContentView2(), and tap Test2, I get the wrong result, var is not changed. false false My guess is that with this declaration of state var ContentView, you create 2 instances, and there is a confusion in the showFileImporter state var at system level. you update var for instance2 which is ignored by the system which uses instance1 (in print). Someone more expert in SwiftUI may provide more accurate explanation. You could use environment variables for showFileImpor
Topic: UI Frameworks SubTopic: SwiftUI
3d
Reply to Sandboxed Mac app denied mach-lookup com.apple.cloudd when signed with Mac Team Store Provisioning Profile on macOS 26
Seeing the same deny(1) mach-lookup com.apple.cloudd on a sandboxed Mac app (SwiftUI, CloudKit via the standard com.apple.developer.icloud-services/icloud-container-identifiers entitlements, not SwiftData). Environment: macOS 26.5.1, Xcode 26.5 — same as OP. What I've confirmed so far: codesign -d --entitlements - on the App Store–downloaded binary shows correct entitlements: icloud-container-identifiers, icloud-services: [CloudKit], icloud-container-environment: Production, matching App ID/container config in the Developer Portal. App ID in the portal has iCloud capability enabled with the correct container assigned (1 of 1 selected) — ruled out a portal-side misconfiguration. Reproduced independently on a second Mac (different machine, App Store install) with the same deny. One difference from the OP's report: in my case, a local Release-scheme build run via Xcode also gets denied, while the Debug-scheme build works fine. So the discriminator for me looks like Debug vs. Release configuration, not s
Topic: App & System Services SubTopic: iCloud Tags:
3d
How to send a message from menu item in SwiftUI App to ContentView
I'm just not getting it. My app adds a custom Import menu item to the File menu. I want to have it tell the sole ContentView to run the fileImporter. Here's how I have it set up. Changing the showFileImporter variable to supposed to make stuff happen, but it doesn't change. @main struct Blah: App { @State public var contentView = ContentView(); var body:some Scene { WindowGroup { // ContentView() // It started out defining the content like normal, but I saw somewhere that if I declared it as a var up top, then I'd have an actual object that I could tell to do things, like calling the importTerms() method below. self.contentView } .commands { CommandGroup(after:.newItem) { Button(Import…) { contentView.importTerms(); } } } } struct ContentView: View { @State private var showFileImporter = false; var body: some View { VStack { ...stuff... } } .fileImporter(isPresented:$showFileImporter, allowedContentTypes:[.text], allowsMultipleSelection:false) { result in } public func importTerms() { print((showFileImporter)
Topic: UI Frameworks SubTopic: SwiftUI
13
0
137
3d
SwiftUI confirmationDialog in List inside .sheet is no longer anchored to the originating row on iOS 27 beta
Area SwiftUI → Presentation / ConfirmationDialog Summary After building with Xcode 27 beta, confirmationDialog presented from a row inside a List that is embedded in a .sheet is no longer anchored to the row that triggered it. Instead, the dialog is displayed near the top of the sheet when the sheet is partially expanded, or in the center of the screen when the sheet occupies the full height. This behavior is reproducible across all tested Xcode 27 beta releases and iOS 27 beta releases (Beta 1, Beta 2, and Beta 3). Steps to Reproduce Present a SwiftUI .sheet. Place a List inside the sheet. Add a confirmationDialog to each list row. Trigger the dialog from a swipe action on any row. Observe the position where the confirmation dialog appears. A minimal reproducible sample project is attached. Expected Result The confirmationDialog should be visually associated with the row that triggered it, as it behaved in previous Xcode and iOS releases. The dialog should appear anchored to the selected li
0
0
58
3d
SwiftUI confirmationDialog in List inside .sheet is no longer anchored to the originating row on iOS 27 beta
Area SwiftUI → Presentation / ConfirmationDialog Summary After building with Xcode 27 beta, confirmationDialog presented from a row inside a List that is embedded in a .sheet is no longer anchored to the row that triggered it. Instead, the dialog is displayed near the top of the sheet when the sheet is partially expanded, or in the center of the screen when the sheet occupies the full height. This behavior is reproducible across all tested Xcode 27 beta releases and iOS 27 beta releases (Beta 1, Beta 2, and Beta 3). Steps to Reproduce Present a SwiftUI .sheet. Place a List inside the sheet. Add a confirmationDialog to each list row. Trigger the dialog from a swipe action on any row. Observe the position where the confirmation dialog appears. A minimal reproducible sample project is attached. Expected Result The confirmationDialog should be visually associated with the row that triggered it, as it behaved in previous Xcode and iOS releases. The dialog should appear anchored to the selected li
0
0
37
3d
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(
Topic: UI Frameworks SubTopic: SwiftUI
1
0
51
4d
Sign in with Apple Failure, AKAuthenticationServerError=-24000
Apple Developer Support Request - Sign in with Apple Failure Date prepared: 2026-07-08 App name: LingJing / XiaoLing Bundle ID: com.jachymchen.xiaoling Apple Developer Team ID: 765B64SW9Z Platform: iOS Summary Sign in with Apple fails before the app receives a usable Apple identity token. The user-facing Apple system sheet ends with the Chinese alert 未完成注册 (Sign Up Not Completed). The app callback does not receive an identityToken, so our backend auth provider is not reached successfully. We reproduced the same failure in a minimal native Swift app that only uses AuthenticationServices and the same Bundle ID / provisioning profile, without Supabase or any app-specific backend code. This suggests the failure is likely in the Apple Sign in with Apple authorization flow, account/device state, or App ID/provisioning configuration recognized by Apple's auth services, rather than in our app's backend implementation. Environment Mac: macOS 26.5 Apple Silicon MacBook Pro Xcode 26.5 iPhone: Real device connected over
0
0
43
4d
Reply to Did VisionOS27 get the LazyVGrid Performance Updates?
Okay. Hours of commenting out swiftUI modifiers one at a time and A/B testing a bunch of nonsense leads me to the following: Treating the lazyVGrid cell content as the label of a button, OR applying a .hoverEffect to the same content, opting not to wrap it in a button, will degrade scroll performance on VisionOS. ScrollView will hitch as new rows come into view and may appear to vibrate as scrolled. These are symptoms I've seen in Apple's own apps, like Files, as well, so maybe it's more systemic. If that's not fixed but the end of the summer, I'll probably swap back to my UIKit implementation :
Topic: UI Frameworks SubTopic: SwiftUI Tags:
4d
Reply to Bug: Xcode 26.2 wants `ENABLE_DEBUG_DYLIB`: How do I enable that in `Package.swift`?
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.
4d
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?
4d
Reply to How to send a message from menu item in SwiftUI App to ContentView
That crossed my mind as well, but again, it feels icky to put the code in the app when only the ContentView should be muddied up with it. I'll do that and move on. It's too bad this SwiftUI stuff isn't friendlier. Thanks.
Topic: UI Frameworks SubTopic: SwiftUI
Replies
Boosts
Views
Activity
3d
Reply to How to send a message from menu item in SwiftUI App to ContentView
Views in SwiftUI are different from AppKit and UIKit in terms that they are value types, and you think about them differently. One way to implement the scenario is this: @main struct MyApp: App { @State private var displayImporter = false var body: some Scene { WindowGroup { ContentView() } .commands { CommandGroup(after:.newItem) { Button(Import…) { displayImporter = true } .fileImporter(isPresented: $displayImporter, allowedContentTypes: [/**/]) { result in /// } } } } }
Topic: UI Frameworks SubTopic: SwiftUI
Replies
Boosts
Views
Activity
3d
Reply to SwiftUI on macOS equivalent of NSSavePanel for choosing a destination URL?
It is possible to write databases with SwiftUI. The API you want to use is the one you mentioned in the original post: https://developer.apple.com/documentation/swiftui/view/fileexporter(ispresented:document:contenttype:defaultfilename:oncompletion:oncancellation:) Here's the document implementation that allows to write directly to the URL: final class MyDocument: WritableDocument { static let writableContentTypes: [UTType] = [.database] // or better, declare a custom UTType for your document type private var info: MyDatabaseInfo func writer(configuration: sending WriteConfiguration) -> sending MyWriter { MyWriter() } @MainActor func snapshot(contentType: UTType) async throws -> sending MyDatabaseInfo { info } } struct MyDatabaseInfo { } struct MyWriter: DocumentWriter { @concurrent func write( snapshot: sending MyDatabaseInfo, to destination: sending URL, previous: sending MyDatabaseInfo?, progress: consuming Subprogress ) async throws { // write the database to destination } }
Topic: UI Frameworks SubTopic: SwiftUI Tags:
Replies
Boosts
Views
Activity
3d
Using `containerRelativeFrame` in a `List` on macOS leads to crash
The following code crashes as soon as the app launches. struct ContentView: View { var body: some View { List { Rectangle() .fill(.red) .containerRelativeFrame([.horizontal, .vertical]) } .frame(width: 400, height: 800) } } I would expect the code not to crash. Note that using a ScrollView works perfectly fine: struct ContentView: View { var body: some View { ScrollView { Rectangle() .fill(.red) .containerRelativeFrame([.horizontal, .vertical]) } .frame(width: 400, height: 800) } } The documentation clearly stipulates that it should work with a list: A scrollable view like ScrollView or List Using Xcode 26.5 (17F42) and simply created a new macOS project using SwiftUI. Feedback FB23655564
Replies
1
Boosts
0
Views
58
Activity
3d
Reply to Need help with Python to apple translation, and iPad editing/runing
Apple doesn’t have any tools that can help with that. Our primary focus is Swift and SwiftUI, and for that we have the Swift Playground app. There are third-party Python IDEs available no the App Store, but I don’t have enough direct experience with them to offer a concrete recommendation. The other option is use a web-based IDE, which often work surprisingly well in Safari on the iPad [1]. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com [1] I once occupied myself during a long train ride by learning StandardML courtesy using a saved web app (-:
Topic: Programming Languages SubTopic: General Tags:
Replies
Boosts
Views
Activity
3d
Reply to How to send a message from menu item in SwiftUI App to ContentView
Problème comes from, not from command. @State public var contentView = ContentView() I have tested this very simple code to show: struct ContentView: View { public func importTerms() { print((showFileImporter)) showFileImporter = true print((showFileImporter)) } var body: some View { Button(Test) { importTerms() } } } struct ContentView2: View { @State private var content = ContentView() var body: some View { Button(Test2) { content.importTerms() } } } If I call ContentView(), and tap Test, I get the correct result. false true But If I call ContentView2(), and tap Test2, I get the wrong result, var is not changed. false false My guess is that with this declaration of state var ContentView, you create 2 instances, and there is a confusion in the showFileImporter state var at system level. you update var for instance2 which is ignored by the system which uses instance1 (in print). Someone more expert in SwiftUI may provide more accurate explanation. You could use environment variables for showFileImpor
Topic: UI Frameworks SubTopic: SwiftUI
Replies
Boosts
Views
Activity
3d
Reply to Sandboxed Mac app denied mach-lookup com.apple.cloudd when signed with Mac Team Store Provisioning Profile on macOS 26
Seeing the same deny(1) mach-lookup com.apple.cloudd on a sandboxed Mac app (SwiftUI, CloudKit via the standard com.apple.developer.icloud-services/icloud-container-identifiers entitlements, not SwiftData). Environment: macOS 26.5.1, Xcode 26.5 — same as OP. What I've confirmed so far: codesign -d --entitlements - on the App Store–downloaded binary shows correct entitlements: icloud-container-identifiers, icloud-services: [CloudKit], icloud-container-environment: Production, matching App ID/container config in the Developer Portal. App ID in the portal has iCloud capability enabled with the correct container assigned (1 of 1 selected) — ruled out a portal-side misconfiguration. Reproduced independently on a second Mac (different machine, App Store install) with the same deny. One difference from the OP's report: in my case, a local Release-scheme build run via Xcode also gets denied, while the Debug-scheme build works fine. So the discriminator for me looks like Debug vs. Release configuration, not s
Topic: App & System Services SubTopic: iCloud Tags:
Replies
Boosts
Views
Activity
3d
How to send a message from menu item in SwiftUI App to ContentView
I'm just not getting it. My app adds a custom Import menu item to the File menu. I want to have it tell the sole ContentView to run the fileImporter. Here's how I have it set up. Changing the showFileImporter variable to supposed to make stuff happen, but it doesn't change. @main struct Blah: App { @State public var contentView = ContentView(); var body:some Scene { WindowGroup { // ContentView() // It started out defining the content like normal, but I saw somewhere that if I declared it as a var up top, then I'd have an actual object that I could tell to do things, like calling the importTerms() method below. self.contentView } .commands { CommandGroup(after:.newItem) { Button(Import…) { contentView.importTerms(); } } } } struct ContentView: View { @State private var showFileImporter = false; var body: some View { VStack { ...stuff... } } .fileImporter(isPresented:$showFileImporter, allowedContentTypes:[.text], allowsMultipleSelection:false) { result in } public func importTerms() { print((showFileImporter)
Topic: UI Frameworks SubTopic: SwiftUI
Replies
13
Boosts
0
Views
137
Activity
3d
SwiftUI confirmationDialog in List inside .sheet is no longer anchored to the originating row on iOS 27 beta
Area SwiftUI → Presentation / ConfirmationDialog Summary After building with Xcode 27 beta, confirmationDialog presented from a row inside a List that is embedded in a .sheet is no longer anchored to the row that triggered it. Instead, the dialog is displayed near the top of the sheet when the sheet is partially expanded, or in the center of the screen when the sheet occupies the full height. This behavior is reproducible across all tested Xcode 27 beta releases and iOS 27 beta releases (Beta 1, Beta 2, and Beta 3). Steps to Reproduce Present a SwiftUI .sheet. Place a List inside the sheet. Add a confirmationDialog to each list row. Trigger the dialog from a swipe action on any row. Observe the position where the confirmation dialog appears. A minimal reproducible sample project is attached. Expected Result The confirmationDialog should be visually associated with the row that triggered it, as it behaved in previous Xcode and iOS releases. The dialog should appear anchored to the selected li
Replies
0
Boosts
0
Views
58
Activity
3d
SwiftUI confirmationDialog in List inside .sheet is no longer anchored to the originating row on iOS 27 beta
Area SwiftUI → Presentation / ConfirmationDialog Summary After building with Xcode 27 beta, confirmationDialog presented from a row inside a List that is embedded in a .sheet is no longer anchored to the row that triggered it. Instead, the dialog is displayed near the top of the sheet when the sheet is partially expanded, or in the center of the screen when the sheet occupies the full height. This behavior is reproducible across all tested Xcode 27 beta releases and iOS 27 beta releases (Beta 1, Beta 2, and Beta 3). Steps to Reproduce Present a SwiftUI .sheet. Place a List inside the sheet. Add a confirmationDialog to each list row. Trigger the dialog from a swipe action on any row. Observe the position where the confirmation dialog appears. A minimal reproducible sample project is attached. Expected Result The confirmationDialog should be visually associated with the row that triggered it, as it behaved in previous Xcode and iOS releases. The dialog should appear anchored to the selected li
Replies
0
Boosts
0
Views
37
Activity
3d
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(
Topic: UI Frameworks SubTopic: SwiftUI
Replies
1
Boosts
0
Views
51
Activity
4d
Sign in with Apple Failure, AKAuthenticationServerError=-24000
Apple Developer Support Request - Sign in with Apple Failure Date prepared: 2026-07-08 App name: LingJing / XiaoLing Bundle ID: com.jachymchen.xiaoling Apple Developer Team ID: 765B64SW9Z Platform: iOS Summary Sign in with Apple fails before the app receives a usable Apple identity token. The user-facing Apple system sheet ends with the Chinese alert 未完成注册 (Sign Up Not Completed). The app callback does not receive an identityToken, so our backend auth provider is not reached successfully. We reproduced the same failure in a minimal native Swift app that only uses AuthenticationServices and the same Bundle ID / provisioning profile, without Supabase or any app-specific backend code. This suggests the failure is likely in the Apple Sign in with Apple authorization flow, account/device state, or App ID/provisioning configuration recognized by Apple's auth services, rather than in our app's backend implementation. Environment Mac: macOS 26.5 Apple Silicon MacBook Pro Xcode 26.5 iPhone: Real device connected over
Replies
0
Boosts
0
Views
43
Activity
4d
Reply to Did VisionOS27 get the LazyVGrid Performance Updates?
Okay. Hours of commenting out swiftUI modifiers one at a time and A/B testing a bunch of nonsense leads me to the following: Treating the lazyVGrid cell content as the label of a button, OR applying a .hoverEffect to the same content, opting not to wrap it in a button, will degrade scroll performance on VisionOS. ScrollView will hitch as new rows come into view and may appear to vibrate as scrolled. These are symptoms I've seen in Apple's own apps, like Files, as well, so maybe it's more systemic. If that's not fixed but the end of the summer, I'll probably swap back to my UIKit implementation :
Topic: UI Frameworks SubTopic: SwiftUI Tags:
Replies
Boosts
Views
Activity
4d
Reply to Bug: Xcode 26.2 wants `ENABLE_DEBUG_DYLIB`: How do I enable that in `Package.swift`?
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.
Replies
Boosts
Views
Activity
4d
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
4d