Appcenter iOS install error "this app cannot be installed because its integrity could not be verified"

user_462440 0
Viewed 92555

I see that this question has been asked many times but I see no solution that works for me so I'm hoping that providing more info might shed some light.

We use appcenter.ms to test iOS apps. Until our iOS certificate expired this method worked fine. We generated a new enterprise certificate and ad hoc provisioning profile for new releases of the iOS app. Which led to the first curiosity.

I see how to upload a certificate on appcenter.ms but not a provisioning profile. I thought there was an option to do this in the past but perhaps I am mistaken. However, the app is signed with a provisioning profile before upload, so perhaps this is not needed now.

Once the app is uploaded, it can't be installed. It remains grey and when you tap it, you get the "this app cannot be installed because its integrity could not be verified" error. Again, that the .ipa is created with an ad hoc certificate and profile in Xamarin (VS for Mac).

Also, I can't install the provisioning profile on a device from appcenter.ms. You basically get stuck in a loop where you seem to successfully install the profile but have to keep doing it because it never actually installs.

I hope this is enough info for some insight and thanks in advance for any feedback.

xamarin certificate ios
6 Answers

We were able to solve this by redoing and downloading development certs and via

And also downloading and double clicking the apple development certificate here

After that our keychain showed both as trusted and we could build to the iPhone again.

user_48526590

The issue can be the your device is simply not registered on the developer portal and/or that ad-hoc provisioning profiles have not been regenerated.

You need to register your device, regenerate a provisioning profile with this device in it and rebuild your app using this profile.

user_9889410

I had this issue because when building the app on xCode for distribution (Product->Archive then Distribute App), I chose automatic signing. After manually signing the app and choosing my own generated certificate and profile, everything worked again fine.

enter image description here

user_23343520

I removed the Entitlements file from the Addition Resources in iOS Bundle Signing and it worked. I think the MSAL configuration was set to debug in entitlements.plist

user_45033730

In my case this was caused by trying to include an entitlement for aps-environment "development" when using an Ad-Hoc provisioning profile. The value for this environment in Entitlements.plist must match what is hard coded into the provisioning profile file - if you open an Ad-Hoc profile in a text editor you will see it expects the "production" environment.

The possible solutions depending on your requirements are to either use the Development profile/certificate, or change the aps-environment to "production" to continue using an Ad-Hoc provisioning profile.

It can also happen if you have other incorrect entitlements - worth checking what entitlements are enabled under the Identifier in Apple Developer portal and removing unnecessary ones.

user_20019340

I have also face this issue before but for me the reason was little different First the build was enterprise one and the build was made on the earlier Xcode version on which the iOS version you are using on the device was not supported by the Xcode. All I did was to update my Xcode and make a new build and shared the build. After that we were able to install that build over device Hope it works for you as well

user_90846410
Related