Xcode Question posted in
Whether you're new to Xcode or an experienced developer, our archive has everything you need to know about this integrated development environment (IDE). From basic functionalities to advanced features, our archive covers a wide range of Xcode-related questions and answers. Browse our archive now and find solutions to your Xcode questions, and take your app development skills to the next level

Xcode – Terminal refusing to "pod update"

I searched all over but the closest answer is here Can't update pods to the latest version. However it did not work for me because I have no deprecated pods. And i cant leave a comment to ask someone about my case so I opened a new question.

I have no "specified version" and am using IOS 13 as the deployment target. Any ideas on how to update those pods? Thanks!

# platform :ios, '13.0'
target 'ChatApp' do
use_frameworks!

pod 'MessageKit'
pod 'JGProgressHUD'
pod 'RealmSwift'
pod 'SDWebImage'
# firebase pods
  pod 'Firebase/Analytics'
  pod 'Firebase/RemoteConfig'
  pod 'Firebase/Auth'
  pod 'FirebaseUI'
  pod 'Firebase/Database'
  pod 'Firebase/Storage'
  
# FaceBook Sign in pods
  pod 'FBSDKLoginKit'

#Google Sign in pods 
pod 'GoogleSignIn'
  
end

enter image description here

Tags:

3

Answers


  1. 0

    Run pod repo update to update Your local database.

    Login or Signup to reply.
  2. 0

    It’s because there are dependencies that need a specific version.

    For instance if we see your "outdated" pods, except for FBSDKLoginKit, they aren’t listed directly in your pod file list.

    Let’s have a look at your Podfile.lock.

    The listing is a such:

    - PodA
  - PodB

    Where PodA needs PodB, it’s by "indentation".

    You use FirebaseFirestore.
    We can see that even last version of
    FirebaseFirestore needs abseil at 0.20200225 (not the last version of it).

    You might say, "hey, I didn’t write pod FirebaseFireStore", that’s normal, you are needing it indirectly (with a little sort of your Podfile.lock):

    - FirebaseUI (9.0.0):
  - FirebaseUI/Firestore (= 9.0.0)
  - ...
- FirebaseUI/Firestore (9.0.0):
  - Firebase/Firestore
- FirebaseFirestore (1.19.0):
  - abseil/algorithm (= 0.20200225.0)
  - ...

    You use FirebaseUI, that needs FirebaseUI/Firestore, which needs Firebase/Firestore in version 1.19.0, that needs the abseil at that version.
    See the nightmare?

    It’s a nightmare to check, but you can do it yourself if needed, and find what the pod that is blocking the version of a pod. I just show an example.

    Now, you are building dependencies, so they need to find a common version where it all works, you can’t have different version really. Else we couldn’t know which one to use, the version 4.0.0 where all changed, or the version 1.0.0?

    Maybe cocoapods-graph (not tested) or cocoapods-dependency might give you a better idea:

    enter image description here

    Login or Signup to reply.
  3. 0

    Run pod repo update to update then also run pod install and check output

    Login or Signup to reply.
Please signup or login to give your own answer.

Back To Top
Search