Month: April 2011

Two years ago I posted some quick instructions on how I keep my Adium chat logs synced between Macs using Dropbox. I’ve tweaked my setup slightly since then. Here’s my new approach.

First, if you already have Adium on multiple machines, copy all your logs over to a single Mac. You can merge the folders easily with an app like Changes. Once you’ve got a canonical folder of all your combined chat logs, place it somewhere in your Dropbox. Then…

cd "~/Library/Application Support/Adium 2.0/Users/Default/"
mv Logs ~/Desktop/LogsBackup
ln -s ~/Dropbox/Path/To/Adium/Logs/ Logs

Repeat the symlink steps on each Mac you want to sync.

This new approach keeps your files physically in Dropbox and a symlink in your Adium support folder pointing to their real location.

And that’s it. Enjoy.

(Really though, this would be a lot easier if Adium had an option to choose where your chat logs are stored.)

For any Mac developers out there who are seeing the following rejection notice when submitting to the Mac App Store:

Unsupported Architecture – Application executables may support either or both of the Intel architectures

Make sure you verify that any included frameworks are Intel only. You can do this using the lipo command:

lipo -info /path/to/SomeFramework.framework/Versions/A/SomeFramework

If the output lists anything other than i386 or x86_64 you’ll get rejected.

This was particularly painful for me because it appears this check is only run when submitting a new version of your app — PPC framework binaries don’t cause a rejection during the original app submission process. I thought I was going crazy since I had made no project changes since the first submission and running lipo on the app binary didn’t return anything unusual. Hopefully this will save someone else the hour of head scratching I just went through.