Weird. I tried that. Still no go. I ended up having to delete that archive (I 
didn’t need it anyway) and now it’s correctly firing up my current development 
copy. 

> On Aug 1, 2014, at 11:21 AM, SevenBits <[email protected]> wrote:
> 
> On Aug 1, 2014, at 11:18 AM, Jon Baumgartner <[email protected]> 
> wrote:
> 
>> 
>>> On Aug 1, 2014, at 3:01 AM, Kyle Sluder <[email protected]> wrote:
>>> 
>>> On Jul 31, 2014, at 9:11 PM, Ken Thomases <[email protected]> wrote:
>>>> 
>>>> You probably want lsregister.
>>>> /System/Library/Frameworks/CoreServices.framework/Frameworks/LaunchServices.framework/Support/lsregister
>>>> 
>>>> First, I'd try "lsregister -f /path/to/NewVersion.app".  If that doesn't 
>>>> change the behavior, you can do "lsregister -u /path/to/OldVersion.app".
>>> 
>>> Also, Launch Services supposedly picks the bundle with the highest 
>>> CFBundleVersion. So make sure that differs between all the versions you 
>>> have installed.
>> 
>> Thanks, guys. Unfortunately, neither of the lsregister commands worked. I 
>> even rebooted in between. 
>> 
>> My CFBundleVersion was unchanged (oops!), so I updated that, but it’s still 
>> insisting on opening the old one!
> 
> Is it possible to maybe clear the derived data and rebuild your app with the 
> updated CFBundleVersion? 
> 
>> _______________________________________________
>> 
>> Cocoa-dev mailing list ([email protected])
>> 
>> Please do not post admin requests or moderator comments to the list.
>> Contact the moderators at cocoa-dev-admins(at)lists.apple.com
>> 
>> Help/Unsubscribe/Update your Subscription:
>> https://lists.apple.com/mailman/options/cocoa-dev/sevenbitstech%40gmail.com
>> 
>> This email sent to [email protected]
> 


_______________________________________________

Cocoa-dev mailing list ([email protected])

Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com

Help/Unsubscribe/Update your Subscription:
https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com

This email sent to [email protected]

Reply via email to