FullScreenCover causes linker crash and app won't start on macOS 10.15

[nrudnyk]

Description

When i try to use SwiftUINavigation, linker fails with the following message on macOS 10.15

Application Specific Information:
dyld: launch, loading dependent libraries

Dyld Error Message:
  Symbol not found: _$s7SwiftUI4ViewPAAE15fullScreenCover11isPresented9onDismiss7contentQrAA7BindingVySbG_yycSgqd__yctAaBRd__lFQOMQ
  Referenced from: /Applications/Ubiquity.app/Contents/MacOS/Ubiquity
  Expected in: /System/Library/Frameworks/SwiftUI.framework/Versions/A/SwiftUI
 in /Applications/Ubiquity.app/Contents/MacOS/Ubiquity

looks that the @available(macOS, unavailable) doesn't work in FullScreenCover.swift or I'm not sure while linker tries to load mentioned symbol.

If there's some suggestion on what could i do - please let me know.

As a side note, I was having issues with trying to run TCA and SwiftUI-navigation on macOS 10.15 system with debugging purposes. That is due to required swift-tools version 5.6 required, but macOS 10.15 only supports XCode 12.4, which has swift-tools of version 5.3. Maybe you can suggest how to overcome this one as well. Thanks!

Checklist

• I have determined whether this bug is also reproducible in a vanilla SwiftUI project.
• If possible, I've reproduced the issue using the main branch of this package.
• This issue hasn't been addressed in an existing GitHub issue or discussion.

Expected behavior

app runs without a crash

Actual behavior

crashes while linking, so the app won't even start

Steps to reproduce

• Create whatever simple application
• archieve it with macos10.15 support
• try to run ot on macOS 10.15
• crash while linking

SwiftUI Navigation version information

14ac251

Destination operating system

macOS 10.15

Xcode version information

Version 14.1 (14B47b)

Swift Compiler version information

swift-driver version: 1.62.15 Apple Swift version 5.7.1 (swiftlang-5.7.1.135.3 clang-1400.0.29.51)
Target: x86_64-apple-macosx13.0

[mbrandonw]

Hi @nrudnyk, I just started a fresh project targeting macOS 10.15 and it seems to work just fine. Can you provide a minimal project that reproduces the problem?

Also I am not sure this is actually a problem with the library, so I am going to covert it to a discussion.

[nrudnyk]

Hello @mbrandonw, thanks for the prompt reply, and please accept my appologies for a delayed response.

Here is the sample project: TestProj.zip
It's not perfectly fine, i was shrinking down spotlike like overlay application.

But while it works perfectly fine on macOS 11+ it crashes on macOS 10.15. Here is the notarized dmg
TestAppInstaller.dmg.zip

So if I were to remove reference to remove the following:

var body: some View {
    Switch(viewStore.binding(\.$item.type)) {
        CaseLet(/Item.Kind.general) { $general in
            GeneralItemView(title: viewStore.item.name, type: "GENERAL")
        }
        CaseLet(/Item.Kind.firstType) { $first in
            GeneralItemView(title: viewStore.item.name, type: "FIRST")
        }
        CaseLet(/Item.Kind.secondType) { $second in
            GeneralItemView(title: viewStore.item.name, type: "SECOND")
        }
    }
}

and remove import SwiftUINavigation the app would run perfectly fine on macOS 10.15

Hope that this helps identify the root cause of the issue. If there's anything I can do to help - please let me know.

[nrudnyk]

@mbrandonw one more unrelated thing, is there any way to build and run TCA on macOS 10.15, which supports only XCode of version 12.4? While i can tell XCode to use latest swift compiler tools, i didn't figure out a way to replace swift-tool which is used by swift package manager...

The reason i faced this is that i wanted to debug some issues on macOS 10.15 directly on the target machine, but couldn't resolve all the TCA packages... If there's some wellknown approach - i would greatly appreciate if you point me to he right direction

[jaredh159]

@nrudnyk I'm seeing this same crash (opened a discussion before i saw this thread). did you ever get this figured out?

[nrudnyk]

@jaredh159 just seen this.
Unfortunatelly haven't figured that out. Have you? Maybe those get fixed with the released version of the lib?

[jaredh159]

yeah, solved it with this PR: pointfreeco/swift-composable-architecture#2385