Hi,
I've tried your method, but it appears that while exporting localization using that destination (and removing -sdk), it is trying to build also for macOS.
If I leave -sdk while adding -destination it starts to compile only for iOS, but the "cannot find external macro" error returns.
Maybe the root cause is the same that prevents me to use Xcode itself (not xcodebuild) for exporting localization. While exporting localization from Xcode, if I'm using a package Xcode will try to export the localization both using iOS and macOS sdk (with destination null)
Maybe when using the destination flag (instead of the sdk) the localization export tries to compile for both iOS and macOS (Which of course cannot compile due to the fact I'm using iOS only apis)
Playrom
Users receive reputation points by contributing quality content to the forums.
Posts include post and replies published on the forums.
Post authors can mark replies as Accepted to indicate successful solutions.
Apple Developer Forums admins can mark replies as Apple Recommended to indicate an approved solution
Last seen
User for
From
Messina, Province of Messina, Italy
Post
Replies
Boosts
Views
Activity
I've opened a TSI, the developer relations confirmed that it should be a bug in SwiftUI, but I've not been told workarounds or hope for a fix
Issue still present on Xcode15 beta 7, and honestly this prevents the creations of connected chains of swiftui packages, to modularize your UI code...
I can confirm, having the same bug, with a very simple form
		Form {
				 Section {
						DatePicker(self.label, selection: self.value)
				 }
		}
2020-11-29 21:11:08.171127+0100 Budgetify[85909:3309604] [Warning] Warning once only: Detected a case where constraints ambiguously suggest a height of zero for a table view cell's content view. We're considering the collapse unintentional and using standard height instead. Cell: <SwiftUI.ListCoreCellHost: 0x7ffdbc08f800; baseClass = UITableViewCell; frame = (0 123; 788 44); autoresize = W; layer = <CALayer: 0x60000223b960>>