Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Wrong error message when pod install failed due to spec not found in local repo clone. #6395

Closed
1 task done
ainopara opened this issue Jan 11, 2017 · 4 comments
Closed
1 task done
Labels
s1:awaiting input Waiting for input from the original author s3:detailed Issues with in-depth explanations and examples that make it easier to troubleshoot t2:defect These are known bugs. The issue should also contain steps to reproduce. PRs welcome!

Comments

@ainopara
Copy link

ainopara commented Jan 11, 2017

Before you start, are you using the latest CocoaPods release?
A lot changes with Xcode releases that are not backwards compatible.

Not an issue about the CocoaPods command line app? Please file an issue in the appropriate repo - https://github.com/CocoaPods
Issues are for feature requests, and bugs; questions should go to Stack Overflow

Using CocoaPods <= 0.39: http://blog.cocoapods.org/Sharding/

Using Xcode 8: Requires CocoaPods 1.1.0 or above.

Issue with Nanaimo not loading:
Please run [sudo] gem uninstall nanaimo and remove all but the latest version.

Linting a Swift 2.3 Pod: You need to add a .swift-version file or the
argument --swift-version=VERSION, see the CHANGELOG.

Report

What did you do?

I added .travis.yml to my open source project, travis CI failed when it was running pod install.
it say:

[!] Due to the previous naïve CocoaPods resolver, you were using a pre-release version of `ReactiveCocoa`, without explicitly asking for a pre-release version, which now leads to a conflict. Please decide to either use that pre-release version by adding the version requirement to your Podfile (e.g. `pod 'ReactiveCocoa', '= 5.0.0-rc.1'`) or revert to a stable version by running `pod update ReactiveCocoa`.

when my Podfile writes

pod 'ReactiveCocoa', '~> 5.0.0-rc.1'

What did you expect to happen?

The actually reason for the failure is pod repo needs update (i.e. there is no podspec for the 5.0.0-rc.1 version in travis CI's image), so CocoaPods should tell me there is no corresponding podspec in local clone of CocoaPods/Spec repo rather than asking for me to change Podfile.

What happened instead?

As said above, it say:

[!] Due to the previous naïve CocoaPods resolver, you were using a pre-release version of `ReactiveCocoa`, without explicitly asking for a pre-release version, which now leads to a conflict. Please decide to either use that pre-release version by adding the version requirement to your Podfile (e.g. `pod 'ReactiveCocoa', '= 5.0.0-rc.1'`) or revert to a stable version by running `pod update ReactiveCocoa`.

CocoaPods Environment

I have tried CocoaPods 1.1.1 and CocoaOods 1.2.0.beta.3, and they have same issue.

Project that demonstrates the issue

travis CI Log: failure
travis CI Log: pod install succeed when pod repo update executed

@benasher44 benasher44 added the t2:defect These are known bugs. The issue should also contain steps to reproduce. PRs welcome! label Jan 11, 2017
@benasher44
Copy link
Member

@ainopara thanks for bringing this up and attaching logs! This definitely sounds like bug. I've labeled this issue appropriately, and hopefully someone can look at fixing this.

@benasher44 benasher44 added the s3:detailed Issues with in-depth explanations and examples that make it easier to troubleshoot label Mar 12, 2017
@stale stale bot added the s1:awaiting input Waiting for input from the original author label Jun 11, 2017
@stale
Copy link

stale bot commented Jun 11, 2017

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates.

@stale stale bot closed this as completed Jul 13, 2017
@stale
Copy link

stale bot commented Jul 13, 2017

This issue will be auto-closed because there hasn't been any activity for a few months. Feel free to open a new one if you still experience this problem 👍

@DenTelezhkin
Copy link

This definitely still happens on CocoaPods 1.3.1. What's even more confusing, is error message suggests to specifically set beta release in Podfile, even if it IS specified explicitly in Podfile.

Only after googling and seeing this issue i understood that local specs repo simply does not have this prerelease podspec and i need to run pod repo update

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
s1:awaiting input Waiting for input from the original author s3:detailed Issues with in-depth explanations and examples that make it easier to troubleshoot t2:defect These are known bugs. The issue should also contain steps to reproduce. PRs welcome!
Projects
None yet
Development

No branches or pull requests

3 participants