EricHolsinger.com

Now that iTunes 10.5, iOS5 and the new Xcode have been released, it is worth mentioning that to uninstall any beta installation you had, you should use the uninstaller.


sudo <Xcode>/Library/uninstall-devtools --mode=all


Where <Xcode> is the directory where you installed the beta Xcode.

I usually install the different versions into different directories (/Developer, /Developer5b3 etc).

I’ve been getting a lot of comments about how to fix the Xcode codesign failed with exit code 1; expired certificates causing ambiguous matches. This problem is such a time sink that I suspect it really helps to have someone explain the simple solution for resolving it.

To make it easier for those who’d rather hear how to solve it, I made a short video explaining the solution.

I appreciate the feedback and I’m glad to help.

And thanks to everyone who’s helped me.

Sometimes, putting a website into a subdirectory just doesn’t cut it. You need to have the website act like it’s on it’s own first party domain. But how do you do this with XAMPP? XAMPP uses Apache web server and to do this with Apache, you would create virtual hosts.

To create some XAMPP virtual hosts on our Mac, we need to

* create a virtual hosts entry for each virtual host
* include the virtual hosts file in the httpd.conf
* add an entry in your hosts file for each virtual host
Read the rest of this entry »

If you work with Xcode code signing long enough you’ll run into an error like this:

/usr/bin/codesign failed with exit code 1

If you view the build results (Build->Build Results), and expand the error message (there is a little paragraph button on the right-hand side of the line) you may see something like this:

iPhone Developer: Firstname Lastname (hashcode): ambiguous (matches "iPhone Developer: Firstname Lastname (hashcode)" in /Library/Keychains/System.keychain and "iPhone Developer: Firstname Lastname (hashcode)" in /Users/username/Library/Keychains/login.keychain)
Command /usr/bin/codesign failed with exit code 1

You have two certificates, with the same unique identifiers. One is in your login keychain and the other is in your system keychain. The real problem is, you probably have an expired certificate conflicting with your active certificate.
Read the rest of this entry »

The web is abuzz with amazement and wonder over Microsoft’s new site http://ie6countdown.com/, with the tagline “Moving the world off Internet Explorer 6″. It shows US IE6 usage at an astounding low of 2%. If you’ve made a web page with CSS and JavaScript in the past 10 years, you’re probably saying (or thinking) “Yes! Die IE6! Die! Die! Die…”.

Wow! US IE6 usage is only 2%? It's almost gone, or is it?

But, there is something missing from this beautiful infographic.
Read the rest of this entry »