when I try to add google mobile ads sdk to my file, there comes out some problems.
when i start install:
pic1
there is nothing wrong here, but when i run the app with xcode, i got a lot of error:
pic2
i don't know how to fix that ...... if anyone could help me ? thanks!!!!!!
Open your old project(without Google-Mobile-Ads-SDK framework), I think it was working(compiling & running) properly. Now add Google-Mobile-Ads-SDK pod line in the project's pod file and install pod by --no-repo-update in the terminal.
pod install --no-repo-update
I have been looking up on every website that had a similar/identical to this specific issue for Xcode of earlier version errors and I have tried everything and nothing has worked. I have cleaned and then tried to build the project but that hasn't worked.
The terminal shows that the firebase pod has been successfully installed but when try to import firebase the xcode says there is no such module Firebase
Then I tried to use adding the framework manually but when I try to build then Xcode says framework not found firebasecore .
I am stuck there ..what can I do next?
Comment all pods in pod file, then install only
pod 'Firebase/Analytics'
pod 'Firebase/Messaging'
For firebase notifications, because some time xcode do not install frameworks of pod files.
Open your pod file from project directory and add this
pod 'Firebase/Core'
then go to terminal and install pod again
pod install
after that make sure you build your project (⌘+B) before use.
Make sure you are opening .xcworkspace file from project directory.
I've upgraded React Native from 54.4 to 57.7 and whenever I try to run the app and launch simulator, the build works but I'm getting an Undefined is not an object (evaluating 'RNBranch.STANDARD EVENT ADD_TO_CART') error.
These are the things i've done:
reinstalled cocoa pods sudo gem install cocoapods
removed pods pod deintegrate /Users/cam/myapp/ios/Hooch.xcodeproj
I cleaned then installed pod clean and pod install
I've gone to my podfile, and added pod "react-native-branch", path: "../node_modules/react-native-branch"
pod "Branch-SDK", path: "../node_modules/react-native-branch/ios"
I've gone to the BranchEvent.js and removed all commerce events, and gone to index.js and removed the variables but no luck.
I can't figure out if this is a pods issue or a branch issue and nothing else I can think of seems to be working.
Anyone have any thoughts on what it could be?
I am new in IOS development and git. I am having a problem after merging my local repo to the dev repo. After merging when I build the project I get an error in the Xcode that says, "The sandbox is not in sync with the Podfile.lock. Run 'pod install' or update your CocoaPods installation."
Build Error
I searched about this and tried the usual solution reinstalling the pods. But executing
pod install
I get another error in terminal that says
Terminal Error
At this point I tried deleting the files associated with the "FTPopOverMenu" pod and reinstalling with pod install. The error doesn't go away. Also, I tried solving it in this way - Error:“The sandbox is not in sync with the Podfile.lock…” after installing RestKit with cocoapods
But both error in the Xcode and in the terminal still remains. I'm new to IOS and Git. I really don't understand what is really happening here.
As per my guess you are working on an old project means which is already developed in Xcode 8 series and now you are working with latest Xcode and you have updated the code accordingly.
So just do the below steps:
"pod deintegrate"
"pod install"
"pod update" (if it is necessary so do it else if you have all latest pod so don't use it.)
It will remove all old cocoapods traces.
OR Alternate way to do it (Temp Work Around)
Remove that cocoa pod temporary, after all your work finish add to your project and give a try cause in my case it is the only work around i have that worked.
In my case pod repos were outdated, solved with pod repo update
if #Ravi Panchal's answer can't solve your problem, it may be your pod repo is out dated
Solution:
pod install --repo-update
First, check your Podfile.lock and make sure no conflict with the spec constraints.
I encounter this issue with strange pod dependency, and solve it by
1. remove Podfile.lock
2. pod install again
It just work like magic. I think it is a bug that cocoapods cannot solve this kind of constraints in Podfile.lock. Remove the old Podfile.lock can make it apply the new rule easily.
please check your podfile and update the platform to the appropriate version number
platform :ios, '11.0'
In my case it worked after I changed iOS version from 8.0 to 9.0 in Target (not Project) settings >> General >> Deployment Info
In .podfile
changed the iOS version
platform :ios, '13.0' // Warning change by your desired
It worked
I had the same issue with FIRMessaging from cocoapods. I solved the issue by doing like following steps
Remove FTPopOverMenu from your podfile which can find in your project folder.
Open terminal and run pod install. You can see in terminal that FTPopOverMenu will be removing from your pods.
Now, again open your podfile and write this pod 'FTPopOverMenu'. Run pod install in terminal.
The error will go away from terminal.
if you are facing this error in Flutter CocoaPods could not find compatible versions for pod
increase your minimum deployments
cd ios and then rm -rf Pods/ Podfile.lock ; pod install
flutter build ios
I fixed by a change to dynamic pod version.
And delete file Podfile.lock
Please check the line below in your Podfile. Please make sure it is commented. it works for me.
platform :ios, '9.0'
I have an answer regarding this in the thread already. But this time my scenario was different. My co-worker accidentally updated the cocoa version from the stable to a beta version, while I was using the lower stable version. I wasn't interested using the beta version, so I didn't update.
As deleting podfile.lock is dangerous which leads to removing the Cocoapods traces, I just opened podfile.lock in editors like Sublime Text, and downgraded the pod which is causing the problem.
Look at the iOS Deployment Target, make it 11.0 and then do
pod install
and it will be fixed
Its frustrating seeing this error every time i use cocoa-pods. The only thing that works with cocoa-pods is 'Firebase SDK' but when i install any other framework such as JSQMessages or Eureka forms or any other framework i got an error 'No such a module" ... Its not the first time I work with these frameworks I did before and it was working correctly in fact I still got my previous projects installed with JSQMesgs, eurka..etc and its working fine till now. For the new projects it doesn't work/import in xcode anymore it is frustrating that I can't run it with this error ... not sure if its xcode or the cocopods .. I have tried instaling using terminal then uninstall and reinstall again with cocoapods application. I cleaned my build, change deployment target several times, and nothing worked so please if any one could share the same problems faced or advice me on how to avoid them or any alternatives to cocoapods.
deployment target 10.3 my xcode version 8.3.3 swift 3 macOS Sierra 10.12.5
# Uncomment the next line to define a global platform for your project
# platform :ios, '9.0'
target 'FinalProject' do
# Comment the next line if you're not using Swift and don't want to use dynamic frameworks
use_frameworks!
# Pods for FinalProject
pod 'Firebase/Core'
pod 'Firebase'
pod 'FirebaseAuth'
pod 'FirebaseDatabase'
pod 'FirebaseStorage'
pod 'ProgressHUD'
pod 'JSQMessagesViewController'
pod 'Eureka'
pod 'Former'
pod 'SwiftForms'
end
Please help.
Build the project.
The Xcode editor doesn't recognize modules coming from the Pods until after they've been built for the first time.
If that doesn't work for you, please share a screen shot of the issue, or even better, a reproducible example.
I had the same problem trying to work with SwiftyStoreKit.
I finally manage to solve my problem and hope that sharing the solution will help someone.
I tried everything was suggested until I realised that I was loading the pod in the wrong target, (in the pod file itself.)
After I repaired the pod file, run again pod install, and, voila, the xcode recognised the pod.