Upgrade testing for iOS - application-identifier e

Question

Previously with Xcode 7.3.1 I was able to build directly over my app store app on my iPad and test the upgrade scenario, which worked perfectly fine. This week I upgraded to Xcode 8 and when I try the exact same approach, I keep getting this upgrade error

"This application's application-identifier entitlement does not match that of the installed application. These values must match for an upgrade to be allowed."

I tried multiple solutions posted on this thread and none of them worked. I also don't have a watch app. Just a simple iOS app target.

App installation failed due to application-identifier entitlement

I deleted my certs and provisioning profiles and recreated them and still the same problem. I then went and downloaded Xcode 7.3.1 and tried it again with the exact same problem.

Now I am stuck without being able to fully test my upgrade scenario.

PLEASE HELP !!

Answer 1

Here is one solution if you want to upgrade over your existing App Store app without deleting it but your application-identifier entitlement does not match. Upload an archive of your new build to the App Store and then use TestFlight to download it to your device. This is not as quick as building to the device, but it will overwrite your old app with your new build while keeping your old data in place. For (relatively) quicker turn-around testing of your upgrade process once you have a new build available on TestFlight:

1. Delete your app off of your device (assuming it was a recent build)
2. Download your app store build and generate some data
3. Download your TestFlight build, but don't run it
4. Build your newest build directly to the device

The TestFlight build overwrites the entitlement without deleting the old data, so Xcode happily will install your new build over the TestFlight build, but you are still testing your upgrade process as if you were building directly on top of the App Store version of your app.

Answer 2

Remove the existing application from the device and Run again.

Answer 3

Select the App Target and click on General, if you select or ticked checkbox automatically manage signing.

Untick this automatically manage signing and select appropriate signing provisioning profile and #Build and run again.

See the below photo.

Answer 4

I got this from an .ipa generated as a Jenkins artefact. The problem for me was that Jenkins was using a different provisioning profile.

I manually set Jenkins to use the same profile as the updated version that I was trying to install, and it started working.

Answer 5

To fix this just enable "Automatic manage signing" from general tab of project settings.

I had also problem for running app on my device directly from xcode 8. Deleting and generation profile and certificate did not worked for me. But enabling "Automatic manage signing" worked for me.

Hope this helps!

Check this question of mine: Xcode 8 shows error that provisioning profile doesn't include signing certificate

Answer 6

I had the same issue while trying to upgrade application. And here what I've found:

I checked application-identifier entitlements of old app and new app. You can do that by running codesign -d --entitlements :- path/to/AppName.app/AppName or open file "archived-expanded-entitlements.xcent" at path "AppName.app/AppName".

Application-identifier of old app was "1234XXX5X6.com.mycompany.myapp" but in new app it was "1234XXX5X6.com.mycompany.myapp.develop".

Usually I set "Bundle Identifier" directly in Info.plist.

But I didn't know that there is also a "Product Bundle Identifier" property in project Build Settings.

The previous version of app was built with Xcode 7.3.1 and it had following settings:

• Info.plist: com.mycompany.myapp
• Build Settings: com.mycompany.myapp.develop
• application-identifier: 1234XXX5X6.com.mycompany.myapp

The new version was built with Xcode 8.2.1 and it had following settings:

• Info.plist: com.mycompany.myapp
• Build Settings: com.mycompany.myapp.develop
• application-identifier: 1234XXX5X6.com.mycompany.myapp.develop

Seems like new Xcode have different source for application-identifier. So I just corrected "Product Bundle Identifier" and my problem was solved.