-
Notifications
You must be signed in to change notification settings - Fork 283
App Not Using theMost Recent Version of Cocoapods #383
Comments
There are issues for letting the CocoaPods app use different versions of the CLI #157 - but it's likely that it's only going to come from an OSS contributor now as I don't have the time nor general inclination to add it myself. I do plan on shipping a 1.2.1 over the weekend though, I can only do it on a specific computer due to #374 |
Ok, good to know. If that is the case, mabye the 'check for updates' button that displays with the 'Your Podfile.lock was generated using a newer version' banner should be removed or re-worded. Based on the context, I would expect it to go out and get the latest version of the cocoapods gem. If it doesn't do that, the button just ends up being confusing. |
any updates on when the cocoapods app can get an update? thanks? |
The computer that I use to deploy hasn't been booting up when I try lately, so the releases are taking longer than I'd like. |
Have you ever considered using a VM instead of a real computer? macOS can run within a VM as long as the host system also is macOS. Should be possible with Oracle's VirtualBox, which is available for free. I once even got macOS to run on a different host system (I just wanted to see if that's even possible) but that's not allowed (violates Apple's license agreement that demands macOS must run on Apple hardware) and it was only possible by first starting a bootloader from a CD image and then booting macOS (booting macOS directly was hanging the VM). |
Considered yep. Could also deploy via CI. Just don't really have the time to give to it. Happy for someone to take a look 👍 |
I got this updated to 1.4.0 |
I had previously installed the most recent release version of the cocoapods command line tool (1.2.1) and used it successfully. I decided to try out the App with the same project today, and I got a notification saying that my Podfile.lock was generated with a newer version. I tried doing an install anyway and sure enough, the app was using version 1.2.0.
Is this expected behaviour? If so, is there any way to configure the app to use the version of cocoapods I already have installed rather than the bundled version?
The text was updated successfully, but these errors were encountered: