@swift-ci create

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.

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:

👋 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.

cc @tomerd

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"

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

cc @abertelrud @neonichu

Sounds like an Xcode issue to me.