Cannot update to 3.5 on older MacPro and 3.5 not compatible with 3.4.5

The only thing you can do to maintain comparability is to restore Mountain Lion (or whatever OS was on the MBP) and continue to run 3.4.5 on all systems.

Note Aperture libraries cannot be rolled back Once the library is updated that's it. The only recourse is to restore it from a backup.

I agree. Mentioning that and also the fact the users who bought Aperture prior to the App Store were going to be switch over to the App Store.

It's a good thing but would have been nice to know about in advance.

regards

have the same issue, work on two Macs, updated one to 10.9 and updated to 3.5

i tend to move projects around and now i can not move them they dont open.

i tought now you can tell the app store to install an older versions?

I believe the "install older versions" is for the iTunes App Store. That is to say, for iOS.

So glad I thought to check before accessing my Aperture library. My main computer isn't 10.9 compatible either. Guess Aperture is just for final storage now and will have to consider starting using a 3rd party app that works through at least back to Lion.

A reason all these recent updates were free I guess.

Just double checking here as I'm in a similar situation. I haven't updated the libraries yet.

But you're saying I need to roll my Mavericks machine back to Mountain Lion? And if so what's the best way to do that?

Thanks.

PS: Note to Apple this really ***** and now warning given.

Replying to self. I'm going to try using TimeMachine to roll back to Mountain Lion. The directions seem simple enough. http://support.apple.com/kb/PH11181?viewlocale=en_US&locale=en_US.

PS Apple seems very sensitive about certain words. The word I used isn't one of the seven dirty words and in fact maybe not even 100 words.

I meant to say (using a more polite wording): Note to Apple this is really a poor way to treat your customers and NO warning given.

TimeMachine worked with a few minor resettings so far.

When I feel like going throught the hoops again, I'll upgrade to Mavericks again, but not update Aperture; although the risk of accidentally upgrading is there. If that happens I'll try copying over Aperture 3.4.5 and seing if it works.

Problem will go away in a couple of months when I upgrade (replace) my laptop. Waiting for refurbs of the newest ones.

Mavericks was free too as well as the iWorks apps. Maybe Apple is going to give away more apps to keep us buying Apple devices.

Actually, I had this same problem - accidentally upgraded my library on my Mac Air to 3.5, but am not running Aperture 3.5 on any of my other, older Macs. I *was* able to downgrade the library back to 3.4.5. BAsically, I had to open the library on a computer running Aperture 3.4.5 in library repair mode (holding down command and option when opening). In the ensuing dialog I had to choose to rebuild the library. I first tried just repairing, and it seemed to work, but next time I opened Aperture I got the "library can't be opened iwth an older version of Aperture" message. Rebuilding it seems to have done the trick.

A more detailed explanation (though not written for this particular scenario) is here:

http://www.apertureexpert.com/faq/common-aperture-questions-issues-and-rep/how-d o-i-repair-or-rebuild-my-aperture-library-or-permission.html

Having restored the library to 3.4.5 format, I downgraded Aperture on my Air to 3.4.5 as well and it's been smooth sailing. Just make sure you have Mavericks set up to *NOT* automatically update your apps, or you'll end up in the same situtation all over again when it silently upgrades Aperture to 3.5 again.

Good luck!

I was encouraged to read this report, but there seems to be a needed caveat. I copied an Aperture 3.5 library to my Mac Pro from my MBP, and then tried to open it with A3.4.5, with the expected failure. Then I did a rebuild, which seemed to go quickly, and the library then opened.

However, I had imported some new photos into this test library while in 3.5, and for those images, clicking to view any individual photo resulted in an Unsupported image message. Those images that had already been in the library when it was first upgraded to 3.5 did not present this issue.

Ernie

Amended result: Reprocessing the Original corrected the unsupported, but assume any adjustments were then lost, but need to confirm later.

Good point. I had not modified the library (added, deleted or modified any photos) before trying to recover it. I think what you're describing would be expected results.

If you had done a large amount of additional work in the converted library, you could try the "import into a new library" trick, but I have not tried that, so I can't say whether it would work.

I'm pretty much seeing this as a recovery solution for those who inadvertantly upgraded and are trying to recover their library, rather than a generalized solution to moving back and forth between library version.

Glad it seems to have helped!

Well, I was only testing. Thus far I have done nothing to imperial my alpha library, which remains under 3.4.5, and for which I am running pre-10.9 OSX -- ML on my rMBP and Lion on the old MP.

But 3.5 and 10.9 are tantalizing fast in response on my rMBP. Sadly that same rMBP booted into Mt. Lion from an external USB3 drive out performs 3.4.5 operating on my Mac Pro which can only run Lion. So I await the new MP and its improved interfaces for synergy with my rMBP and its Thunderbolt library drives.

Ernie