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

Already on GitHub? Sign in to your account

undefined method `copy_resources_script_path' for <Pod::PodTarget> #1157

Closed
dennisreimann opened this Issue Jul 1, 2013 · 7 comments

Comments

Projects
None yet
6 participants

It looks like the commit 363af1f broke some post_install hooks that were relying on the library representation being passed into the block. An example that breaks with the release of 0.21.0 (and its release candidates) from the HockeySDK-iOS podspec:

s.post_install do |library_representation|
    File.open(library_representation.copy_resources_script_path, 'a') do |file|
        file.puts "install_resource 'HockeySDK/Resources/HockeySDKResources.bundle'"
    end
end

The Mapbox iOS SDK seems to have this problem too: mapbox/mapbox-ios-sdk#265

Owner

fabiopelosin commented Jul 2, 2013

I can confirm the bug, in the last release the Pod target is being used instead of the aggregate target for the library representation. This is a serious bug which needs to be fixed ASAP. I already have implemented a partial fix (the issue is present also on the installer) and I might be able to complete and push it tonight.

Nice! 🍰

nejra commented Jul 3, 2013

I will also be very grateful if this is going to be fixed any time soon :) I'm having issues with MapBox SDK.

akaralar commented Jul 3, 2013

same here! having issues with MapBox 1.0.3

akaralar commented Jul 3, 2013

i update cocoapods with "gem update cocoapods", but it says there is nothing to update. when will this fix be available there? or can you point me as to how i will clone it from github?

subscribe to the issue akaralar.
How to upgrade to the Github?

@nullproduction nullproduction referenced this issue in nothirst/TICoreDataSync Jul 3, 2013

Closed

Problem with TICoreDataSync.podspec #67

Owner

alloy commented Jul 31, 2013

@akaralar @nullproduction Use gem install cocoapods instead.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment