Logo Questions Linux Laravel Mysql Ubuntu Git Menu
 

How to solve keychain access warning after app transfer to new account

I have few question about "Potential Loss of Keychain Access ".

I transfer one app from old account to new account but now i want to update that application and when i try submit update build xcode show me warrning Potential Loss of Keychain Access but no error (using new provisioning profile by xcode). So i search on google about it and i found that its because old Team id and new Team id , its differnt and because of that you can not have provisioning profile containing old team id. So i create new provisioning profile using XCode something like "xc:com.TESTING.Test" and submitted app by using that with warrining.

but after submitting app i receive an email from apple saying "The previous version of software has an application-identifier value of ['XYZXYZ.com.TESTING.Test'] and the new version of software being submitted has an application-identifier of ['ABCABC.com.TESTING.Test']. This will result in a loss of keychain access."

So my questions are as follows :-

1) If i use new provisioning profile ignoring "keychain access warrning" then my app will not able to access NSUSerDefaults? or any other important information? (and this problem occures with only old install or new install also dont have access to keychain?)

2) How to solve this problem?

Any help is appriciated

Thank you

like image 435
Swap-IOS-Android Avatar asked Mar 16 '15 16:03

Swap-IOS-Android


2 Answers

According to the docs - Resolving the Potential Loss of Keychain Access warning, A one-time loss in keychain data will occur if you switch your App ID prefix -, this will happen anyway.

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

like image 166
Geri Borbás Avatar answered Oct 18 '22 08:10

Geri Borbás


You should contact with Apple customer service, they will change your TeamID to new account instead of keeping using old TeamID. Then creating new provisioning profile and connect to your app which has just been transfered.

like image 1
Binh Le Avatar answered Oct 18 '22 07:10

Binh Le