-
Notifications
You must be signed in to change notification settings - Fork 14
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
'WebEngage/WebEngage.h' file not found #8
Comments
@uc-asa Can you share more details on your integration? |
@uc-asa Awaiting your reply. |
PodFileUncomment the next line to define a global platform for your projectplatform :ios, '9.0' Uncomment the next line if you're using Swift or would like to use dynamic frameworksuse_frameworks!Pods for MyApppod 'React', :path => '../node_modules/react-native', :subspecs => [ pod "yoga", :path => "../node_modules/react-native/ReactCommon/yoga" pod 'react-native-webengage', :path => '../node_modules/react-native-webengage' RNFirebasepod 'RNFirebase', :path => '../node_modules/react-native-firebase/ios' end target 'MyApp-tvOSTests' do Pods for testingpod 'react-native-image-picker', :path => '../node_modules/react-native-image-picker'pod 'react-native-fetch-blob', :path => '../node_modules/react-native-fetch-blob' pod 'react-native-netinfo', :path => '../node_modules/@react-native-community/netinfo' pod 'react-native-webview', :path => '../node_modules/react-native-webview' pod 'RNCAsyncStorage', :path => '../node_modules/@react-native-community/async-storage' end target 'MyApp' do Pods for testingend target 'MyApp-tvOS' do Uncomment the next line if you're using Swift or would like to use dynamic frameworksuse_frameworks!Pods for MyApp-tvOStarget 'MyApp-tvOSTests' doinherit! :search_paths# Pods for testingendend target 'NotificationService' do target 'NotificationViewController' do |
#PodFile.lock PODS:
DEPENDENCIES:
SPEC REPOS: EXTERNAL SOURCES: SPEC CHECKSUMS: PODFILE CHECKSUM: 8a31f18a0f169f20bff030375e87b0fc63874a62 COCOAPODS: 1.8.0.beta.2 |
@uc-asa We are debugging this, will get back to you shortly. |
@ygit, I'm also facing the same issue, I'm using react-native-webengage v1.1.1, react-native v0.59.1 |
Facing the same issue. Unable to release updates to our app because of this error. Please resolve it fast. |
Could this be a result of an upgrade to xcode 11? I have a branch on RN 0.59.8 that was building fine, but now does not. It worked before I got xcode 11 as an automatic update. No guarantee this is the cause, but it is known to cause some problems with RN (see this issue), so perhaps this module is also affected in some way? RN had to release a fix as part of 0.59.9. |
Hey, I did some hack, I removed the reference of RNWebenage.xcodepro from my project's library and removed RNWebengage.a files from the binary section under build phase and then pod install Works for me. |
@rdickert Does the same branch work on Xcode 10 for you? |
@ygit I downgraded xcode, and the problem persisted, so I went a little deeper. The change that actually broke the branch came when I was merging a large feature branch. It had a merge conflict in package-lock.json, so I was guessing that something happened in a version change when I addressed that. However, a look at the package-lock.json doesn't show a change to webengage. Our package.json has
and the package-lock for that version shows
Unfortunately for this discussion, I learned that we aren't using webengage anymore, so my fix was to remove it altogether, but hopefully this info will help a little. |
@uc-asa We have released a new version of iOS SDK: 4.9.8 |
As mentioned earlier, updating to WebEngage iOS SDK version 4.9.8 or above resolves this issue. |
Still facing issue in release/archieve build - "react-native-webengage": "^1.2.9", "react": "^17.0.2", |
Try updating to XCode14. Solved the issue for us. |
I just updated my react native project with RN 0.59.9. After updating its showing
'WebEngage/WebEngage.h' file not found
.I tried many things but fails.
Team, could you help please with this.
The text was updated successfully, but these errors were encountered: