react-native-fabric: 'Crashlytics/Crashlytics.h' file not found at update component

I update component version and now on iOS: /myProject/node_modules/react-native-fabric/ios/SMXCrashlytics/SMXCrashlytics.m:2:9: 'Crashlytics/Crashlytics.h' file not found

In SMXCrashlytics.mfail #import <Crashlytics/Crashlytics.h>

In SMXcrashlytics project, Header Search Paths have: $(SRCROOT)/../../../ios/Pods/Headers/Public/Crashlytics

But in Headers i dont have Crashlytics, but i have it on my Podfile and in /ios/Pods/Crashlytics

I think i must add the correct Framework Search Paths.

About this issue

  • Original URL
  • State: closed
  • Created 8 years ago
  • Reactions: 2
  • Comments: 16 (4 by maintainers)

Most upvoted comments

See this previous issue that is a duplicate for this one: #17

Read below for a conclusion of how to fix this (I wish I had this distilled when I had the problem myself, since it took me a while to figure things out):

There are 2 scenarios based on your Podfile: you have use_frameworks! enabled -or- disabled (i.e. commented out).

First, regardless of what scenario you’re in

In your XCode project select Libraries/SMXCrashlytics.xcodeproj , and go to Target’s “Build Settings”. Then:

if you have use_frameworks! enabled in Podfile

in Framework search Paths, add:

$(SRCROOT)/../../../ios/Pods/Crashlytics/iOS

=> You’re DONE

if you do NOT have use_frameworks! enabled in Podfile

in Header Search Paths

$(SRCROOT)/../../../ios/Pods/Headers/Public/Crashlytics with non-recursive set

=> You’re DONE

@rcugut 's solution still failed for me 😦

My RN version is 0.44

Here’s my Podfile `use_frameworks!

target ‘dm_app’ do pod ‘SwiftyJSON’, ‘3.1.4’ pod ‘Charts’, ‘3.0.1’ pod ‘Firebase/Core’, ‘4.0.0’ pod ‘Firebase/Messaging’ pod ‘Fabric’ pod ‘Crashlytics’ end

post_install do |installer| installer.pods_project.targets.each do |target| target.build_configurations.each do |config| config.build_settings[‘SWIFT_VERSION’] = ‘3.0’ end end end `

2017-08-14 2 12 39 2017-08-14 2 13 21

Anyone still facing the same problem now?

Did you ever get this resolved? having the same issue on xcode 8