Incorrect version of cocoapods

#1

In our Podfile.lock we specify Cocoapods 1.10.0.

I see this in the log after a build…

Determining required cocoapods version
Searching for Podfile.lock
Found Podfile.lock: /Users/vagrant/git/Podfile.lock
Required CocoaPods version (from Podfile.lock): 1.9.3

Where is it getting 1.9.3 from?

0 Likes

#2

Hi @murray
Thank you for reaching out to Bitrise.
The Podfile.lock file on your local machine where you specify the cocoapods version to 1.10.0?
On Bitrise VM you need to install the cocoapods version 1.10.0 via script step if you want to use the same version as your local machine.

Thanks
Chaitanya

0 Likes

#3

Thank you. But for my own understanding what Podfile.lock is it referring to in the log?

0 Likes

#4

Also, I received an email from thi.nguyen asking me to enable bitrise support and I’ve done that. I think this is the url you need: https://app.bitrise.io/app/7b9f2af97e3c931a/workflow_editor#!/workflows?workflow_id=stg

0 Likes

#5

Chaitanya, I looked into your suggestion but I found this and it seems to contradict your advice.

https://www.bitrise.io/integrations/steps/cocoapods-install

This is the way I hope it works. I want to specify the version of cocoapods once in Podfile.lock. If move to a newer version I only want to change it in Podfile.lock, I hope I don’t have to, in addition, install it here at bitrise.

The problem is, from the log I included above, I don’t know what Podfile.lock it’s looking in to find 1.9.3. For sure I have 1.10.0 in our Podfile.lock.

0 Likes

#6

Hi @murray
Can you please send a copy of your podfile.lock file so that we can take a look inside of your file?

Thanks
Chaitanya

0 Likes

#7

Tried to upload, it says that file type is not authorized. So here are the contents of our Podfile.lock:

PODS:

  • Alamofire (5.2.2)
  • GoogleWebRTC (1.1.31999)
  • InputBarAccessoryView (5.1.0):
    • InputBarAccessoryView/Core (= 5.1.0)
  • InputBarAccessoryView/Core (5.1.0)
  • Kingfisher (5.15.0):
    • Kingfisher/Core (= 5.15.0)
  • Kingfisher/Core (5.15.0)
  • MarqueeLabel (4.0.2)
  • NotificationBannerSwift (3.0.2):
    • MarqueeLabel (~> 4.0.0)
    • SnapKit (~> 5.0.0)
  • NYTPhotoViewer (5.0.3):
    • NYTPhotoViewer/AnimatedGifSupport (= 5.0.3)
    • NYTPhotoViewer/Core (= 5.0.3)
  • NYTPhotoViewer/AnimatedGifSupport (5.0.3):
    • NYTPhotoViewer/Core
    • PINRemoteImage/iOS (~> 3.0.0)
    • PINRemoteImage/PINCache
  • NYTPhotoViewer/Core (5.0.3)
  • PINCache (3.0.1):
    • PINCache/Arc-exception-safe (= 3.0.1)
    • PINCache/Core (= 3.0.1)
  • PINCache/Arc-exception-safe (3.0.1):
    • PINCache/Core
  • PINCache/Core (3.0.1):
    • PINOperation (~> 1.2.0)
  • PINOperation (1.2)
  • PINRemoteImage/Core (3.0.1):
    • PINOperation
  • PINRemoteImage/iOS (3.0.1):
    • PINRemoteImage/Core
  • PINRemoteImage/PINCache (3.0.1):
    • PINCache (~> 3.0.1)
    • PINRemoteImage/Core
  • ProgressHUD (13.4)
  • Realm (5.3.5):
    • Realm/Headers (= 5.3.5)
  • Realm/Headers (5.3.5)
  • RealmSwift (5.3.5):
    • Realm (= 5.3.5)
  • SideMenu (6.4.9)
  • SnapKit (5.0.1)
  • Starscream (3.1.1)
  • SwiftDate (6.2.0)
  • SwiftyJSON (5.0.0)

DEPENDENCIES:

  • Alamofire
  • GoogleWebRTC
  • InputBarAccessoryView
  • Kingfisher
  • NotificationBannerSwift
  • NYTPhotoViewer
  • ProgressHUD
  • RealmSwift
  • SideMenu
  • Starscream (= 3.1.1)
  • SwiftDate
  • SwiftyJSON

SPEC REPOS:
trunk:
- Alamofire
- GoogleWebRTC
- InputBarAccessoryView
- Kingfisher
- MarqueeLabel
- NotificationBannerSwift
- NYTPhotoViewer
- PINCache
- PINOperation
- PINRemoteImage
- ProgressHUD
- Realm
- RealmSwift
- SideMenu
- SnapKit
- Starscream
- SwiftDate
- SwiftyJSON

SPEC CHECKSUMS:
Alamofire: 814429acc853c6c54ff123fc3d2ef66803823ce0
GoogleWebRTC: b39a78c4f5cc6b0323415b9233db03a2faa7b0f0
InputBarAccessoryView: 19953f486a23e846e9487099f92bbe3456e46ce5
Kingfisher: 1acb67597a520c2d0310677e66d6e0af455ef757
MarqueeLabel: f762aa681ae201f66c1d511858b171f75d83013a
NotificationBannerSwift: 713e20f21b6105f4a36a00e5d9fa414a930d3d8e
NYTPhotoViewer: 8d8e101da2127a66ddb1ffe0f36a58d62daaa92d
PINCache: ee3c4abadd09970a61cdda0cfc345e69a3d75b26
PINOperation: 3a967a927e7867e61976c6cc23e5770416449fbc
PINRemoteImage: 3b7cedb118c2d357f87e9eabc7c81ba0202cb236
ProgressHUD: 137a7fc677487c5581668f4490563124fb35c232
Realm: 2b52fcc86fc0ed3d75a56ac0eb1e73c4f1a60e16
RealmSwift: a6ea2ea561039fc3833c08dec81371a9a3bb5ca6
SideMenu: 8ef57a3cfc024a2d3fc1c036c7fe98537baec9e0
SnapKit: 97b92857e3df3a0c71833cce143274bf6ef8e5eb
Starscream: 4bb2f9942274833f7b4d296a55504dcfc7edb7b0
SwiftDate: d117c3eb6beed72e47d3f4d1e3bc63fa1e66d7c3
SwiftyJSON: 36413e04c44ee145039d332b4f4e2d3e8d6c4db7

PODFILE CHECKSUM: d5867de833721fa1bd7346bdebba87c5fe755a98

COCOAPODS: 1.10.0

0 Likes

#8

Hello @chaitanya.tanna. I think I know the problem. When I was given access to bitrise I saw 1 app on our dashboard. I am new to the company and new to bitrise so I never thought for a moment that that app wasn’t the one I was working on. But it is indeed not the right app. That is almost certainly the root of this problem.

0 Likes

#9

Dang. I have indeed been working on the wrong app! I apologize for the churn on this and thank you for your efforts. I’m going to mark this as resolved. If it ends up that there is an issue with this app I’ll open a new ticket (and hopefully have all the facts straight).

0 Likes

closed #10

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.

0 Likes