Is this lib missing a dependency on CombineSchedulers?

[ryanmeisters]

Description

Howdy! We have a large project with tons of modules. When updating to TCA 1.17.0 I'm getting these linking errors when xcode tries to link Sharing:

Showing All Messages
Undefined symbol: CombineSchedulers.AnyScheduler.now.getter : A

Undefined symbol: static (extension in CombineSchedulers):CombineSchedulers.AnyScheduler< where A == (extension in Dispatch):__C.OS_dispatch_queue.SchedulerTimeType, B == (extension in Dispatch):__C.OS_dispatch_queue.SchedulerOptions>.immediate.getter : CombineSchedulers.AnyScheduler<(extension in Dispatch):__C.OS_dispatch_queue.SchedulerTimeType, (extension in Dispatch):__C.OS_dispatch_queue.SchedulerOptions>

Undefined symbol: type metadata accessor for CombineSchedulers.AnyScheduler

Undefined symbol: nominal type descriptor for CombineSchedulers.AnyScheduler

Undefined symbol: protocol conformance descriptor for CombineSchedulers.AnyScheduler<A, B> : Combine.Scheduler in CombineSchedulers

Linker command failed with exit code 1 (use -v to see invocation)

I'm wondering if Sharing is missing a dependency on CombineSchedulers, e.g. this code here looks like .immediate comes from there?

Our project is complex so this could be a me problem, but wanted to make sure i'm not crazy.

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

No response

Actual behavior

No response

Reproducing project

No response

Sharing version information

No response

Destination operating system

No response

Xcode version information

No response

Swift Compiler version information

No response

[stephencelis]

@ryanmeisters swift-sharing depends on swift-dependencies, which depends on combine-schedulers, so I don't think this is the problem you are seeing. I'm going to convert to a discussion till we can determine this is a bug in the library. Can you share a repro so we can see if this is something to do with your project vs. our library?

[bedrock-drivet-externe]

For reference, here's the compilation error site.

[bedrock-drivet-externe]

After a lot of searching on the interwebs, I tried a few solution but unfortunately, none of them worked so far.

https://forums.swift.org/t/how-to-import-macros-using-methods-other-than-swiftpm/66645/40
pointfreeco/swift-composable-architecture#3419
pointfreeco/swift-composable-architecture#2639
https://stackoverflow.com/questions/77386744/swift-macros-external-macro-implementation-type-could-not-be-found

[mbrandonw]

Hi @bedrock-drivet-externe, are you able to provide a project that demonstrates the problem you are having?

[mbrandonw]

@bedrock-drivet-externe: I believe this will also fix the macro errors you are seeing: pointfreeco/swift-navigation#256

[bedrock-drivet-externe]

@mbrandonw pointfreeco/swift-navigation#256 did fix the build issue with the @Perceptible macro. Thanks a lot for the investigation and the fixes on both swift-sharing and swift-navigation.

Interestingly, I did some testing with Tuist to see how it would integrate the same project architecture and the only time it "worked" was by making the FeatureA framework a static framework with MACH_O_TYPE set to Static library so it matches your statement about Xcode 16.1+ changing something about dynamic framework.

When can we expect those fixes to be fully released? I imagine that there will be some internal testing before they go live.