'Intercom/Intercom.h' file not found
See original GitHub issueapp/node_modules/react-native-intercom/iOS/IntercomUserAttributesBuilder.m:10:9: 'Intercom/Intercom.h' file not found
react-native-intercom: 11.0.0 intercom-ios: 5.0.2
Tried every combination of Search Paths, adding and removing Libraries and the framework, react-native link but can’t get the app to build. Worked with react-native-intercom 10.2.0 and an older version of the iOS SDK
Issue Analytics
- State:
- Created 5 years ago
- Reactions:8
- Comments:19 (6 by maintainers)
Top Results From Across the Web
Use of undeclared identifier 'Intercom' in AppDelegate.m
If you go into the framework's Headers folder in your workspace (Workspace -> Intercom.framework -> Headers) you will see the Intercom.h file.
Read more >React-native 0.60.6 - Interconnected - Intercom
I'm trying to use the intercom libs on our react native apps but I'm running into trouble with the ... 'Intercom/Intercom.h' file not...
Read more >changelog - CocoaPods
Fixed: An issue where Intercom was not relinquishing keyWindow status, causing problems with external keyboards and text input fields. Fixed: An issue where...
Read more >@intercom/intercom-react-native - npm
Start using @intercom/intercom-react-native in your project by running `npm i ... There are no other projects in the npm registry using ...
Read more >How to install React Native Intercom for 0.63+ | by Begum Akbay
Build input file cannot be found · React/RCTDefines.h file not found · Intercom/Intercom.h not found · Library not found for -lCocoaAsyncSocket ...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Sorry, I was reacting to the single word “No” response and the closing of the issue with no further comment, which seems to me a poor way to respond to a legitimate request.
Since most react native packages offer a simple install mechanism with
react-native link
, it seems entirely reasonable an expectation to have of this repo.An alternative response to “No [closes issue]” could also have been “I don’t have any plans to implement this due to lack of time, but I am totally open to any PRs”, or “I don’t think this is the right direction for this package, so I won’t be implementing it, but feel free to fork this repo and do as you please” or whatever.
I admit I thought this was maintained by Intercom (and find it a little unsettling that they don’t invest in this project themselves), so I do apologize for any offense my ignorance may have caused.
No.