UncheckedReturn -Xclang -analyzer-checker -Xclang security. Sidenote: if you're using fastlane to deploy, keep your project's build target in first place, otherwise fastlane gets confused and thinks you're building a library, so it never builds an ipa. Summary:The subspec should declare enough dependencies. Sorry for the wrong first response on your solution but I'm just a little bit puzzled when after ejecting with expo the integration with fcm went to hell and I have to revert all my changes to make the project without expo, only plain react native and from that moment I has a little bit mess in native and js source code. AbeHerbert I now how frustrating that is I had that issue for a while and 's suggestion worked for me. However, I deleted the reference and copied as a group and it worked as expected.
Is there any other trick to get new schemes to work as well using the new staging configuration. If the include file is part of a single Sketch, instructions are here. This issue has been automatically marked as stale because it has not had recent activity. The problem was not the Info. Have a question about this project? It will be closed if no further activity occurs. Due to this, I got an error from iTunesConnect Invalid Bundle - One or more dynamic libraries that are referenced by your app are not present in the dylib search path.
Since this path is now in the Header Search Paths of the main project, it gets picked up and everything else builds fine. I want to avoid having to keep editing the scheme every time I create a staging or a release archive. With the latest changes to public headers exposed by React. I am not sure if it sheds any more light on the problem I am having since you said that the said issue doesn't occur with packages installed using cocoa pods and that the scheme manager is mainly to fix the projects installed using npm. Actually there is not much magic.
I looked at the react-native-schemes-manager when I was going to through the comments. Sign up for a free GitHub account to open an issue and contact its maintainers and the community. I suggest something like MyCommon. . Duplicate one of the configurations and give it whatever name you like. Summary: To make React Native play nicely with our internal build infrastructure we need to properly namespace all of our header includes.
I'm not clear on the differences between those two. I just added that dependency back in 0. Observe that the frameworks are not listed. If I edit the default scheme to use the staging configuration, then the archive is created successfully. Sign up for a free GitHub account to open an issue and contact its maintainers and the community. Until all that changes, or the guys at the metro bundler tackle this problem in a very smart way, the work stays the same. I hope it will solve your problem.
If you think this issue should definitely remain open, please let us know why. Even if I patch it to find React, it can't find any other native dependencies. Determined to figure this out, I finally got it to work with the new project. UncheckedReturn -Xclang -analyzer-checker -Xclang security. So I removed the dependency in 0. Have a question about this project? I tried the suggestions from and using which I was able to build the app using staging configuration.
The following sections are informative. I will use the react-native-schemes-manager if I don't find a solution to this problem soon. The error mentioned and error icon are there from the start. But as they all require the rn packanger which has just two build configurations, those need to be copied for all of them. When my project builds, React builds first, and since it doesn't know about configurations other than Release and Debug, it builds with the Release configuration. I'm not sure, this might help.