ITMS-90076: Potential Loss of Keychain Access

I have App Store Connect issues, after when I transferred application another account.

ITMS-90076: Potential Loss of Keychain Access - The previous version of software has an application-identifier value of ['oldID.iosapp'] and the new version of software being submitted has an application-identifier of ['newID.iosapp']. This will result in a loss of keychain access.

development team changed and what can I do ?

I have App Store Connect issues, after when I transferred application another account.

Right. This is expected. iOS keychain access groups are prefixed by your App ID prefix, which is usually your Team ID. When you transfer the app, its App ID prefix changes to the Team ID of your new team and thus you lose access to your existing keychain access groups.

what can I do ?

That depends on your specific circumstances:

  • In many cases this loss of keychain access isn’t a problem — it results in a minor irritation, like the user having to log in again — and so you can ignore this warning.

  • In other cases this is a big deal. For example, I’ve worked with developers who store all the user’s data in an encrypted database with the encryption key held in the keychain. If they lose access to this keychain item, all the user’s data is gone!

If you’re in the second group then my advice is that you transfer the app back to the original team, which effectively undoes the change. You can then create a more considered plan for the transfer.

There are two standard ways to plan for this transfer:

  • Provide the user with an export/import process (option A). The user must then:

    1. Manually export their data before the upgrade

    2. Upgrade the app

    3. Manually re-import their data after the upgrade

  • Create a second copy of the app and provide an easy way for the user to migrate their data (option B).

Personally I’m not a fan of option A. The issue here is that it’s very error prone: If things go wrong, there’s no way for the user to recover.

In contrast, option B is much safer: If something goes wrong the user can continue using the old app. The main drawback, however, is that you have to convince your users to actually make the leap to the new app.

Share and Enjoy

Quinn “The Eskimo!” @ Developer Technical Support @ Apple
let myEmail = "eskimo" + "1" + "@" + "apple.com"

Hi, If lost access of Keychain was minor to our customers, how can I eliminate the warning and public new builds?

  1. So basically you can't transfer apps with keychain access, a warning would be in place..
  2. how do you eliminate the warning

The lack of documentation and support is nuts.

ITMS-90076: Potential Loss of Keychain Access
 
 
Q