I recently updated my organisation developer program so I can use it one more year, but now my apps seem to be impossible to install, I got this famous error :
app_name can't be installed at this time
I got this problem on the App Store and for Ad Hoc distribution as well.
My certificates and my provisioning profiles are fine.
Did someone have the same issue recently ?
What could it be ?
Thanks in advance for your answers !
I believe you may have changed your app build settings and are likely not building with the enterprise distribution profile. That error usually means you are building with a regular development provisioning profile and the device's UDID is not in the list.
Verify your app's build settings are set to build using the Enterprise Distribution Profile.
If you do not believe that to be the case, post the Console logs from the device during an install attempt to find the actual error.
I finally found where the problem came from and it is a bit stupid. Actually, someone in my team recently changed our certificate on the Apple member center but didn't add this certificate to our build server.
After adding the certificate to the build server, everything worked as expected.
So as the title says, I am trying to pre-release an ios8 app. The app is uploaded successfully from the archive and appears under pre-release. I press on submit for beta release and add internal test users. In testflight the app appears, but when I press install it says:
"Could not install app, testflight is currently unavailable. Try again later".
This makes no sense. I tried recreating the developer profiles, I tried it on different devices with different account... always the same. Any ideas?
I re-downloaded the distribution profile for the app and re-archived the app. Now TestFlight works. Make sure that you select a Distribution profile (not Development)
Full description with pictures ... https://stackoverflow.com/a/30801899/294884
I had the same issue with one application for internal users... This worked for me:
Go to Prerelease -> Builds
Turn Off Beta Testing
Refresh testflight at your device (Build will appear as unavailable)
Turn On Beta Testing
Refresh Testflight at your device and install
Same error. My provisioning file was inactive in iOS developer portal as my certificate was revoked by other developer. I'd to activate the provisioning file with new certificate (exported from keychain by that very developer). So, I'd to use these new provisioning and cert to archive my app.
None of the solutions worked for me. I had the problem, that I couldn't update the gems version (an earlier version was already installed) with the same error message.
Turns out, re-inviting the affected user solves the problem.
I have two iphone devices( 4s and 5 ) connected to my computer and i am trying to install an application in both the devices. It installs pretty well in iphone 5 but it gives an error 'The application could not be verified.' when attempted to install in the iphone 4s device.
The UDIDs of both the devices have been added in the provisioning profile generated for the application.
Also, to add a note, I have just updated my iphone version to 8.1.3 in my 4s device. I am not sure though if the error has anything to do with it.
Any help on this would be much appreciated. I have been stuck on this for some time now.
EDIT:
I just connected this to another iPhone device and the issue seems to be there again. Basically this means that the app, for some reason, installs only in the phone which I have been using for some time now and not in any other phone. Once again, I am pretty sure that the provisioning profile contains the UDIDs of all these 3 devices.
I had something similar happen to me just recently. I updated my iPhone to 8.1.3, and started getting the 'application could not be verified' error message from Xcode on an app that installed just fine on the same iOS device from the same Mac just a few days ago.
I deleted the app from the device, restarted Xcode, and the app subsequently installed on the device just fine without any error message. Not sure if deleting the app was the fix, or the problem was due to "the phase of the moon".
As I notice The application could not be verified. raise up because in your device there is already an app installed with the same bundle identifier.
I got this issue because in my device there is my app that download from App store. and i test its update Version from Xcode. And i used same identifier that is live app and my development testing app. So i just remove app-store Live app from my device and this error going to be fix.
just delete the app and try again, it happens to me when i try to launch over a device that has the same app but generated by an ipa file.
You probably used the "Fix Issue" option in Xcode when plugging in a new device. Old question but I believe this is the actual answer to WHY this is happening. When you install an app on a device it is signed with a specific development provisioning profile. If, for instance, you plug in another device that is not registered on your developer account Xcode will ask you to "fix the issue". When you press that the device is added and another provisioning profile is created/modified. If you try to overwrite an existing app you'll receive that error. Deleting the app and reinstalling it works since the profile has been altered. I find this often happens when a Team is set and a member plugs in a new device then Xcode "Fixes" the problem.
Might have figured it out... Deleting the app from the device worked for me, as others mentioned before (thanks!).
I think the reason is that the app on the device was actually signed with a separate provisioning profile, specifically a distribution profile in my case.
I faced this issue a lot. I am not sure if this is the issue, but I think, when xCode saw that there is an app with the same bundle identifier as of the app, I am trying to install, it didn't allow me. So, I had to delete the older one and attempted to install and it worked. However sometimes for testing purpose, I needed multiple version of the same app and in that case, I would change the bundle identifier and try to install. It only works if, I am using an wildcard provisioning profile.
To others not using RubyMotion and don't think that deleting the app is acceptable (as in, you want to do upgrade testing). Check out the bottom of these docs from Apple:
https://developer.apple.com/library/ios/technotes/tn2319/_index.html
It looks like they changed something in 8.1.3 to check for this new rule.
The Fix
"[Add] the installed application’s application-identifier value, as logged in the second parentheses, to the previous-application-identifiers entitlement’s array value for the app being installed (by resigning it or re-building it) and requesting new special provisioning profiles as shown below."
<key>previous-application-identifiers</key>
<array>
<string>{Your Old App ID Prefix}.YourApp.Bundle.ID</string>
</array>
EDIT:
In order to do this, you need special provisioning profiles. You can request these from Apple:
"To enable signing with the previous-application-identifiers entitlement new special provisioning profiles are required that can be obtained by going to the Contact US page and requesting them." (from the docs linked above).
Had the same issue on my iPad running 8.1.3 Deleting the app and installing again fixed the issue. I use two different provisioning profiles on two different machines and that could have caused this issue.
Working & tested solution, which does not require to delete application:
It looks like AppStore Distribution Provisioning Profile or just iOS Distribution certificate have special permissions and "Could not be verified..." problem does not apply to them. They will always override previous certificate.
In other words: AppStore release will install successfully, even if already installed (testing, adhoc or enterprise) app has been signed by the certificate from different team.
If you are lucky and have previously uploaded app to the AppStore account owned by the same team as in certificate you have a problem with - then things are very simple: just download & install app from AppStore.
When it installs - app certificate will be the same as the one you want to test with and problem goes away.
If your app is not on the AppStore yet - iTunesConnect beta comes to the rescue:
Disclaimer: I did not tested this but since cert an prev are the same as AppStore release, I bet it works:
Archive your app with AppStore provisioning profile (iOS Distribution cert) and upload to iTunesConnect (to the account owned by the same developer team as included in the provisioning profile not you want to run).
Invite person with the device you want to run on (yourself?) to beta test.
Download & install the app from iTunes connect beta.
Now you are able to install your testing version.
The application could not be verified" , in your device there could be already an app installed with the same bundle identifier.
So Simple solution Just delete the App & try again..
....
TL;DR answer - There is no real solution besides "delete app and reinstall".
This answer is not satisfactory for many situations, when you have an existing database that needs to not get deleted within the app.
Lukasz and plivesey are the only ones with solutions that don't require delete, but neither worked for me.
I resolved this issue by changing the Build System to legacy in xcode.
I had the same problem but the mentioned solutions above didn't work for me. Even I had no previous app on device, I got this error when deploying on my device.
How to do:
Simply, go to menu File > Project Setting, inside Share Project Settings, change Build System from "New Build System (default)" to "Lagacy Build System".
I also encountered the same issue. Deleting the app didn't work, but when I tried deleting another app which was the current one's 'parent'(I copied the whole project from the previous app, modified some urls and images, then I clicked 'Run' and saw the unhappy 'could not be verified' dialog). Seems the issue is related to provisioning and code signing and/or some configurations of the project. Very tricky.
I had changed the team but I forgot to change it in my Tests target it so it caused that. Maybe this helps someone.
Just had the same problem and I found out that the issue is with expired certificate.
My app was distributed (AdHoc) through firebase and few days ago app was working just fine.
Today I've realized that I can't install it because 'The application could not be verified'.
Finally I realized that certificate that I was using for app signing has expired 2 days ago.
You need to upload it again and you'll be able to install it.
I had the same problem. But, I realised I was using a single plist with (debug) and (release) configuration, like this.
So, I changed few things..
Keeping a separate scheme for (release).
I added a new scheme for development purposes.
Edited the new scheme > run > Build Configuration > and set it to (release)
Generated a new archive using the new scheme and voila!!..
I'm able to install on all my devices.
My case:
jailbreak'ed iPhone
Final solution:
Install tweak AppSync Unified via Cydia
to bypass signing/certificate verification
Same issue occurred for me when I was installing through link. I tried to install using different link. Then I could install the app.
I am working on xamarin for ios.
Its was working on my older machine. But, then i had to switch to new machine and recreate all the certificates and everything for the new machine.
I have created the app ID. Then created the aps certificates and then created the provisioning profile.
In Debug I have provided the downloaded provisioning profile. But still I am getting this same error. And my app is unable to get the device token.
I am searching a lot since last night. And have done the following things with no success:
Regenerating provisioning profile and trying with the new one
I also deleted the app id itself. Recreated everything from start. All Certificates, app id, provisioning profile
Deleted all the provisioning profile from my system and device. Created new profiles and installed them.
Above are three most common solutions i found in my searches, but to my dismay nothing is working for me.
If you have any idea please throw at me. I am in a great need for that. Its holding me from submitting the app.
Please help.
The problem was xamarin studio itself. It seems that after updating form stable 5.2/5.1 version to 5.3 this issue surfaces. So i deleted the app and installed it again which game me v5.2. Now i am not udpating till i publish my app.
This link is full of people facing this problem:
http://forums.xamarin.com/discussion/22502/xamarin-studio-5-3-push-notification-error
did you add the App's Development SSL Certificate to your keychain? when enabling push notifications for the App ID you should generate a Development SSL Certificate for the App, download it and add it to your key chain.
I know there are already several questions on the subject, but I am really desperate. I don't know what else to do than to look for an advice here.
So, I have an app ready to be uploaded.
I have checked all the pre-steps, before trying to upload:
Bundle ID matches in info.plist, iTunesConnect, Apple developer, Provisioning profile
Game works perfectly when I run it on the device, in app purchase works with a test user, and not a single issue appears
Here are some screenshots with some info:
What I have noticed is that there isn't any Provisioning Profile selected:
Yet, when I select the provisioning profile I made earlier, I get this error. When I clock "Fix" it changes it back to none provisioning profile selected.
I don't know if that's the cause of the trouble
All in all, this is the Error I get:
This is my first time that I'm uploading an app with in app purchase. So I might missed some obvious step. I really hope that somebody will see the problem here, because I've been trying to fight this for 2 days now :(
When you see "iPhone Developer" in the code signing identity, that means Xcode will automatically select a matching identity to sign the app (It doesn't mean that no profile is selected).
From what I can see it looks like "iPhone Developer" is chosen for both Debug and Release configurations which will likely cause a problem because you cannot submit a Developer signed app to the App Store, it must be signed with a Distribution certificate and Distribution profile.
You will need to ensure that you have created a Distribution Certificate and profile to sign your app with before archiving it and submitting it via Xcode.
I would recommend you read up on how app store distribution works from the Apple documentation here:
https://developer.apple.com/library/ios/documentation/IDEs/Conceptual/AppDistributionGuide/Introduction/Introduction.html
Then if you still are having trouble, read the trouble shooting guide from the docs here:
https://developer.apple.com/library/ios/documentation/IDEs/Conceptual/AppDistributionGuide/Troubleshooting/Troubleshooting.html
I have had a similar problem. We received an APP from an external provider and re-signed the APP ourselves using our own certificate and provisioning profile. When uploading the APP with Application Loader I received the error ITMS-90167: No .app bundles found in the package.
I have sierra installed on my Mac and I am using XCode 8.0 but had an old version of Application Loader (3.0) that was installed separately. Using this version of Application Loader I got the message. If I instead used the Application Loader that is part of Xcode (from the XCode/Open Developer Tool menu), ie version 3.6 everything worked out great and the ipa file was successfully uploaded to ITunesConnect.