Re: App ID issue
Re: App ID issue
- Subject: Re: App ID issue
- From: Martin Umgeher <email@hidden>
- Date: Wed, 11 Jun 2014 14:41:07 +0200
On 11 Jun 2014, at 10:22 , Quincey Morris <email@hidden> wrote:
> — In particular, you must use XYZ for MAS-unique entitlements such as iCloud access and (I presume) push notifications. Forget about trying to use ABC.something in an app with such entitlements. It simply won’t work.
So you say that iCloud and Push _only_ work with a non-wildcard, Team ID-prefixed App ID?
> It’s not entirely clear what you mean by “preserve keychain access”. If you mean there’s app/user-specific data stored in the keychain under ABC.*, then I don’t know how you’re going to get to it from an XYZ.foo app. In the worst case, perhaps you can put out a utility under ABC.* that extracts the data for migration to the new app. If no one jumps in with a better answer, it may be worth using a TSI to get a definitive answer on this.
Yes, that’s what I mean. I have some data in the keychain that cannot be regenerated or entered by the user. And if I change the App ID prefix, I can no longer access this data.
Changing the keychain access group is the last resort here. Your idea of using a utility app for getting the data is interesting indeed. My approach would have been to create an app version which stores the data from the ABC keychain in some other place (either on the device or on a server), and then (a few weeks later) create yet another app version which uses the XYZ prefix (also for the keychain) and imports the old keychain data. Of course, that’s a very clumsy and error-prone solution.
Thanks for your reply!
Martin
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden