implicit import bridging header in module is deprecated

bridging-error.mkd

now in swift 4 you just have to import a briding header into Test target and reference objc-class .h files there...using @testable import nameOfYourApp should work

In Swift there's a message in "Test Target" that states that the bridging header will be removed in newer versions of swift. I'm using mixed objc and swift clasess, but the UnitTest class is a swift file. Using @testable key was there in code

  @testable import YourProject

You fix it by adding in your Test area the bridging header with objc headers that your test will use:

  #import "Project-Bridging-Header.h"

Oldated ..

and deleting the @testable inside your test

 import YourProject 

I'm unclear on the context here. If you're using @testable import YourProject (which I am) then it looks like it's in a swift file. In which case adding #import "Project-Bridging-Header.h" will lead to a syntax error since it's not valid swift. Also, as @hlung and @alper mentioned, you lose access to classes in the application module when you remove @testable. At least, like them, that's what I'm seeing.

My Scenario: App contains mixed code (objC/Swift), UnitTest class is a swift file.

I import the "App-Bridging-Header.h" in my TestTarget Bridging Header (ObjC) and in my TestClass I remove the "@testable" so it looks like "import App". Then the Warning disappear and all seems to work well.

Source: Comments on the bug ticket: https://bugs.swift.org/browse/SR-3801

Maybe is not that clear the text I wrote long ago. I've updated the text :/ like @matzino commented, that was my solution as well.

Removing @testable in my test class leads to a lot of unresolved types, which are no longer imported from the "main" target.

For me the solution was much simpler, just go to the AppTest-Bridging-Header.h and add #import "App-Bridging-Header.h". I didn't touch the test class and kept the @testable.

@florieger - appreciate it. This worked for me. Just adding the #import "Bridging header.h file here" worked for me and didn't touch the @testable ` on my test class and all good.

Once I did this..I'm getting a module not found in my original bridging header file now. Warning or error went away in my test class but now my main bridging header is getting screwed up..any ideas?