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.
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.
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.
This can also happen because of
Developer ID Notary Service - Outage
which can be checked on https://developer.apple.com/system-status/
Notarization is well explained here:
Notarization gives users more confidence that the Developer ID-signed
software you distribute has been checked by Apple for malicious
components. Notarization is not App Review. The Apple notary service
is an automated system that scans your software for malicious content,
checks for code-signing issues, and returns the results to you
quickly. If there are no issues, the notary service generates a ticket
for you to staple to your software.
Work around fix:
Select your app.
Navigate to TextFlight tab
Create External Testing group
Add one tester
Add build which you want to download using TestFlight
Open TestFlight and download an app.
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.
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.
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
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
This is how I solved for myself.
In you iPhone Settings > General > VPN & Device Management you should see your company name (if an app from it is installed), and if you click on it, you will see a button like "Verify" above the list of apps installed provided by the company. Just click on "Verify".
There is issue in my any swift application(Even there is nothing done in application) as I tried to install the application using distribution certificate and profile it is always crashing but if I am using development certificate and profile then it is working fine.
Also if I am using some other Mac system and use same certificates of distribution then it works well. Moreover Build size from my system is lesser than the build size than any other system build size.
I had tried all the suggestions related to this issues and changing settings or certificates but nothing helped me in this case.
Please suggest if you had faced similar issue or anyone you know.
Thanks In Advance
With Distribution certificate and profile app will not install from Xcode. You need to use only development certificates and profile for install app from Xcode to device. If you want to test with distribution certificate your app you can use test flight or iTune. Check below link for understanding -
check this answer
apple developer
apple.com
Tutorial
Afternoon all,
We have a client who recently came via our offices and installed a development version of an app we have been working on for a trip to the States to show his colleagues.
He has just gone to test it and is getting the message that '"App Name" is no longer available"' when he tries to open it. We have tested our development devices and the same build of the app here and everything is working fine.
Is there anything we can try as he does not have access to Xcode for a fresh install of the app?
We have checked the developer certs and provisioning profiles and all seem ok and in date.
Thanks a lot.
If you gave it to them via ad hoc or something, the provisioning profile has probably expired so you would need to renew that. This is a similar problem I've met before. For the IPA file providing, you could try to upload your apps to Pgyer or TestFlight and provide the installation link to customer.
We're working on the same project 2 persons. I don't understand why Apple forces the use of a "Development" profile, since develop isn't really supposed to be signed but whatevs. My issue is each time we compile on our machines, XCode invalidate existing provisioning profiles and create a "Managed" one.
Obviously this isn't XCode fault, but we failed to understand how it is supposed to work. Can we get an step by step on how to set up both development and production on more than 1 machine, using the "Managed by XCode" option, so we don't have to create a CSR each time? Thanks in advance
The short answer? Don't manage your provisioning profiles with XCode, I myself and countless others have the same issue and the only way I found around it was to manage them myself or using something like Sigh
I get this error when I want to export my project for Enterprise Distribution. But the funny thing is that I have all my certificates installed on the machine, so nothing should be wrong. Why can't Xcode import them if it knows I have a valid one? This is just stupid! Always these kinds of problems when distributing iOS apps, and always a different problem every time, with the certificates.
Here is the some reason for this error.
Your app is already live or review in appstore at that time this error is occured
Solution
you can clear DrivedData and make a new build file
Create a new AdHoc Provisioning And Download and after select that
certificates and make new build file
I hope this help you.