[Update] Additional issues with r13 have been fixed, the latest version is r14. See below.

I've just released an update (v1.8r13) that fixes the Can't get item 1 of "" bug on Mac OS X 10.5 Leopard which was launched yesterday. All plug-ins have also been updated, with the exception of SmugMug. To update, if you're still on 10.4, choose 'Check for Updates' from the Help menu in PictureSync; otherwise download the new version and then choose Check for Updates to get the latest plug-ins.

For the techies; the only compatibility issue (unearthed thus far) was that 10.5 changes the location of temporary files (yet again). In fact this change is for the better as the path is now apparently randomised which increases security. The SmugMug plug-in didn't require an update as we're using AppleScript's XML-RPC client (ironically SmugMug were considering dropping support for XML-RPC, but it does have the advantage of portable and reliable client support, if not a flexible lexicon). For all the other plug-ins we use our own HTTP and parsing methods to support the various services REST, SOAP and variant web service APIs.

If you're wondering what I think of Leopard, well I'm rather blasé:

• 10.5 Leopard is not such a notable upgrade as 10.4 Tiger unless you're a developer, the knock-on of this to you as a user is that you're like to see more applications with 10.5 specific functionality. It will herald a whole new era of enriched user-interfaces, but these apps may still be a little while coming. If you're on 10.3 Panther, go buy yourself a copy. If you're on 10.4, you'll have to weigh up the pros and cons.
• The UI tweaks really aren't too bad, I'll live with the new folder icons—they do go with the increased use of the powder-dusted aluminium look. Some are welcome, such as white menus (albeit semi-opaque), and glossy icon previews for videos.
• I'm not noticing too much performance improvement (and I installed extra RAM), but the new Finder is a welcome relief, although it's crashed twice…hopefully it'll become more stable with future updates.
• There are some nice little functionality tweaks, such as shared computers automatically appearing the sidebar, and secured network icons in the Airport menu (hold down alt for signal details). Hardly life changing though.
• An Archive & Install took about 1h30 (I skipped the disc check), took ages to calculate the time remaining which started at 8h and then remained at 1 minute for ages. My recommendation; if you currently have 10.4 or 10.3 and no prior version, and have experienced no issues, use the regular upgrade. If you've already upgraded your system e.g. from 10.3 to 10.4 and now 10.5 I'd recommend an Archive & Install.
• I was unable to delete and recreate some secondary partitions on my drive from the installer disc, but once booted I did without problem (a very welcome feature).
• I'm not likely to use TimeMachine myself, at least until I have more storage. I use SuperDuper because my backups are then bootable. (Tip: SuperDuper also preserves the upload state for items uploaded with PictureSync, which few other programs do. I'm sure, but have not tested, that TimeMachine will too.)
• Warning from Apple: do not use TimeMachine whilst running Aperture.

[Update 28th Oct. 2pm EST] Apparently this update is broken because it asks for Expression Media/Aperture, which is a terrible failure either of Xcode 3 or OS X 10.5. I'll get an update out in an hour or so if a rebuild on 10.4 goes as planned. You can still grab the prior version and prior plug-ins (unzip and drop into Home/Application Support/PictureSync/Services/).

[Update 28th Oct. 4pm EST] I've now rebuilt PictureSync using xcode 2.2 on 10.4 and released it as v1.8r14 to address the issues reported in the comments. It appears Xcode 3.0 on 10.5 is ignoring AppleScript "using terms from" commands that allow referencing applications that might not be installed—without prompting the user to locate a missing/unknown application. I'll have to investigate further but for now it certainly looks like I won't be using 10.5 to do further compiling.

As to why this slipped passed testing, in order to have caught it I would have needed to uninstall one of the supported applications, which is not something I test with minor updates as this was/should have been. As a small company (PictureSync for Mac is essentially maintained by myself only, at present) we're agile and rely mainly on your feedback to help isolate issues amongst the multitude of various combinations that PictureSync supports. As such we then aim to fix problems ASAP, as in this case. Arguably we wouldn't have to fix such issues if we had longer more thorough testing phases but in that scenario it would be impossible for us to offer PictureSync at it's current cost, indeed no charge has been made for upgrades since licences were originally introduced. Updates such as this are pushed out to only a small number of users so that issues are resolved by the time the majority download.

As ever thanks for reporting your issues, and I hope I've been able to address them suitably speedily.