How to enable a warning about access to the keychain after the application switches to a new account

Question

I have few questions about the "Potential loss of access to the keychain."

I am transferring one application from the old account to the new account, but now I want to update this application, and when I try to send the update. build xcode show me warrning. Potential loss of access to the keychain, but without errors (using the new xcode initialization profile). Therefore, I searched on google about this, and I found that this is due to the fact that the old Team identifier and the new Team identifier are different from it, and because of this, you cannot have a profile profile containing the old team identifier. So I create a new preparation profile using Xcode, something like "xc: com.TESTING.Test" and a submitted application using this with warrining.

but after sending the application I get an email from Apple saying: "In the previous version of the software, there is the value of the application identifier ['XYZXYZ.com.TESTING.Test'], and the new version of the software, the identifier ['ABCABC.com.TESTING.Test ']. This will result in loss of access to the keychain.

So my questions are: -

1) If I use the new provisioning profile, ignoring "warchain access warrning", then my application will not be able to access NSUSerDefaults? or any other important information? (and this problem only occurs with the old installation or the new installation also does not have access to keychain?)

2) How to solve this problem?

Any help is determined

thanks

Answer 1

According to the docs Allowing a warning about a potential loss of access to the key chain . If you switch the identifier prefix of your application , data will be lost once in the key chain.

NSUserDefaults has nothing to do with this. If you have not used the Keychain services - Keyword Relationship Reference - you can safely omit this warning, as they say.

Answer 2

You should contact Apple Support, they will change your TeamID to a new account, instead of using the old TeamID. Then create a new provisioning profile and connect to the application just migrated.