On Sep 6, 2009, at 2:04 PM, Iceberg-Dev wrote:
On Sep 5, 2009, at 1:54 AM, Kevin Brock wrote: Kevin Brock wrote:
I managed to reproduce this with a really simple app. Xcode--> new Cocoa app, then build. Make three versions of it. 1.0, 1.1, 1.2.
Make a simple PackageMaker project by dropping in the app, and build it for each of the versions of the app.
Install 1.0 --> works
Install 1.1 version over 1.0 --> works
Install 1.2 version over 1.1, --> skipping component "com.mycompany.theapp" (*-1.0.0-*-*) because the version *-1.1.0-*-* is already installed.'
So it looks like it's not me. It's SnowLeopard...
Except that I can see the same behavior on Leopard. This is about as minimal an app as it's possible to build the only thing I customized was the name and the version. First upgrade is OK, second fails.
On Leopard it looks like sometimes it might be *saying* that it won't copy the app, but it does copy it anyway. On Snow Leopard it's doing what it says it's going to do. Which would be fine if it was getting the right version for the package...
If I remove the test app from the system and do an install with this package, it works, and the version definitely is 1.2, not 1.0.
There are no scripts involved, no strange bundle types, no customization...
Could it be that the application bundle is set so that Installer.app will look for an already installed version and it's finding one in a location that is not /Applications?
No... We've run into that as well, especially on development & test systems. We know that Installer will always try put the app wherever it was last registered, regardless of instructions. That's a whole 'nother pain in the a**. On this system there is no other possible location. The app wasn't built there, and it's only ever been in /Applications.
The really odd thing (among several) is that the *second* time it's failing. If they were simply not parsing the version string correctly that would be one thing, but the first upgrade works, and they show the correct versions. It's the second one that's failing, and showing a bogus version.
I really wish the PackageMaker & Installer docs were up to Apple's normal standards, but they've never, ever been close...
Kevin
|