-
Notifications
You must be signed in to change notification settings - Fork 136
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
AppCenter/AppCenter.h file not found (rn 0.61.0-rc.3 - use_native_modules! & use_frameworks!) #714
Comments
Hey @brunoreis ! While I set up new RN to reproduce, would you mind answering these questions: Does this issue reproduce only on XCode 11? |
Have also seen any errors/warnings during |
And could you send your Podfile please? |
Hi @annakocheshkova, I tested a fresh install here and got the same error. I think this will be easier for you to test.
4 - I "deintegrated" the pods and run
5 - to fix that I added this hack on the Podfile
6 - So, isolating things, the issue seems to be with the use_frameworks! Please notice I did not add any other packages or pods other than AppCenter and ReactNative default ones. Podfile:
|
I dont understand, should we put I have problem on AppDelegate.m |
@yestay90, I think that the |
Hey @brunoreis. Indeed this is not working and looks like in new RN version, there's still no proper support for dynamic frameworks. |
@brunoreis just wanted to let you know that I opened an issue in react-native repo. Feel free to jump in! |
I am closing this issue. Feel free to reopen if you feel like you need support. |
@annakocheshkova, thanks. Sorry for the delay answering this. I was focused on a web task. We decided to wait a little to work on the new RN build. I think the newest 0.61.0 version already supports use_frameworks!. (https://github.com/facebook/react-native/releases/tag/v0.61.0)I was able to build with rc-3 at that moment. But was not able to build after adding the AppCenter libs. I'll let you know when we get back to this task. Thanks a lot! |
Hi @annakocheshkova, I am working to solve this same problem with the flag use_framework!, any suggestion is welcome.
Podfile
Versions: |
@JuanSeBestia would you mind sharing step-by-step guide to repro? That would really help me investigate the problem. Thanks in advance |
@Jamminroot I have replicated it, in the installation of the Pods it is broken, you can read the steps in the readme of the git https://github.com/JuanSeBestia/RN-test |
This worked in my case :
I am using : |
Downgrading cocoapods didn't fix "use_frameworks" issue for me. It is still not supported fully from react-native side. |
@arcesoj I need the las versión of RN 61.x :/ |
I am experiencing the same incompatibility with AppCenter and use_frameworks on RN 61.3 |
Hi, @freshedgarT ! It still is not supported on RN. |
+1 for react-native 0.61.4 - the same issue with use_framework! in pod file! |
Hi @annakocheshkova. Are you sure it's not supported on RN? I was able to build the RN (>0.61) app with all the modules I had and 'use_framework!'. Conflicts only happen if I try to add AppCenter. In fact, due to that, we had to remove AppCenter from our app on the recent build. |
This is a big issue for us as well. I had to remove AppCenter and AppCenterAnalytics from our most recent build, just like @brunoreis because we need 'use_framework!' |
I solved the build issue by downgrading Cocoapods to 1.5.3 as a temporary solution. |
This isn't really a solution to this issue, but I managed to upgrade all my modules to where I didn't need |
if you want to use CodePush only, it seems that https://github.com/microsoft/react-native-code-push still builds on new RN versions with |
I had to remove all AppCenter modules except for code push to get things working because of this issue. |
What is going on with this? Hitting same issue. |
Same... |
Any updates on this? |
Hey, this is going to be addressed in one of the next releases. |
In the meanwhile, are there any workarounds you guys came up with? |
@viemic you can try to apply changes from this PR: https://github.com/microsoft/appcenter-sdk-react-native/pull/789/files |
Any new about this issue? |
This issue should be fixed in version 3.0.0. |
I am using RN Version: "react-native": "0.61.5" I have tried all the workarounds mentioned above none of them worked for me. |
Hi! Thanks for getting in touch with us!
If the issue will persist then could you please try to reproduce this issue on an empty project and let me know about the results? |
@0x1bitcrack3r it's probably related to #875 - 3.0.1 pods do not pin version, so it leads to version conflict. Please update to latest (4.x) or to version with the patch for this issue (3.1.3) |
I have tried above steps in my current project still no luck. Will try checking with an empty project |
Description
I get the following error message on xCode 11, trying to build on an iPad pro. The message here is:
.../node_modules/appcenter/ios/AppCenterReactNative/AppCenterReactNative.m:22:9: 'AppCenter/AppCenter.h' file not found
If I go to that DerivedData folder, I don't see an AppCenter.h in there. Only appcenter-umbrella.h and AppCenterReactNative.h.
I'm new to xCode, but I could note that:
There is a pod under
Development Pods
calledappcenter
, and another one insidePods
that's calledAppCenter
. TheAppCenter
one is where the AppCenter.h lives, but the podspec just mention the AppCenterReactNativeShared.frameworkI have to use "use_frameworks!" due to a pod that requires it. But I don't know enough to say if it's messing things up or not.
(rn is 0.61.0-rc.3, because I read it has support for use_frameworks! and appcenter is 2.3.0)
2.3.0
iOS 12.3.1
iPad Pro
Bugsnag
TextToSpeech
fetch-blob
RNCAsyncStorage
RNVectorIcons
react-native info
pod --version
1.5.3
[MSAppCenter setLogLevel: MSLogLevelVerbose];
before your call to[AppCenterReactNative register];
(or any other SDK registration). For Android, useAppCenter.setLogLevel(android.util.Log.VERBOSE);
before yourSoLoader.init
call (you will need toimport com.microsoft.appcenter.AppCenter;
). Include the logs here:I think this does not apply, because I can't even run.
The text was updated successfully, but these errors were encountered: