[SR-15154] ObjC projects using SPM fail when we expose our models into another module

[swift-ci]

Previous ID	SR-15154
Radar	rdar://problem/82827693
Original Reporter	taquitos (JIRA User)
Type	Bug

Attachment: Download

Additional Detail from JIRA

Votes	3
Component/s
Labels	Bug
Assignee	None
Priority	Medium

md5: 4659038e109b6bed99ec521e272addf0

Issue Description:

Setup:
We create an ObjC App that uses our SPM package "RevenueCat".
In our app, we create an object that uses an object from the "RevenueCat" package as part of its api.

We expose this object's header (which exposes the method containing the RevenueCat object as a parameter) as a public header.

We create a Swift test target that depends on the ObjC App and has a bridging header for that object we created.

We attempt to use the API in a test. API that doesn't include RevenueCat objects is fine, but any API that uses RevenueCat objects in the parameter is not found.

Environment:
Xcode 12.5.1 (Build version 12E507) & Xcode 13 Beta 5

M1 Mac as well as Intel mac.

Swift Package Manager - Swift 5.4.0

Swift Package Manager - Swift 5.5.0

Component: Package Manager

Reproduction project: https://github.com/taquitos/SPMBug

Attempt to build the test target.

You'll get
`Value of type 'TaquitosAreTheBest' has no member 'purchaserInfo'`

[typesanitizer]

@swift-ci create

[ryanwilson]

We ran into a similar issue, I believe a workaround is to import the header instead of using a forward declaration. I know it's not the best practice for Obj-C but makes it usable at least.

[oleksandryevdokymov]

I have faced similar issue. This bug is also reproduces in mixed Swift/Objective-C project (not only in Test target).
Case: header file has forward class declaration from SPM and this type used for declare properties or parameters in this header.
Those properties and parameters won't be exposed into Swift.
You will receive build error:

[scannillo]

👋 We have encountered this same issue while converting the Braintree SDK from Obj-C to Swift. Our SDK is comprised of several sub-modules, and while we thought we could convert to Swift module-by-module, this SPM bug has us blocked and forced to convert our entire SDK at once.

Our team has created a Swift Forum post on the issue here, for those that want to follow along / try to gain traction.

[AnthonyLatsis]

cc @tomerd

[mamouneyya]

Sharing this workaround which we have been using for a while now to go around this. Just add this to your app's build settings (or whatever consumer of the package that has the Obj-C types). Even better if you're using a .xcconfig file since you can add a comment explaining why this weird hack is needed:

// Until the following Swift Package Manager bug is
// fixed, we have to explicitly load the generated
// module map of any dependency that has ObjC bridged
// types (a.k.a. `@objc` annotated Swift types). Other-
// wise the module won't be accessible from ObjC headers
// Ref: https://bugs.swift.org/browse/SR-15154
OTHER_SWIFT_FLAGS = $(inherited) -Xcc "-fmodule-map-file=${OBJROOT}/GeneratedModuleMaps-${PLATFORM_NAME}/PackageWithObjC.modulemap"

[AnthonyLatsis]

@tomerd Please help me transfer this if it is indeed a package manager issue.

[tomerd]

cc @abertelrud @neonichu

[neonichu]

Sounds like an Xcode issue to me.

[rconnell9]

@scannillo, is this still an issue for you? I was able to build the original example project (https://github.com/taquitos/SPMBug) without issue