Post

Replies

Boosts

Views

Activity

Reply to SwiftUI Previews in Xcode 14 failed to run with SettingsError: noExecutablePath(IDESwiftPackageStaticLibraryProductBuildable)
I followed Microsoft's approach with my own libraries and removed the library type(s) from the Package.swift file and the issue 'goes away'. Hopefully this reduces the bug reports coming in stating that my library has 'broken' SwiftUI. However, this is purely a workaround of the issue and not a solution. Some clients want to explicitly define their library usage and for them the Xcode bug persists. If this is somehow my problem (ie. I'm using SPM incorrectly) then it would be awesome to understand how to fix it (especially since Xcode 13 didn't have this issue).
Topic: UI Frameworks SubTopic: SwiftUI Tags:
Nov ’22
Reply to SwiftUI Previews in Xcode 14 failed to run with SettingsError: noExecutablePath(IDESwiftPackageStaticLibraryProductBuildable)
Linking against a .dynamic type library fixes the SwiftUI preview breaking (well, at least for me) both on iOS and macOS For example, linking against QRCodeDynamic (in my package.swift) :-  .library( name: "QRCodeStatic", type: .static, targets: ["QRCode"] ), .library( name: "QRCodeDynamic", type: .dynamic, targets: ["QRCode"] ) the SwiftUI previews start working correctly. Linking against a static library type always fails. At least this is a workaround if you're stuck. This also works if the type is not specified. .library( name: "QRCode", targets: ["QRCode"] ), But not a fix.
Topic: UI Frameworks SubTopic: SwiftUI Tags:
Sep ’22
Reply to SwiftUI Previews in Xcode 14 failed to run with SettingsError: noExecutablePath(IDESwiftPackageStaticLibraryProductBuildable)
I've been finding this with my own SPM packages, and reported by a number of users of that package. Filed bug FB11397938 back in August. SettingsError: noExecutablePath(<IDESwiftPackageStaticLibraryProductBuildable:ObjectIdentifier(0x000060000d2b3b70):'QRCode'>) Easily reproducible by adding a package to a blank SwiftUI project in Xcode 14. Cannot be reproduced in Xcode 13.
Topic: UI Frameworks SubTopic: SwiftUI Tags:
Sep ’22
Reply to Core Spotlight on macOS: Is thumbnailData used?
Seeing the same thing here on macOS 12 (even with recent Xcode betas). The thumbnail seems to be completely ignored. However, running the same application on macOS 13 beta (compiled with Xcode 14 beta 6) the custom thumbnail is appearing as expected (well, I've only tested for thumbnailData). Annoying as hell. So much wasted time.
Topic: App & System Services SubTopic: Core OS Tags:
Sep ’22
Reply to SwiftUI Previews in Xcode 14 failed to run with SettingsError: noExecutablePath(IDESwiftPackageStaticLibraryProductBuildable)
I followed Microsoft's approach with my own libraries and removed the library type(s) from the Package.swift file and the issue 'goes away'. Hopefully this reduces the bug reports coming in stating that my library has 'broken' SwiftUI. However, this is purely a workaround of the issue and not a solution. Some clients want to explicitly define their library usage and for them the Xcode bug persists. If this is somehow my problem (ie. I'm using SPM incorrectly) then it would be awesome to understand how to fix it (especially since Xcode 13 didn't have this issue).
Topic: UI Frameworks SubTopic: SwiftUI Tags:
Replies
Boosts
Views
Activity
Nov ’22
Reply to SwiftUI Previews in Xcode 14 failed to run with SettingsError: noExecutablePath(IDESwiftPackageStaticLibraryProductBuildable)
Unfortunately, this is still an issue for me with 14.1 beta 3 [Xcode Version 14.1 beta 3 (14B5033e)] HumanReadableSwiftError SettingsError: noExecutablePath(<IDESwiftPackageStaticLibraryProductBuildable:ObjectIdentifier(0x0000600032e3b4e0):'DSFToolbar'>) FB11513131 has been updated with a new preview report
Topic: UI Frameworks SubTopic: SwiftUI Tags:
Replies
Boosts
Views
Activity
Sep ’22
Reply to SwiftUI Previews in Xcode 14 failed to run with SettingsError: noExecutablePath(IDESwiftPackageStaticLibraryProductBuildable)
Linking against a .dynamic type library fixes the SwiftUI preview breaking (well, at least for me) both on iOS and macOS For example, linking against QRCodeDynamic (in my package.swift) :-  .library( name: "QRCodeStatic", type: .static, targets: ["QRCode"] ), .library( name: "QRCodeDynamic", type: .dynamic, targets: ["QRCode"] ) the SwiftUI previews start working correctly. Linking against a static library type always fails. At least this is a workaround if you're stuck. This also works if the type is not specified. .library( name: "QRCode", targets: ["QRCode"] ), But not a fix.
Topic: UI Frameworks SubTopic: SwiftUI Tags:
Replies
Boosts
Views
Activity
Sep ’22
Reply to SwiftUI Previews in Xcode 14 failed to run with SettingsError: noExecutablePath(IDESwiftPackageStaticLibraryProductBuildable)
I've been finding this with my own SPM packages, and reported by a number of users of that package. Filed bug FB11397938 back in August. SettingsError: noExecutablePath(<IDESwiftPackageStaticLibraryProductBuildable:ObjectIdentifier(0x000060000d2b3b70):'QRCode'>) Easily reproducible by adding a package to a blank SwiftUI project in Xcode 14. Cannot be reproduced in Xcode 13.
Topic: UI Frameworks SubTopic: SwiftUI Tags:
Replies
Boosts
Views
Activity
Sep ’22
Reply to Core Spotlight on macOS: Is thumbnailData used?
Seeing the same thing here on macOS 12 (even with recent Xcode betas). The thumbnail seems to be completely ignored. However, running the same application on macOS 13 beta (compiled with Xcode 14 beta 6) the custom thumbnail is appearing as expected (well, I've only tested for thumbnailData). Annoying as hell. So much wasted time.
Topic: App & System Services SubTopic: Core OS Tags:
Replies
Boosts
Views
Activity
Sep ’22