same for me EXC_CORPSE_NOTIFY Application Specific Information: ProductBuildVersion: 12E262 ASSERTION FAILURE in /Library/Caches/com.apple.xbs/Sources/DVTFrameworks/DVTFrameworks-18168/DVTITunesSoftwareServiceFoundation/App Loader/Wrappers/DVTITunesConnectApplicationVersionDescription.m:70 Details: (y) should not be nil. Object: DVTITunesConnectApplicationVersionDescription: 0x7fb2b6570340 Method: -initWithCoder: Thread: NSThread: 0x7fb3225777a0{number = 27, name = (null)} Open FDs: 55/7168 Hints: Backtrace: 0 -[IDEAssertionHandler handleFailureInMethod:object:fileName:lineNumber:assertionSignature:messageFormat:arguments:] (in IDEKit) 1 _DVTAssertionHandler (in DVTFoundation)

I do use 16.0.1 downloaded inside IntelliJ.

it seems working in Xcode 12.5 but we do have a WORSE case. Suppose You need to write something like that: struct InfoSheetView: View {     if #available(iOS 15, *) {     } else {     } var body: some View { ..... } } even if an EMPTY if # I got: Expected declaration on if #.. I would like to write ..     if #available(iOS 15, *) { @Environment(\.dismiss) var dismiss     } else {     @Environment(\.presentationMode) var presentationMode     } see original example at: https://www.hackingwithswift.com/quick-start/swiftui/how-to-present-a-new-view-using-sheets and try to conditionally use @Environment(\.dismiss) var dismiss OR     @Environment(.presentationMode) var presentationMode

hello, processors AND chips are different so no way to do it. bootcamp relied on using same Intel chips, so some sort of HW virtualixzation was in place.

bootcamp does rely on Intel x64 binary instructions, and some sort of HW virtualisation, no way to run directly.

saame for me both on Monterrey (Xcode 13) AND Ventura (Xcode 14 beta)

a real, working example with a nice implementation is here: https://swiftuirecipes.com/blog/swiftui-scrollview-scroll-offset

same for me, and more stranger in Xcode 15 beta warning disappears... :(

fixed downloading xccode Version 15.0 beta 5 (15A5209g). God bless us! BUT... no tTest flight!! Unsupported Xcode or SDK Version. Your app was built with a version of Xcode or SDK that is not yet supported for upload to App Store Connect. For more information about supported versions of Xcode and SDK for Testflight or App Store submissions, view the App Store Connect What's New page (https://developer.apple.com/app-store-connect/whats-new/). (ID: a1433239-95a6-42db-88d9-c3bc0365679f)

same for me, until Xcode beta 4 I could, but binaries crash on iOS 17 beta of yesterday. (opened another thread)

with very low stress, You can easy install directly with cable or wifi... or using Ad Hoc distributions (but require to register devices, create and "ad Hoc" profile, build IPA with those settings, and send them...

// MARK: Refreshable - Modifier for Refreshable based on OS: **(note: inline code does NOT work... is not my fault...) ** // accesory: public func isCatalyst()->Bool { //tolerate warnings! #if targetEnvironment(macCatalyst) return true #endif return false } public typealias RefreshAction = ()->() private struct MyRefreshableModifier: ViewModifier { internal init(action: @escaping RefreshAction) { self.action = action } private let action: RefreshAction public func body(content: Content) -> some View { #if os(iOS) // Catalyst IS under iOS: if isCatalyst(){ content }else{ content .refreshable { action() } } #elseif os(macOS) content // nada. We throw away #endif } } public extension View { func portableRefreshableModifier(action: @escaping RefreshAction) -> some View { modifier(MyRefreshableModifier(action: action) ) } } // usage: /* List { Text("Hello World") Text("Hello World") Text("Hello World") }.refreshable { print("refresh....") } will be: List { Text("Hello World") Text("Hello World") Text("Hello World") }.portableRefreshableModifier { print("refresh....") } */

seee HERE to see better.. https://stackoverflow.com/questions/67616459/catalyst-app-crashes-when-using-wheelpickerstyle/77166542#77166542

I succeded in terminal issuing: xcodebuild -downloadAllPlatforms DONT know HOW, but it reset something :(

same for me in XCTest. If I add Host Application, AND Allow testing Host Application APIs tests build correctly. any other combinations, fails.