Sunday, 15 May 2011

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


I have a few questions about the "potential loss of key mill access".

I used an app for the old account, but now I want to update that app and when I try to submit the update build, shows me the key mill Has to suffer potential losses, but there is no error (using new provisions profile by encode). So I search on Google about it and I think that the reason is that old team id and new team id, its variation and because of this you can not create a provisioning profile with the old team id, so I "XC: com. Using a new XCode such as "TESTING.Test", I am creating a new profile and submitted the application using it with war.

But after submitting the app, I received an email from Apple "In the previous version software [XYZXYZ.com.TESTING.Test '] is an application-identifier value and the software is being presented In the new version ['ABCACC.com.Testing Test'] is an application-identifier. As a result,

1) If I ignore the "Provisional Warship" key, the new provision profile I am using Will the app not be able to use NSUSerDefaults? Or any other important information? (And does this problem not only reach old bunch of old installs or new installs?)

2 ) How to solve this problem?

Any help is epiiced

According to the docs, it will be anyway

.

NSUserDefaults There is nothing to do with this if you have a keychain From Classes are not used - - so they can leave safely this warning.


No comments:

Post a Comment