If we're changing it, it should be to im.adium.adium, not com.adium.adium,
definitely.
We'd need upgrade code for any NSUserDefaults preferences; pretty easily done
by something like this untested code snippet:
for (NSString *key in [(NSArray *)CFPreferencesCopyKeyList(oldAppID,
kCFPreferencesCurrentUser, kCFPreferencesCurrentHost) autorelease]) {
CFPropertyListRef value = CFPreferencesCopyAppValue((CFStringRef)key, oldAppID);
CFPreferencesSetAppValue((CFStringRef)key,
value,
newAppID);
}
We'll definitely end up re-prompting for keychain access, too, with a new
bundle ID, but I think we'll do that anyways because we're changing code
signing identities.
-Evan
On Tuesday, March 20, 2012 at 7:47 PM, Eric Richie wrote:
> Or even just kill the X's?
>
> -Eric
>
> On Mar 20, 2012, at 8:46 PM, Jordan wrote:
> > Could you change it to im.adium.adium without causing tons of problems?
> >
> > Jordan
> >
> > On Tuesday, 20 March, 2012 at 9:42 PM, Evan D. Schoenberg, M.D. wrote:
> >
> > > Folks,
> > >
> > > Just a status update.
> > >
> > > We now have an approved and identity-verified Apple Developer account,
> > > associated with Instant Messaging Freedom, Inc., so we will be able to
> > > sign Adium with an Apple-provided Mac Developer ID.
> > >
> > > However, the com.adiumX.adiumX bundle identifier is marked as "already
> > > registered" so we can't get the certificate yet. I believe I registered
> > > it into some other Apple registry a long time ago, but I'm not 100%
> > > certain of that… in any case, I can't figure out where, or how to free
> > > it. I've emailed Apple developer support for help.
> > >
> > > -Evan
> >
>
