0 Replies
      Latest reply on Dec 5, 2019 4:48 AM by a4o
      a4o Level 1 Level 1 (0 points)

        We are trying to create a new build of an app for iPad and iPhone which has just been transferred to a new account. The new build will not install over the version which is published on the AppStore.


        XCode says... Failure Reason: This application’s application-identifier entitlement does not match that of the installed application. These values must match for an upgrade to be allowed.


        The main error in the console is of the form... Upgrade's application-identifier entitlement string (NEWTEAMID.com.COMPANY.APP) does not match installed application's application-identifier string (OLDTEAMID.com.COMPANY.APP); rejecting upgrade. The only mismatch is in NEWTEAMID vs OLDTEAMID.


        The app contains file picker and provider extensions sharing an app group with the app. The IDs for these these were not moved to the new account by the transfer process. We have re-created them in the new account with Xcode,  which required that they were deleted from the old account. Data stored by the app includes files in the group folder and settings accessed via NSUserDefault, but nothing keychain related, I don't think.


        Apple Developer Support - Development and Technical referred me to the documentation, including https://developer.apple.com/library/archive/technotes/tn2319/_index.html#//apple_ref/doc/uid/DTS40013778-CH1-ERRORMESSAGES-UPGRADE_S_APPLICATION_IDENTIFIER_DOES_NOT_MATCH_THE_INSTALLED_APP, which suggests that if the app is to use the new team ID, we need to manually edit entitlements files and request a special provisioning profile from Apple. I don't see how we could sign the app with the old team ID.


        I have sent a request via the "Apple Developer Program Support" link in the tech note, using the heading "Certificates, Identifiers, Profiles". The new reply from Apple suggests I use a technical support incident via apple.developer.com/support/technical, but reading that page suggests to me it is for code level, API support.


        There are other threads in these forums about this problem but I can't see any solutions apart from deleting the old application or resetting your watch, and there are "me too, did you manage to fix this" responses.


        Does anyone know how can we proceed to update the existing app, so existing users will not lose data stored by the app?


        It could be helpful to many to record the current solution here.