Realm-cocoa: umbrella header 'Realm.h' not found

[fiancrs]

RS,this problem happened when i used cocoapods integrate Realm to my iOS project(Using Xcode 7)

here's my screenshot, thanks!

[mrackwitz]

Which version of CocoaPods do you use? I guess, you declare the directive use_frameworks! in your Podfile?

[fiancrs]

The version is 0.38.2. I had found the problem finally, i had set &(PODS_ROOT) in Build Setting in my Project(not the Pods’s).But in the other side ,it make some clashes with other thirty-party library. Absolutely , i had declared ‘use_frameworks’ in Podfile

On 24 Sep 2015, at 00:14, Marius Rackwitz [email protected] wrote:

Which version of CocoaPods do you use? I guess, you declare the directive use_frameworks! in your Podfile?

—
Reply to this email directly or view it on GitHub https://github.com/realm/realm-cocoa/issues/2558#issuecomment-142651392.

[mrackwitz]

So is it now working for you? Which third-party libraries are those, where you noticed clashes with? Would you mind sharing your Podfile? Is this perhaps more sort of a general problem with CocoaPods?

[fiancrs]

here is my Podfile . Actually I don't know if this is not a conflict。why i set $(PODS_ROOT),the Realm had warming me "umbrella header 'Realm.h' not found".without that ,the QBImagePickerController warming warming ''unfound QBImagePickerController" about this

[mrackwitz]

With CocoaPods it should be never necessary to overwrite PODS_ROOT in your project or in any other target. If QBImagePickerController doesn't work without that, then it seems like something is wrong with this pod. Can you copy the exact error message you get?

[jpsim]

@fiancrs have you had the chance to undo overwriting PODS_ROOT and then sharing the complete CocoaPods error message here so we can help you fix your project?

[jpsim]

Closing assuming @fiancrs resolved their issue.

[AgapovOne]

I also have a problem exactly like this after I just added realm pods, and installed them through pod update
Here is my Podfile (cocoapods v0.39.0):

platform :ios, '8.2'
source 'https://github.com/CocoaPods/Specs.git'
use_frameworks!

target 'IntellectualCallerID' do

  #Core pods
  pod 'Alamofire'
  pod 'SwiftyJSON'
  pod 'Async', :git => 'https://github.com/duemunk/Async.git'
  pod 'ChameleonFramework/Swift'
  pod 'DZNEmptyDataSet'
  pod 'pop'
  pod 'SnapKit'

  pod 'Fabric'
  pod 'Crashlytics'

  pod 'Realm'
  pod 'RealmSwift'
end

[fiancrs]

Check whether u had set $(PODS-ROOT) in your main target's setting ,if had ,try to delete it

Sent from my iPhone

On Oct 15, 2015, at 2:44 PM, Agapov Alex [email protected] wrote:

I also have a problem exactly like this after I just added realm pods, and installed them through pod update

—
Reply to this email directly or view it on GitHub.

[AgapovOne]

Still have problems, but now with cocoapods itself without PODS_ROOT in User Defined inside Build Settings for my app.

I have these warnings:

[!] The `IntellectualCallerID [Debug]` target overrides the `PODS_ROOT` build setting defined in `Pods/Target Support Files/Pods-IntellectualCallerID/Pods-IntellectualCallerID.debug.xcconfig'. This can lead to problems with the CocoaPods installation
    - Use the `$(inherited)` flag, or
    - Remove the build settings from the target.

[!] The `IntellectualCallerID [Release]` target overrides the `PODS_ROOT` build setting defined in `Pods/Target Support Files/Pods-IntellectualCallerID/Pods-IntellectualCallerID.release.xcconfig'. This can lead to problems with the CocoaPods installation
    - Use the `$(inherited)` flag, or
    - Remove the build settings from the target.

[fiancrs]

I don't know what's your mean exactly 。The pods root setting should not be happened in your main project target but not the pods project target . This warning is dued to the Xcode had searched the head files straightly needn't framework's name while you had setting pods root in your main project target 。

Sent from my iPhone

On Oct 16, 2015, at 3:47 AM, Agapov Alex [email protected] wrote:

Still have problems, but now with cocoapods itself without PODS_ROOT in User Defined inside Build Settings for my app.

