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

The cocoapods version is 1.7.4, and when I execute the pod trunk command, I report the following error: #142

Open
melo30 opened this issue Dec 6, 2019 · 16 comments

Comments

@melo30
Copy link

melo30 commented Dec 6, 2019

Command

/Users/chencheng/.rvm/rubies/ruby-2.4.1/bin/pod trunk push MJBUserInfoKit.podspec --allow-warnings --use-libraries

Report

  • What did you do?

  • What did you expect to happen?

  • What happened instead?

Stack

   CocoaPods : 1.7.4
        Ruby : ruby 2.4.1p111 (2017-03-22 revision 58053) [x86_64-darwin17]
    RubyGems : 2.7.7
        Host : Mac OS X 10.15.1 (19B88)
       Xcode : 11.2.1 (11B53)
         Git : git version 2.21.0
Ruby lib dir : /Users/chencheng/.rvm/rubies/ruby-2.4.1/lib
Repositories : master - https://github.com/CocoaPods/Specs.git @ b515bbf3933f4f956141326a3352a3e393330998

Plugins

cocoapods-deintegrate : 1.0.4
cocoapods-plugins     : 1.0.0
cocoapods-search      : 1.0.0
cocoapods-stats       : 1.1.0
cocoapods-trunk       : 1.4.1
cocoapods-try         : 1.1.0

Error

NameError - uninitialized constant Pod::TrunkSource
/Users/chencheng/.rvm/gems/ruby-2.4.1@global/gems/cocoapods-trunk-1.4.1/lib/pod/command/trunk/push.rb:147:in `update_master_repo'
/Users/chencheng/.rvm/gems/ruby-2.4.1@global/gems/cocoapods-trunk-1.4.1/lib/pod/command/trunk/push.rb:69:in `run'
/Users/chencheng/.rvm/gems/ruby-2.4.1@global/gems/claide-1.0.2/lib/claide/command.rb:334:in `run'
/Users/chencheng/.rvm/gems/ruby-2.4.1@global/gems/cocoapods-1.7.4/lib/cocoapods/command.rb:52:in `run'
/Users/chencheng/.rvm/gems/ruby-2.4.1@global/gems/cocoapods-1.7.4/bin/pod:55:in `<top (required)>'
/Users/chencheng/.rvm/rubies/ruby-2.4.1/bin/pod:23:in `load'
/Users/chencheng/.rvm/rubies/ruby-2.4.1/bin/pod:23:in `<main>'

――― TEMPLATE END ――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――

[!] Oh no, an error occurred.

@listenzz
Copy link

listenzz commented Dec 6, 2019

Same problem with pod _1.6.1_ trunk push XX.podspec

@melo30
Copy link
Author

melo30 commented Dec 6, 2019

Same problem with pod _1.6.1_ trunk push XX.podspec

I suspect that this problem is caused by a mismatch between the pod version and the system version. My system version is 10.15.1. How about yours?

@listenzz
Copy link

listenzz commented Dec 6, 2019

@melo30 My system version is same as you.

@melo30
Copy link
Author

melo30 commented Dec 6, 2019

@melo30 My system version is same as you.

@listenzz I try to upgrade the pod version to 1.8.4, and there's another problem.Now I feel like I can only return the system version.

@dnkoutso
Copy link
Contributor

dnkoutso commented Dec 6, 2019

@igor-makarov is it possible cocoapods-trunk 1.4.1 not to be backwards compatible with 1.7.x and 1.6.x?

Seems like we discussed this here #132 previously.

@dnkoutso
Copy link
Contributor

dnkoutso commented Dec 6, 2019

I was not able to reproduce this. I need clear step-by-step instructions on how this issue can occur.

@igor-makarov
Copy link
Contributor

Seems like it's incompatible, but not from the PR you mentioned:

trunk = sources_manager.find_or_create_source_with_url(Pod::TrunkSource::TRUNK_REPO_URL)

The PR that caused this:

#135

@dnkoutso
Copy link
Contributor

dnkoutso commented Dec 6, 2019

Ouch, is it a fix we can have in cocoapods-trunk and release 1.4.2?

@igor-makarov
Copy link
Contributor

Think so, just need to that the symbol exists I think...

@dnkoutso
Copy link
Contributor

dnkoutso commented Dec 6, 2019

sgtm, wonder if we can have a test for it too.

@dnkoutso
Copy link
Contributor

dnkoutso commented Dec 6, 2019

Moving this issue from cocoapods/cocoapods to cocoapods/cocoapods-trunk

@dnkoutso dnkoutso transferred this issue from CocoaPods/CocoaPods Dec 6, 2019
@igor-makarov
Copy link
Contributor

Probably could add a different Gemfile to the Travis matrix

@melo30
Copy link
Author

melo30 commented Dec 7, 2019

@dnkoutso @igor-makarov So what you're saying is that the only way to solve this problem is to wait until the release of version 1.4.2 of cocoapod-trunk😂

@igor-makarov
Copy link
Contributor

Or you could upgrade CocoaPods to >= 1.8.0.

Or downgrade cocoapods-trunk plugin. That's also a solution.

@melo30
Copy link
Author

melo30 commented Dec 9, 2019

Or you could upgrade CocoaPods to >= 1.8.0.

Or downgrade cocoapods-trunk plugin. That's also a solution.

I solved the problem by downgrade cocoapods-trunk plugin to 1.3.1 , thank you very much!

@melo30
Copy link
Author

melo30 commented Dec 9, 2019

Or you could upgrade CocoaPods to >= 1.8.0.

Or downgrade cocoapods-trunk plugin. That's also a solution.

But, if i upgrade CocoaPods to >= 1.8.0, Can't solve this problem. First of all, it will report the wrong "CDN: trunk Repo update failed". Then I looked at the common online solution: 1.podfile add source 'https://github.com/CocoaPods/Specs.git' 2.pod repo remove trunk . And then when I went to execute 'pod trunk push ....' , It's going to help me create trunk repo again. And then repeat the mistake:CDN: trunk Repo update failed... Do you know why this is?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants