Comment by Steven Sheldon (JIRA)

This warning was introduced in 08af6f0, cc graydon (JIRA User)

Is there a way that tests should be configured for mixed ObjC/Swift targets to avoid this warning? When creating a brand new Swift app with tests in Xcode, as soon as I add an ObjC file and a bridging header this warning starts to appear.

Comment by Graydon Hoare (JIRA)

Yeah, it was introduced a little too aggressively in that patch which made it into beta 1, sorry! We're aware and have dialed it down a ways (see: #7045 ) but it's going to take a little while to percolate through to a release build. It's in nightly snapshots already if you want to install one of those.

If you don't want to wait, the workarounds are:

1. explicitly import the App bridging header into your unit tests (via a build setting) or

2. chain the import by adding #import "App-Bridging-Header.h" to any existing unit test bridging header you have

Comment by Steven Sheldon (JIRA)

Thanks and no problem, I wanted to make sure it was reported before the full Xcode 8.3 release but you're way ahead of me 🙂

Feel free to close this out if it's been fixed by that pull request, I can try corroborating with a nightly snapshot sometime.

Comment by Steven Sheldon (JIRA)

Okay I've tried this out on Xcode 8.3 beta 3 using the Swift 3.1 2017-03-05 toolchain, and the original case I reported doesn't warn anymore. However if you add a bridging header to the tests (even an empty one) the warning starts appearing again. I've attached a second repro case.

Is that expected? i.e. are we required to chain the import like described in workaround #2 above? (A tweet from Jordan seems to imply that this might be expected)

Comment by Graydon Hoare (JIRA)

Yes it's expected in that context (that's the context the followup fix narrowed it to). Chaining the bridging headers together is the intended fix. Long-term, we'd like to phase out support for the implicit imports altogether, which means that chaining or explicit imports will be the only mechanism that remains working.

Comment by Steven Sheldon (JIRA)

Got it. If there's any way to change this diagnostic so that it suggests adding the import to the bridging header, that might be helpful. Otherwise I think this is fine to close out.

Thanks for your help Graydon!

Comment by Erik Aigner (JIRA)

Is this ever going to be fixed? Still can't import a single mixed framework without generating tons of warnings. The workarounds listed here are not valid solutions, the bridging header should not be exposed to any importing project at all.