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

Demo app can't compile #51

Closed
markfulo opened this issue Mar 16, 2015 · 10 comments
Closed

Demo app can't compile #51

markfulo opened this issue Mar 16, 2015 · 10 comments

Comments

@markfulo
Copy link

These are the errors:

diff: /../Podfile.lock: No such file or directory
diff: /Manifest.lock: No such file or directory
error: The sandbox is not in sync with the Podfile.lock. Run 'pod install' or update your CocoaPods installation.

I also tried to update the pod but it also has an error:

NoMethodError - undefined method []' for #<Xcodeproj::Project::Object::PBXFileReference:0x007f8249322260> /Library/Ruby/Gems/2.0.0/gems/cocoapods-0.36.0/lib/cocoapods/project.rb:186:inblock in add_file_reference'
/System/Library/Frameworks/Ruby.framework/Versions/2.0/usr/lib/ruby/2.0.0/pathname.rb:263:in block in each_filename' /System/Library/Frameworks/Ruby.framework/Versions/2.0/usr/lib/ruby/2.0.0/pathname.rb:263:ineach'
/System/Library/Frameworks/Ruby.framework/Versions/2.0/usr/lib/ruby/2.0.0/pathname.rb:263:in each_filename' /Library/Ruby/Gems/2.0.0/gems/cocoapods-0.36.0/lib/cocoapods/project.rb:184:inadd_file_reference'
/Library/Ruby/Gems/2.0.0/gems/cocoapods-0.36.0/lib/cocoapods/installer/file_references_installer.rb:168:in block (2 levels) in add_file_accessors_paths_to_pods_group' /Library/Ruby/Gems/2.0.0/gems/cocoapods-0.36.0/lib/cocoapods/installer/file_references_installer.rb:166:ineach'
/Library/Ruby/Gems/2.0.0/gems/cocoapods-0.36.0/lib/cocoapods/installer/file_references_installer.rb:166:in block in add_file_accessors_paths_to_pods_group' /Library/Ruby/Gems/2.0.0/gems/cocoapods-0.36.0/lib/cocoapods/installer/file_references_installer.rb:162:ineach'
/Library/Ruby/Gems/2.0.0/gems/cocoapods-0.36.0/lib/cocoapods/installer/file_references_installer.rb:162:in add_file_accessors_paths_to_pods_group' /Library/Ruby/Gems/2.0.0/gems/cocoapods-0.36.0/lib/cocoapods/installer/file_references_installer.rb:104:inblock in add_resources'
/Library/Ruby/Gems/2.0.0/gems/cocoapods-0.36.0/lib/cocoapods/user_interface.rb:110:in message' /Library/Ruby/Gems/2.0.0/gems/cocoapods-0.36.0/lib/cocoapods/installer/file_references_installer.rb:102:inadd_resources'
/Library/Ruby/Gems/2.0.0/gems/cocoapods-0.36.0/lib/cocoapods/installer/file_references_installer.rb:38:in install!' /Library/Ruby/Gems/2.0.0/gems/cocoapods-0.36.0/lib/cocoapods/installer.rb:486:ininstall_file_references'
/Library/Ruby/Gems/2.0.0/gems/cocoapods-0.36.0/lib/cocoapods/installer.rb:130:in block in generate_pods_project' /Library/Ruby/Gems/2.0.0/gems/cocoapods-0.36.0/lib/cocoapods/user_interface.rb:49:insection'
/Library/Ruby/Gems/2.0.0/gems/cocoapods-0.36.0/lib/cocoapods/installer.rb:128:in generate_pods_project' /Library/Ruby/Gems/2.0.0/gems/cocoapods-0.36.0/lib/cocoapods/installer.rb:96:ininstall!'
/Library/Ruby/Gems/2.0.0/gems/cocoapods-0.36.0/lib/cocoapods/command/project.rb:71:in run_install_with_update' /Library/Ruby/Gems/2.0.0/gems/cocoapods-0.36.0/lib/cocoapods/command/project.rb:101:inrun'
/Library/Ruby/Gems/2.0.0/gems/claide-0.8.1/lib/claide/command.rb:312:in run' /Library/Ruby/Gems/2.0.0/gems/cocoapods-0.36.0/lib/cocoapods/command.rb:46:inrun'
/Library/Ruby/Gems/2.0.0/gems/cocoapods-0.36.0/bin/pod:44:in <top (required)>' /usr/bin/pod:23:inload'
/usr/bin/pod:23:in `

'

@lazerwalker
Copy link
Member

Hmm. Wouldn't surprise me if that's an issue related to all of the recent changes in CocoaPods and the release of 0.36. I'm hoping I'll have the time to check this out soon – thanks!

@markfulo
Copy link
Author

Alright! hopefully you can fix it, Thanks! 👍

@lazerwalker
Copy link
Member

This is potentially a CocoaPods 0.36 issue – see the reference directly above this comment for #3195.

@kylef
Copy link

kylef commented Mar 30, 2015

@lazerwalker This appears to be a problem with your pod spec, you have the same resources used across multiple resource and resource bundles.

Commenting out ss.resources = 'IntentKit/IntentKit-Localizations.bundle' from your pod spec will make it work.

You'll notice that 'IntentKit' => 'IntentKit/{**/*.strings,Images/*.png}' matches the .string files inside the IntentKit/IntentKit-Localizations.bundle so they are included multiple times.

@lazerwalker
Copy link
Member

@kylef that (sadly!) doesn't seem to be solving the problem 🙀

I commented out that single line (and after a once-over of the rest of the podspec, it looks like there shouldn't be any other such duplications) and I'm still getting the exact same error / stack trace with a clean pod install.

@lazerwalker
Copy link
Member

Nope, hold the phone. The local pod / podspec was getting cached – after inserting foot firmly in mouth, seems to be working great.

Thanks!

@lazerwalker
Copy link
Member

@markfulo Before I push a new build, any chance you can confirm this fix by checking out HEAD?

@markfulo
Copy link
Author

@lazerwalker, I have build it now and it's working. Thanks a lot! but there's seems to be 3 issues with the shell script:

  • find: 2/IntentKit/Apps: No such file or directory
  • find: 2/IntentKit/Images: No such file or directory
  • Command /bin/sh emitted errors but did not return a nonzero exit code to indicate failure

@lazerwalker
Copy link
Member

Sorry I hadn't gotten back to you about this. Did you ever figure it out?

I've been mucking around with the test project for code coverage stuff, and it seems to be working fine for me, but happy to help troubleshoot if you're still having issues.

@lazerwalker
Copy link
Member

Ping? Going to close this for now, but happy to reopen / help if you're still having issues.

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

3 participants