Re: Question about Info.plist's

> On Aug 19, 2020, at 10:04 PM, Ben Kennedy wrote: > > >> On 19 Aug 2020, at 7:45 pm, Michael Hall via Cocoa-dev >> wrote: >> >> Something else I’m curious about is doesn’t this somehow invalidate any >> application signing that’s been done? > > Code signing happens last, even if you put

Re: Question about Info.plist's

> On 19 Aug 2020, at 7:45 pm, Michael Hall via Cocoa-dev > wrote: > > Something else I’m curious about is doesn’t this somehow invalidate any > application signing that’s been done? Code signing happens last, even if you put your shell script phase at the very bottom. (Observe the build outp

Re: Question about Info.plist's

> On Aug 19, 2020, at 9:04 PM, Michael Hall wrote: > > > I’m not familiar with the Plistbuddy that’s been mentioned. I see that is in fact builtin. Wasn’t aware. Something else I’m curious about is doesn’t this somehow invalidate any application signing that’s been done? ___

Re: Question about Info.plist's

> On Aug 19, 2020, at 11:07 AM, Gabriel Zachmann via Cocoa-dev > wrote: > > Question: > > Is there a way to use a key/value that was defined earlier in the plist file > to define a value for a later key? > Maybe off-topic but this used to be supported for Java applications for pre-set vari

Re: Question about Info.plists

Here’s the info from my StackOverflow answer. https://stackoverflow.com/a/55525399/1058199 Over the years, Apple has come up with several manners of changing version and build numbers. Many of them are now outdated and poor practice. Changing CURRENT_PROJECT_VERSION modifies values within your

Re: Question about Info.plists

I have build scripts that do that based on the # of the git checkins. I’ll send you the projects. > On Aug 19, 2020, at 11:07 AM, Gabriel Zachmann via Cocoa-dev > wrote: > > Question: > > Is there a way to use a key/value that was defined earlier in the plist file > to define a value for a l

Re: Question about Info.plist's

> On 19 Aug 2020, at 11:47 am, Gabriel Zachmann via Cocoa-dev > wrote: > > I tried this: > > plutil -replace CFBundleVersion -string '$(CURRENT_PROJECT_VERSION) 111' > qq.plist > > which works -- but what I need to do is something like this: > > plutil -replace CFBundleVersion -string "\$

Re: Question about Info.plist's

Thanks a lot for the insights. > On 19. Aug 2020, at 18:44, Glenn L. Austin wrote: > > No, you can't use an "earlier" key to create a "later" value - but you can > use code to do basically the same thing. > > Or, you can use the same variable that sets your CFBuildNumber to set your > CFBundl

Re: Question about Info.plist's

> On 19 Aug 2020, at 9:07 am, Gabriel Zachmann via Cocoa-dev > wrote: > > The plist file has, additionally to all the default stuff, the key > CFBuildNumber (with a value that I increment automatically). > > In Xcode, I tried to change "Bundle version" to a value like > > $(CURRENT_PROJEC

Re: Question about Info.plist's

On Aug 19, 2020, at 11:11 AM, Saagar Jha via Cocoa-dev wrote: > > Which file are you modifying? The one in your source directory? Because the > one that goes in the final product doesn’t get copied over until after you’ve > lost most control over the build process (it’s done by Xcode after the

Re: Question about Info.plist's

Which file are you modifying? The one in your source directory? Because the one that goes in the final product doesn’t get copied over until after you’ve lost most control over the build process (it’s done by Xcode after the normal build stages). > On Aug 19, 2020, at 09:58, Owen Hartnett via C

Re: Question about Info.plist's

You can also use a build script that calls PlistBuddy to alter the contents of a plist called using a Run Script in Build Phases just before Compile Sources. I used to use one to apply the subversion revision number to the build version, but then I switched to git. -Owen > On Aug 19, 2020, a

Re: AddInstanceForFactory: No factory registered for id

> On Aug 19, 2020, at 8:27 AM, Gabriel Zachmann via Cocoa-dev > wrote: > > I would just like for the (error?) message in the log file to go away. Don't worry about it. There are plenty of Apple subsystems that log warnings in normal operation. It would be nice if it didn't happen, but it's n

Re: Question about Info.plist's

No, you can't use an "earlier" key to create a "later" value - but you can use code to do basically the same thing. Or, you can use the same variable that sets your CFBuildNumber to set your CFBundleVersion. -- Glenn L. Austin, Computer Wizard and Race Car Driver <><

Question about Info.plist's

Question: Is there a way to use a key/value that was defined earlier in the plist file to define a value for a later key? Explanation: I have a macOS project with an automatically created "About" window. The plist file has, additionally to all the default stuff, the key CFBuildNumber (with a val

Re: AddInstanceForFactory: No factory registered for id

>> On Aug 18, 2020, at 10:33 AM, Gabriel Zachmann via Cocoa-dev >> mailto:cocoa-dev@lists.apple.com>> wrote: >> >> (I have already experimented with AudioServicesCreateSystemSoundID(), but >> failed.) > > In my experience, playing sounds (in macOS apps) only works when using mp3 > files. I am