I have these warnings:

[!] The IntellectualCallerID [Debug] target overrides the PODS_ROOT build setting defined in Pods/Target Support Files/Pods-IntellectualCallerID/Pods-IntellectualCallerID.debug.xcconfig'. This can lead to problems with the CocoaPods installation - Use the$(inherited)` flag, or
- Remove the build settings from the target.

[!] The IntellectualCallerID [Release] target overrides the PODS_ROOT build setting defined in Pods/Target Support Files/Pods-IntellectualCallerID/Pods-IntellectualCallerID.release.xcconfig'. This can lead to problems with the CocoaPods installation - Use the$(inherited)` flag, or
- Remove the build settings from the target.
—
Reply to this email directly or view it on GitHub.

[mrackwitz]

@Leshich: Did you really removed the build setting or overwrote it with an empty value?

[AgapovOne]

I did remove a value, so now it's empty. Xcode is not allowing me to fully remove this 'User-defined' build setting.

I have another project with realm installed. But I also have a pods_root setting in there. That project works fine. But I do have some problems with active project where I had a lot of pods for three months working correctly, and now I can't add only Realm. I don't really know what's the problem here.

Is this the setting you say about?

[mrackwitz]

Can you enable showing different levels to check where this build setting originates from? It doesn't seem to be overwritten anymore as it was when you ran pod install. Does the warning still appear if you run it again?

[mrackwitz]

@Leshich: FYI - You can select the levels perspective here. The other red box marks where the setting is expected to come from, all other columns should be empty in that row, beside the column which shows the resolved value.

[AgapovOne]

https://github.com/CocoaPods/CocoaPods/issues/4420

After updating to Xcode 7.1 I have this problem running with facebook/pop library. So now I have already two problems with connecting framework through cocoapods. I want to wait a bit for a fixes in cocoapods/xcode for now.

[AgapovOne]

Still have this problem installing Realm through Cocoapods.

Installed using Dynamic frameworks. It worked, but i really want to use cocoapods here)

Don't really know what's my problem, because I have a second app using realm through cocoapods, and it works:)

[krimpedance]

I held the same problem, too.

I was adding Bridging Header to use SVProgressHUD in Swift.
But then a message as "error: 'SVProgressHUD.h' file not found" had, so I was settled by setting "User Header Search Paths = Pods/**".

When making Realm coexist, this setting seems to have been a problem.
So I was changed "Pods/" to "Pods/SVProgressHUD/".
Compilation passed by this.

By now, I guess you get used to my funny English writing.

[ncbb]

I had the same problem. Manually moving some header files (specifically, those declared in Realm.h) from “Project Headers” to “Public Headers” solved the issue. Latest Xcode, cocoa pods 1.0.0.beta.3.

[jpsim]

We don't support any of the CocoaPods 1.0 release candidates at the moment. Please use the latest stable version of CocoaPods to install Realm.

[bimusiek]

@jpsim Any plans on supporting it? I am forced to do so, as other things are not working properly with stable cocoapods version. With beta I don't have any problems except for RealmSwift import. :(

[jpsim]

_Of course_ we plan on supporting CocoaPods 1.0! Unfortunately, the release candidates have introduced a regression, which is being tracked in CocoaPods/CocoaPods#4848 on their side, and realm/realm-cocoa#3052 on our side.

Contributors to both CocoaPods and Realm are looking into the best way to fix this.

[sushiwu]

I also have this problem, too.
CocoaPods 0.39.0
swift

[sushiwu]

[velthune]

I find THE solution:

pod _0.39.0_ install --verbose

I was installing with cocoapod 1.0.* that Realm does not support yet!

[mrackwitz]

I was installing with cocoapod 1.0.* that Realm does not support yet!

That's not true anymore. We support the prereleases of CocoaPods 1.0 from 1.0.0.beta.4.

[velthune]

Oh.. are you sure? I'm using 1.0.0.beta.3 and Xcode 7.3.
I read "N.B.: The CocoaPods 1.0.0 Release Candidate versions are not supported at this time. Please use the latest stable version." from doc.

[velthune]

@mrackwitz you're right, I updated cococapods

 sudo gem install cocoapods --pre

Then I run:

pod clean
pod install --verbose

And all works fine, thanks!