We have an app that was distributed using Enterprise Distribution Profile. Now, the same app is working for some but others are reporting the following issues.
Existing/Installed app throws this error, and doesn't open:
{App Name} Is No Longer Available
Users who try to download the app from the Enterprise link are reporting this error:
Unable to Download App - {App Name} could not be installed at this time.
Done Retry
Users running iOS 8.4.1 are specifically reporting these issues. I regenerated the profile and rebuild the app. This seems to have fixed the issue for some users, but not for all.
What's the real problem here? Thoughts?
Most common causes of this issue:
URL in the plist that references the ipa is invalid.
Device storage is full
The provisioning profile is a developer provisioning profile
The ad hoc distribution provisioning profile is corrupted and the device is having an issue with it.
The device was restored from a backup and is causing a conflict for over-the-air distribution
There was a network timeout
Architecture settings of the build and the device are incompatible (can sometimes happen when "Build Active Architecture Only" is on when
building).
Not Using Mobile Safari.
To find out the exact cause of this issue:
Connect the device to your Mac.
In Xcode, open the Devices window.
Choose your device from list on the left.
View the console for the device.
Now install the app it will show the exact cause of problem
My guess, since it is only happening on some device, is that you could be using a developer provisioning profile, or maybe you are building for only one architecture, so it will only work on some devices that match the built architecture.
Please look at the device console during an install attempt to get a detailed error that should point you down the correct path for a fix.
I have the same problem.
We have found a temporary solution.
To install beta builds we are installing our apps via itunes and an ipa file
Related
I am trying to deploy an iOS app Ad Hoc to an iPhone for beta testing. I've been developing the app on Windows VS, I have a Macbook air with all the necessary software (Xcode, VS, etc), and I have paired to it with VS on my Windows machine. I have also followed the following steps:
Created an Apple Developer account
Created an App ID with the bundle identifier as the same exact one as the one in info.plist
Created a signing certificate using my Macbook Air, downloaded it, and installed it into XCode
Created a provisioning profile with the App ID and the certificate, and made sure to include the device that I want to load the app onto.
Made sure everything above was set to "distribution" and "ad hoc" as needed.
Set Bundle Signing in my iOS project properties to Manual Provisioning, and selected the Signing Identity and Provisioning Profile to the ones that I created for this deployment.
Set the build to Release and the target to Remote Device
Ensured that the deployment target in info.plist was set to the highest available, which is 15.4, though my iPhone is at 15.6 (could this be the problem?)
Set the IPA Packaging Options to "Build iTunes Package Archive (IPA)"
Set "Include iTunesArtwork images and the iTunesMetadata.plist" to true in the same area
Successfully built the iOS project and produced a .ipa file
After all that, I've been trying to get the .ipa onto my phone, which is definitely the device I added to the provisioning profile.
I've tried two methods to do this, and both have failed:
Connecting my phone to my Windows machine and opening iTunes. Dragging the .ipa file onto the device. The app shows up on my phone, but when I try to open it, I get this error:
"This app could not be installed because its integrity could not be verified". Though it should have been.. The device is linked to the provisioning profile that was used to create the darn thing.
Connected my phone to my Macbook Air and accessed the device through XCode > Window > Devices and Simulators. I emailed myself the .ipa file and downloaded it onto the machine (the Microsoft docs explicitly state that emailing the .ipa should work just fine). In the "Intalled apps" section of the device, I clicked the little '+' and then pointed it to the downloaded .ipa. After a few seconds, it pops up an alert window that says "Unable to install *.iOS".
Other things I have tried since this has been a problem:
Recreating the above steps by re-registering my device, creating new certificates, downloading, installing, all that business.
Messing with the deployment target version.
Jumping out from behind the couch and startling it to make it do what it's supposed to.
I swear I'm done with Xamarin forever after this problem is solved, but all the headaches I've experienced have made me think twice about whether to even bother with .NET Maui haha thanks for any help you can provide
Firstly, the error This app could not be installed because its integrity could not be verified" may be caused by the proper certificate or the test devices are not visible in 'Devices' (UDIDs added) in developer.apple.com/account.I found two simialr issues, you can refer to them: link1, link2.
Secondly, have you follow this docs on how to generate the IPA file?
I am new in iOS development world. Currently, I'm trying to export my app for some users to test. I do not want to upload to the store first, so I'd export my app as Ad-Hoc Deployment. After that, I uploaded my myApp.ipa to Diawi to generate link for distribution. But two kind of results I got:
Note: Both devices are iPhone 6, both iOS v9.3.2.
Device 1: Successful
Device 2: Not Successful
They able to download but once the circle is completed. This message prompted. No matter how many times they tested, the result still the same.
Unsuccessfull Message Prompt
I do not understand what is happening. Tested in many devices, some successfully downloaded, but some not. Should I register each of them in the application under Provisioned Devices? If yes, is there any other way to distribute the app without needing to register them? If no, what actually I need to do to solve this issue? Thanks in advance.
Most common causes of this issue:
Device storage is full
The provisioning profile is a developer provisioning profile
The ad hoc distribution provisioning profile is corrupted and the
device is having an issue with it.
The device was restored from a backup and is causing a conflict for
over-the-air distribution
There was a network timeout
Architecture settings of the build and the device are incompatible (
can sometimes happen when "Build Active Architecture Only" is on when
building).
Not Using Mobile Safari.
Check also "iOS Deployment Target"
To find out the exact cause of this issue:
Connect the device with iMac.
Open Organizer then choose devices.
Choose your Connected device from sidebar.
Choose Console inside the chosen device.
Now install the app it will show the exact cause of problem
I think this is helpfull for you.
I'm sending my app to testers with Beta from Crashlytics which is an amazing tool to do app testing.
I had every new tester's device UDID registered in my developer account and then distribute a new build.
My testers got email invitation and accessed app's installation which could not be completed on their device.
They kept seeing an alert showing up with message:
Unable to download app - MyApp could not be installed at this time -
Done / Retry
Testers' testing status are "installed" in my Crashlytics dashboard but they're actually not able to finish installation.
Please help me find any possible factor causing this problem.
Perhaps the provisioning profile embedded in the build has been invalidated. Use Xcode to create a new archive, then use Fabric to upload a new build with that archive.
Discussion:
In my case, I had deleted the provisioning profile in the Apple Developer Member Center that had been embedded in each of my Fabric Beta builds. This caused the app testers had previously installed to immediately crash when they tried to launch it (embarrassing). It also caused the "Unable to download app - MyApp could not be installed at this time - Done / Retry" issue when testers tried to (re)install the app via Fabric Beta. Uploading a new build with my new provisioning profile embedded fixed the issue (each tester had to install the new build).
I've run into this problem back on iOS8 and just recently saw it again for iOS9, the only thing that solved the install issue was for my users to delete any previous version that they had downloaded, restart their phone, and try again.
You can also verify with them if Crashlytics properly installed on their iDevice, I've seen more than once where the configuration profile caused the issue, it's worth removing that (Settings -> General -> Configuration Profile (towards the bottom)) and retrying the install.
This is usually caused by one of two problems:
Incorrect provisioning profile/code signing settings. Double- and triple-check that the following settings are the same for the project and the provisioning profile: bundle identifier, development vs. distribution, adhoc.
Caching - sometimes, even when you've done everything correctly, things still just go awry. In such cases, you can try: deleting the previous version of the app from your phone, cleaning your project, deleting and re-downloading provisioning profiles, and building the app again.
RubyMotion Solution
For me, it was because I was using a development distribution profile, but with the wrong entitlements. Well, entitlement, singular.
I still had the 'beta-report-active' entitlement enabled, which was not included with the development distribution profile I am using. It is instead included with the production distribution profile (which is needed to distribute to TestFlight). However, I just wanted to deploy to my local phone, and not air my dirty app laundry to my entire internal test group, so this is where I found myself.
In any case, removing the 'beta-report-active' entitlement fixed my issue.
I tried the normal route of checking for proper certs and also deleting the app and provisioning profile along with rebooting device. In my case it was installing on device A and not device B. Device A was older iPhone 5c running iOS 9 and device B was newer iPhone 8 running iOS 11.x. When I archived the app for distribution I was selecting device A during the archive. Once I selected "Generic Device" it worked. But I'm sure I've built in the past selecting a specific device instead of generic and it worked. I was using Xcode 8.2, but I don't believe the Xcode version matters.
We submitted an app recently with Apple Watch support. It installed from the App store fine but when preparing an update, we can't get it to install on a real Apple Watch anymore (fine in simulator). We have tried installing using Apple Testflight Beta and Ad Hoc builds (we, the developers do not have an actual device ourselves, just a remote tester).
The only significant thing that has changed is that we have updated to XCode 6.3 since the first release.
I have tried:
Adding/removing beta-reports-active: Debug on real Apple Watch: Application Verification Failed
Verified that the deployment target is iOS 8.2.
UUID for watch and phone are in the provisioning profiles
Provisioning seems OK when examining IPA bundle and it can be uploaded to Apple Testflight
Rebooting XCode, machine, etc.
The one thing that is suspicious, is that when exporting the IPA from XCode, the entitlements summary for the watch app have a circle/cross for the icon (no error is reported though). Also, the keychain-access-groups value is by default set to the Watch app's bundle id (not the host app). I have tried creating my own entitlement file to match though, and this doesn't seem to do anything. I would attach a screenshot but I don't have a 10 reputation...
Any help with this would be great. It is very hard debugging when you don't have the actual device. I have to make builds and wait for the one remote tester to try. Then repeat...
Update:
Now that I have the rep, here is the screenshot:
I did get a watch. The first time I tried to install it, it gave the same error. I then tried debugging in Xcode. It would install through Xcode (Xcode created provisioning XC profiles). Subsequently, I could get it to install using Testflight Beta. However, it still would not install for our external tester!
Check your certificate entitlements. Go to apple developer center and accept the new entitlement if any. Make sure you are not using beta Xcode to publish the app.
Try validating the build before pushing to Test flight(validate in archive area) and also do check the certificate is a distribution certificate.
I am using In-House subscription of Apple. I built app and distributed it via web link. Everything was okay, so I could install this app by calling manifest from iPhone's safari browser. Then I revoked certificate and remove provision profile - that causes my app to fail to run (then I found that this happens all the time when you revoke certificate.)
To make my app working again I created new certificate and in-house provision profile - then I resigned my current .ipa file and replaced it on web server.
Then I tried to install app on different devices
I installed it on 1 iPad and it works, I see in settings new provision profile appeared.
I tried to install same app on 2nd iPad and it fails during installation process. And what is strange it installed old provision profile to my settings (I think this is some kind of caching or whatever). I deleted all apps, all profiles and reboot - but no luck - I can't still install this app to this particular iPad.
May be someone had same issue, please assist me how should I clean cache if it's related to caching issue.
P.S. I want to fix it without wiping the device
Is your second iPad connected via USB to your development computer while you're doing this testing? If it is, Xcode's Organizer will often just restore the provisioning profile that you're trying to delete. If this is the case, try deleting it from the Organizer as well.