Hi @jarekbb, like @dnkoutso mentioned it is in all probability an issue with how react native interacts with cocoapods. If you can't downgrade cocoapods, strive downgrading react native. Sucky temp answer however till we get updates I'm undecided what else to counsel. @dnkoutso If there is no podspec file current in my Local Podspecs directory, do I add one manually? I might copy the file from the appcenter node_module folder. @dnkoutso after operating rm -rf Pods/ && pod set up from my ios folder I obtain the identical issue. It seems really likely you are appropriate that this can be a ReactNative problem. Check /Users/connormullins/Sonder/ios/Pods/Local Podspecs/appcenter.podspec.json and see if the file is current. Browse other questions tagged ios ruby xcode react-native cocoapods or ask your own query. I am attempting to update the react native utility from 0.59 to 0.64, it is in 0.59, it permits to do pod set up. A yarn remove / yarn add of just appcenter works fantastic although. For what it is price, I reinitialized my project and it solved this issue and some other issues I was having. I know it's annoying to do, however my project had been around since RN v0.58 so there was most likely some issues I missed when performing updates to newer RN variations. Integrating shopper project Pod set up complete! There are 60 dependencies from the Podfile and fifty two complete pods installed. Appcenter was not put in and no pod lockfile was generated. Sign up for a free GitHub account to open a difficulty and get in contact with its maintainers and the neighborhood. As of React Native 0.60, the command use_native_modules! Handles including the third get together pods into your Podfile. You shouldn't need to, CocoaPods manages this folder.
I anticipated CocoaPods to successfully set up the appcenter pod. Not exactly sure what has modified in CocoaPods between 1.7.x and 1.eight.x that could possibly be inflicting the difficulty. It's possible that this could be a combination of React Native 0.sixty one modifications and 1.8.x of CocoaPods. I give it a small chance its a CocoaPods bug or a bug that's exposed into CocoaPods from RN. This thus far appears to be an RN upgrade concern and never a CocoaPods issue. Unless you'll be able to provide an a sample with out RN that demonstrates the problem. We are unable to diagnose an issue with the given information.
