Glad it's working!
-damien
> On 27 Jan, 2017, at 15:14, James Foster
> wrote:
>
> Hi Damien,
>
> Thanks very much. That seems to have done it!
>
> Some time ago I copied one of the many scripts out there that provides for
> auto-incrementing the build, and it defaulted to hex. I’ve switched
Hi Damien,
Thanks very much. That seems to have done it!
Some time ago I copied one of the many scripts out there that provides for
auto-incrementing the build, and it defaulted to hex. I’ve switched to decimal
and that works.
James Foster
> On Jan 27, 2017, at 12:09 PM, Damien Sorresso wr
Hi James,
"E6" is not a valid CFBundleVersion. CFBundleVersions are very specifically
tuples consisting solely of three numeric elements as proscribed in
https://developer.apple.com/library/content/documentation/General/Reference/InfoPlistKeyReference/Articles/CoreFoundationKeys.html#//apple_ref
Hello James,
If I remember correctly, you need special keys in your tool and app info plist
files with codesigning designated requirements. Did you verify that these
designated requirements verify correctly against the actual tool and app you
are using while testing?
Regards,
Thomas
> On 27 J
According to Damien Sorresso, BSD Engineering, Apple Inc. (see
https://lists.macosforge.org/pipermail/launchd-dev/2010-October/000834.html),
"ServiceManagement will check the CFBundleVersion of the tool and, if it's the
same ..., will not overwrite it."
I've updated my code to show the CFBundle
I am attempting to replace a helper tool. Most of the time if I increment the
version (of my application and of the helper tool) then the new tool will be
installed. Sometimes it won't be installed and I have to delete the old one
manually. The problem seems to occur about every dozen versions o
