Bower component download failures in CodeKit

Question

I downloaded the latest version of CodeKit (trial version 2.0 (16828)). It starts fine on my Mac Mini, but as soon as I try to download a component using Bower, it fails with the error: "Bower Error / Bower could not determine which components are installed in this project. Make sure you're connected to the Internet and try again." Repeated attempts (either clicking "Retry" or clicking "OK" and trying to download the component again) continue to fail.

The app completes the "Downloading Bower component list" without error. The error occurs when it is "Scanning For Installed Components..."

I'm connected to the Internet just fine.

When I try to install a Bower component, it fails with this message:

Why am I getting these errors and how can I fix CodeKit?

Thank you!

Answer 1

Turns out that Bower continued to fail, which prevented CodeKit from working.

Tolga Akyuz's answer to Siddharth's problem was the fix - I had a ~/.cache file which was preventing Bower from adding files to ~/.cache/

When I renamed the ~/.cache file (e.g. to ~/.cache-orig) and created a ~/.cache/ directory, Bower began working properly - and so did CodeKit.

Answer 2

It turns out that this behavior can be caused by several things. Another user fixed it and shared this with me:

I installed xcode and still had issues. After a bit of research, I found a post that said installing the command line tools in Xcode might solve the problem. I did that and the problem is now solved.

From what I can see, there is a appears to be an issue with the $PATH getting messed up with systems that have been upgraded from Lion (and Snow Leopard) that did not ship with git. In the questions and answers listed on the page linked below, there were several terminal command options given, but I was unsure of which to choose so I went with the Xcode route. https://apple.stackexchange.com/questions/18470/why-is-git-not-found-after-installing-os-x-lion

Answer 3

I had the same issue.

1. Check console messages (mac)
2. Delete faulty library. I had one.
3. Should be all good now.

good luck

Answer 4

If it's still relevant. In my case it was Google Maps AMD Loader Plugin. All fixed after removing it.

Answer 5

In my case the problem was with path to the project folder – it contains "!" symbol that makes bower crazy. To check is it Bower or CodeKit problem try to cd in terminal to your project folder and run "bower list".

zhaba$ bower list bower EINVALID Name must be lowercase, can contain digits, dots, dashes, "@" or spaces

With corrected project folder path CodeKit works.

Answer 6

I had the same problem running CodeKit2 with El Capitan, and an old version of Xcode. Updating Xcode fixed the problem.