Please test CocoaPods 0.14 compatibility

166 views
Skip to first unread message

Eloy Durán

unread,
Sep 26, 2012, 5:26:01 AM9/26/12
to rubym...@googlegroups.com
Hi,

Yesterday I pushed a few motion-cocoapods compatibility patches. I’ve already heard from one user that it works, but I would like to hear from a few more, to ensure there aren’t any big issues that needs to be resolved first.

You can test it out by adding the following to your Gemfile (in case you use Bundler):

gem "motion-cocoapods", :git => "git://github.com/HipByte/motion-cocoapods.git"

- Eloy

Joffrey Jaffeux

unread,
Sep 26, 2012, 6:03:09 AM9/26/12
to rubym...@googlegroups.com
Hi,


Using your patch gave me a lot of errors :

- Your RubyGems version (1.3.6) is too old, please update with: `gem update --system` ????? gem -v gives 1.8.24
- [DEPRECATED] `dependency' is deprecated (use `pod') (doesn't really matter but worth mentioning I guess as I'm using pod in my rakefile)
- Here is the result of verbose rake :

Resolving dependencies of: 

Finding added, modified or removed dependencies:
  - AFNetworking
  - Facebook-iOS-SDK
  - MBProgressHUD
  - NanoStore

Resolving dependencies for target `default' (iOS 6.0):
  - NanoStore (= 2.1.4)
  - AFNetworking (from `https://github.com/lldong/AFNetworking.git') # forked repo to add a header
  - NanoStore (= 2.1.4)
  - Facebook-iOS-SDK (= 3.0.8)
    - SBJson (= 2.2.3)
  - MBProgressHUD (= 0.5)

Installing dependencies

-> Using AFNetworking (0.10.0)

-> Using Facebook-iOS-SDK (3.0.8)

-> Using MBProgressHUD (0.5)

-> Using NanoStore (2.1.4)

-> Using SBJson (2.2.3)

Generating support files

- Generating xcconfig file at `/project/xxx/vendor/Pods/Pods.xcconfig'
- Generating prefix header at `/project/xxx/vendor/Pods/Pods-prefix.pch'
- Generating copy resources script at `/project/xxxs/vendor/Pods/Pods-resources.sh'
- Running post install hooks
- Writing Xcode project file to `/project/xxx/vendor/Pods/Pods.xcodeproj'
- Writing lockfile in `/project/xxx/vendor/Podfile.lock'


- And then I have an error in the bride I guess as it doesn't recognize anymore one of AFNetworking method : "bjective-C stub for message `setReachabilityStatusChangeBlock:' type `v@:@?' not precompiled. Make sure you properly link with the framework or library that defines this message." Was perfectly working before.

Eloy Durán

unread,
Sep 26, 2012, 6:14:41 AM9/26/12
to rubym...@googlegroups.com
Thanks for testing, Joffrey!

> - Your RubyGems version (1.3.6) is too old, please update with: `gem update --system` ????? gem -v gives 1.8.24

So it printed this message but did continue with the installation? That's weird, it should have exited: https://github.com/CocoaPods/CocoaPods/blob/master/lib/cocoapods.rb#L9.

Can you print Gem::VERSION from your Rakefile to be sure which rubygems version is being loaded?

> - [DEPRECATED] `dependency' is deprecated (use `pod') (doesn't really matter but worth mentioning I guess as I'm using pod in my rakefile)

That is very weird indeed. Could you check the Gemfile.lock file to see which version of CocoaPods is being used exactly?

> - And then I have an error in the bride I guess as it doesn't recognize anymore one of AFNetworking method : "bjective-C stub for message `setReachabilityStatusChangeBlock:' type `v@:@?' not precompiled. Make sure you properly link with the framework or library that defines this message." Was perfectly working before.

Did you see wether or not motion-cocoapods generated a new Pods.bridgesupport file? And is that method indeed missing from the BS file?

Thanks for your time,
Eloy

Joffrey Jaffeux

unread,
Sep 26, 2012, 6:29:32 AM9/26/12
to rubym...@googlegroups.com
-1)
"1.8.24"

-2) 
motion-cocoapods (1.1.4)
      cocoapods (>= 0.9.1)

cocoapods (0.13.0)
      activesupport (~> 3.2.6)
      colored (~> 1.2)
      escape (~> 0.0.4)
      faraday (~> 0.8.1)
      json (~> 1.7.3)
      octokit (~> 1.7.0)
      open4 (~> 1.3.0)
      rake (~> 0.9.0)
      xcodeproj (>= 0.3.0)

3) Yep Pods.bridesupport is generated and I can find the method in it : 

<method selector='setReachabilityStatusChangeBlock:'>
<arg declared_type='void (^)(AFNetworkReachabilityStatus)' function_pointer='true' name='block' index='0' type='@?'>
<arg declared_type='AFNetworkReachabilityStatus' type='i'/>
<retval declared_type='void' type='v'/>
</arg>

Joffrey Jaffeux

unread,
Sep 26, 2012, 6:31:22 AM9/26/12
to rubym...@googlegroups.com
Hum.... Didn't change anything... and for some reason it's now working...

I still have theses errors though :

$ rake
Your RubyGems version (1.3.6) is too old, please update with: `gem update --system`
[DEPRECATED] `dependency' is deprecated (use `pod')

But no more bridge error, and app is working.

Eloy Durán

unread,
Sep 26, 2012, 6:35:28 AM9/26/12
to rubym...@googlegroups.com
Ok, it appears you are still using the old versions of motion-cocoapods and CocoaPods. I should have been clearer in my explanation of how to test the latest. After adding the git url you have to run: $ bundle update

Could you try it with that?

--
 
 
 

Joffrey Jaffeux

unread,
Sep 26, 2012, 6:36:32 AM9/26/12
to rubym...@googlegroups.com
Sorry but I've already done that several times

Joffrey Jaffeux

unread,
Sep 26, 2012, 6:39:12 AM9/26/12
to rubym...@googlegroups.com
As bundle update is not changing anything... I have deleted Gemfile.lock and then ran bundle update, it seems to do the trick :

    cocoapods (0.14.0)
      activesupport (~> 3.2.6)
      colored (~> 1.2)
      escape (~> 0.0.4)
      faraday (~> 0.8.1)
      json (~> 1.7.3)
      octokit (~> 1.7)
      open4 (~> 1.3.0)
      rake (~> 0.9.0)
      xcodeproj (>= 0.3.3)

  specs:
    motion-cocoapods (1.5.0)
      cocoapods (>= 0.14.0)


Still having the same errors though.

Eloy Durán

unread,
Sep 27, 2012, 5:49:00 AM9/27/12
to rubym...@googlegroups.com
I’m unfortunately unable to reproduce this, nor have others reported this. If you do happen to get to the bottom of it, please let us know on the motion-cocoapods repo.

Thanks,
Eloy

--
 
 
 

Joffrey Jaffeux

unread,
Sep 27, 2012, 6:42:50 AM9/27/12
to rubym...@googlegroups.com
Sure.
Reply all
Reply to author
Forward
0 new messages