umbrella header for module 'myFramework' does not include header 'otherFramework.h'

Question

My Swift / iOS9 framework 'viewer_protocol' uses another and external Objective-C framework (CocoaAsyncSocket). I'm using Carthage to build CocoaAsyncSocket. So far everything works fine: In have an example App inside my framework Xcode Project using my framework without any problems.

Now I want to use my Framework in a different Xcode Project - although using Carthage. I include only my Framework as a dependency and Carthage automatically resolves the dependencies to CocoaAsyncSocket. I embedded both frameworks into this new Xcode Project and build my App: Everything works fine here - except one warning I can't rid off:

/Users/John/Repositories/my_project/<module-includes>:1:1: 
Umbrella header for module 'my_project' does not include header 'GCDAsyncSocket.h'

This is my framework header:

#import <UIKit/UIKit.h>

//! Project version number for my_project.
FOUNDATION_EXPORT double my_projectVersionNumber;

//! Project version string for my_project.
FOUNDATION_EXPORT const unsigned char my_projectVersionString[];

// In this header, you should import all the public headers of your framework     
using statements like #import <my_project/PublicHeader.h>
#import <CocoaAsyncSocket/CocoaAsyncSocket.h>

As you can see CocoaAsyncSocket.h is imported. Furthermore inside my framework the CocoaAsyncSocket.h file is included:

What I am missing here? I'm using several others external frameworks inside my framework, there're no warnings for them - all of these external frameworks are written in Swift - CocoaAsyncSocket is pure Objective-C.

This is my frameworks module.modulemap:

 framework module my_project {
   umbrella header "my_project.h"

   export *
   module * { export * }
 }

 module viewer_protocol.Swift {
     header "my_project-Swift.h"
 }

Update

I found a solution: Changing the import statement in my framework header from

#import <CocoaAsyncSocket/CocoaAsyncSocket.h>

to

#import "CocoaAsyncSocket/CocoaAsyncSocket.h"

Now Xcode finds the header file and the warning disappears.

score 38 · Answer 1 · answered Aug 03 '16 at 09:49

38

I recently ran into same issue. Apparently I had header file set as public in target membership, but it was not exposed in umbrella header. Fixed issue by making header file with project access instead of public.

answered Aug 03 '16 at 09:49

AyJay

439
6
12

This should have way more upvotes. Fixing the header's privacy setting is a far better solution than importing something you don't need. – Max Dec 13 '17 at 21:36
This worked for me as well. I could not actually make mine public as suggested above, because it included C++ stuff that Swift could not handle. : – Joe Steele Sep 27 '18 at 17:39
I feel like this is the answer they were getting at when they wrote the error message. Thanks for putting it into actionable words! – Ben Leggiero Feb 13 '19 at 22:46

score 27 · Answer 2 · edited May 09 '20 at 18:15

27

I had the same issue today

Umbrella header for module 'HockeySDK' does not include header 'BITHockeyBaseViewController.h'

and the solution was

1.build and run project and go-to Report Navigator

2.look at the warning, click to expand details

it will so you the file name where you need to make change as you can seen in below screen shot

So i just updated my import statement in AppDelegate.m file

New

#import "HockeySDK/HockeySDK.h"

Old

#import <HockeySDK/HockeySDK.h>

and issue gone..

hope this will help someone. who are coming here for solution.

edited May 09 '20 at 18:15

Kiril S.

8,572
5
34
56

answered Mar 10 '16 at 08:47

swiftBoy

33,793
26
129
124

The same for me but in my case the problem was Twitter.SDK. Thanks for you response! – MarMass Nov 16 '16 at 09:19
i had the same issue with UnityAds SDK. i was doing #import "UnityAds/UnityAds.h" instead of #import – Radu Ursache Jun 26 '17 at 23:22

score 23 · Answer 3 · edited Nov 12 '20 at 03:47

23

I had the same issue. Seemed to be related to old build files.

The standard Xcode problem fixer worked for me:

Clean project (Product > Clean Build Folder)
Deleted derived data
Restart Xcode

edited Nov 12 '20 at 03:47

Minding

1,112
1
14
24

answered Aug 21 '16 at 23:58

Senseful

73,679
56
267
405

On XCode 8 I had the same issue and only this worked. Cleaning not, needed to delete the derived data. – iOS Developer Jan 13 '17 at 15:23
1

I cleaned the build folder(option+cmd+shift+K) and builded again. Warning disappeared. – techgentsia Jun 12 '18 at 11:49

score 15 · Answer 4 · answered Mar 23 '16 at 08:40

15

For me the solution was as follows:

1) Each Objective C framework has 1 header file that contains all the:

#import ...
#import ...
#import ...

2) Make sure that this file imports the missing header.

3) Build the project again, it should remove the warning.

answered Mar 23 '16 at 08:40

Oded Regev

3,235
2
34
49

Thank you for this. – Philihp Busby Oct 11 '16 at 20:45

score 12 · Answer 5 · answered Aug 29 '17 at 22:15

12

Alternatively, you may have exposed files within the Public area of your framework's build phases that should actually be moved back to the Project area.

If you don't want those files to be within your framework's umbrella header so they're publicly accessible, you can revert this.

Goto Framework -> Target -> Build Phases and drag to move the unnecessary header files from Public to Project.

Screenshot

answered Aug 29 '17 at 22:15

iwasrobbed

45,197
20
140
190

awsome. u save me – Kernelzero Oct 19 '18 at 02:22
Hi could you please check my question: https://stackoverflow.com/questions/56769304/extending-a-public-class-for-partial-public-access-in-swift – nr5 Jun 26 '19 at 13:31

score 7 · Answer 6 · answered Jul 15 '16 at 14:47

7

Just for completeness if your header is set to public in :

Build Phases > Headers

You should either

Include the import in your main header as others have mentioned

OR

Move that header to "private" if it doesn't need to be exposed

answered Jul 15 '16 at 14:47

pflous

531
6
16

score 6 · Answer 7 · answered Aug 23 '17 at 22:38

6

We got this recently and it was due to corruption in DerivedData. Deleting that folder fixed the problem.

answered Aug 23 '17 at 22:38

AnneTheAgile

8,897
6
42
45

score 1 · Answer 8 · answered Jul 29 '19 at 06:39

1

In my case (Obj-c framework):

Umbrella header for module 'opus' does not include header 'opus_multistream.h'

I needed to change:

@import opus.opus_defines;

into

@import opus;

(I don't have in #import "....h" or #import <....h> for frameworks)

answered Jul 29 '19 at 06:39

szubiszon

86
7

score 0 · Answer 9 · answered Dec 04 '17 at 22:46

Take a look at this post:

@import vs #import - iOS 7

It goes over the concepts of the new module importing. I had my own custom framework and after adopting the new method to import objective-c framework

old: #import <MyFramework/MyFramework.h>

new: @import MyFramework;

it took care of the warning/

user1105951 · Answer 10 · 2018-10-16T13:21:00.297

0

For others : In my case I already move the headers I want to expose from my framework, from "project" to "public" (Build phases of the framework target)

Then Xcode gave my this warning.

Xcode is telling us that we also need to add #import "name of header in the warning> in the public header file that was created with framework, so the clients (of the framework) will know this header.

So The Fix:
1.go to the framework public header file.(the one what created by xcode when you created the framework) .
2. add #import "the-name-of-the-header-in-the-warning.h"

edited Oct 16 '18 at 13:21

answered Oct 16 '18 at 12:51

user1105951

2,117
2
28
53

This is the best, simplest distillation of the solution. Thanks! – Ben Leggiero Feb 11 '19 at 21:37

score -1 · Answer 11 · answered Aug 29 '16 at 07:36

trying to fix a archive build error led me to this error and post

my solution was real simple but took forever for me to figure out.

when i ran $ pod install it generated a workspace for me in the same dir as my .xcodeproj file.
however i had already created a workspace to use as its parent directory.
so then i simply deleted my old workspace and went with the one that pods created

hope this helps someone! glhf!

score -1 · Answer 12 · answered Jan 25 '17 at 08:14

-1

For me the fix was rather simple, commit all your changes and build again. The warning disappeared.

answered Jan 25 '17 at 08:14

jarora

4,400
2
30
39

umbrella header for module 'myFramework' does not include header 'otherFramework.h'

12 Answers12

Linked