Related
I am getting message "TestFlight is Currently is Currently Unavailable. Try again later" when trying to install from TestFlight app. My outside testers get a message "[App Name] beta has expired" when trying to run the app. When trying to renew from TestFlight they get "TestFlight is currently unavailable. Try again later." I've been trying again later all day and just wanted to see if anyone else is experiencing this.
I had this same error.
Discovered that the company certificate was expired, and therefor all provisioning profiles as well.
1. Renew the company certificate (download, install on your computer)
2. Renew the provisioning profiles (edit, select new valid certificate, generate, download and install in xcode)
3. Repost the app to iTunes connect
problem solved :)
If you're new to Xcode, be sure to note the difference between a CERTIFICATE (first large red arrow below) and then a PROVISIONING-PROFILE (second large red arrow below). Basically provisioning-profiles are made using a certificate. So first make a new certificate, and then set a provisioning profile to use that certificate.
First, certificate...
Then, provisioning profile...
In the second image, click on the "Distribution" provisioning profile (the one with the purple arrow.) Then click to edit it, and you will then see the third image below. Note that somewhat annoyingly, the DATE is the only way really to distinguish your corporate certificates, when, you have more than one. (Ultimately you can, generally, just throw away the OLDER one, but it's clearer if you leave it so that you can clearly see how you select one or the other, as in this third image.)
Editing a provisioning profile...
A minor point is that you'll have to make a new build (so, increase the build number in Xcode, then archive, and then send up that new one) because you'll get a "redundant build" warning if you fix the cert/profile (i.e., as described in this answer) and re-submit.
Another possible reason for this message:
You accidentally removed the affected user from the TestFlight external testers group.
Adding him again would fix the issue.
Problems with certificates have been identified in several answers as the cause to this message. However, there's another possible (yet stupid) cause that leads to this situation.
You may see this error if your device's date/time is not set correctly. So make sure you set the correct date or "Set Automatically" is enabled under Settings > Date & Time.
I spent 2 days "trying again later" until I realized this.
I was ultimately able to fix this message by uninstalling and reinstalling the TestFlight app from scratch. Worth a try if the other answers don't fix your problem.
Make sure TestFlight can use Mobile Data if working without Wi-Fi. Otherwise it fails with this generic error.
Had to disable 'Use cellular data' option in Settings for Testflight. I did not have cellular data internet and was connected via wifi. Looks like testflight tried to use cellular data with that option being on.
Did a factory reset and that fixed it for me.
Actually just waiting solved the problem.
I had to wait around 16 hours and then it worked normally, without doing anything particular.
Sometimes the error message is just what it is, no need to panic !
Ahh devs ;)
Currently, Testflight is experiencing issues. It's always worth checking Apple's status page
Another possible reason , if your mobile app build is in processing state for a long time.
Just wait for the build to complete apple processing solved our issue of Testflight currently unavailable.
I had this same issue when using my personal email for beta testing my app, then using my apple ID email for internal testing.
I solved this issue by removing my personal email from all testing tracks, then deleting the TestFlight app and downloading it again. I now only use the one email (my Apple ID) for all testing.
I had to go to https://developer.apple.com and accept a new version of Apple's Developer Agreement
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.
This must be the worst question ever asked.
I'm almost ashamed to ask it but I can't wrap my head around this.
We are trying to push my app to itunes connect for beta testing.
Now there is no way to do this because XCode 6 gives all signing errors available.
We are able to run the app on the development device just as usual. We have the profiles.
But when we set the release sign identity to iOS Distribution, the hell breaks loose.
No matching identity was the first error. Fix issue releases another error:
No provisioning profiles with a valid signing identity were found.
It's useful to note that XCode knows this better than I do so it changes the code signing identity back to developer.
That's not me, I want to distribute.
Ok so at this time we're stuck at this error. We don't know where it came from, but we do know there was another error.
While pressing the submit button in the organizer the error was:
"You already have a valid provisioning profile"
According to the apple documentation I should press the revoke & request button but that isn't there.
So here we are, totally stuck and have no idea where to go now. The apple docs are incomplete, the signing gives errors but no logs. Errors messages change, but are consistent.
What the hell should we do now?
Reinstall OSX and remove all existing profiles? What will happen with current clients running apps on those profiles?
Have a look in yoru account and check that the provisioning profiles are active and not invalid. You might need to regenerate it.
You might also want to download them manually and install them yourself.
Sometimes I've had to archive the app then submit 'manually' using application loader.
I would recommend going back to basics:
check your development and distribution profiles on the developer site. if you have recently renewed your annual subscription, you might need to recreate them.
when you are archiving make sure you chose the real testing device, not a simulator.
if both doesn't work, create a new empty project and sign it with the profiles and archive. if that works, then check if you altered the bundle settings. if it doesn't work, delete your profiles and recreate them.
I hope that helps.
Hmm. I understand the plight of having to deal with the overly complex process of app submission which should have been rather simple.
Two things:
Make sure you delete all the provisioning profiles. Revoke and request a new one. Create a new certificate with distribution licence (you can make upto 3).
Once you've done that go to tour XCode > Preferences > Accounts and open up the apple id you find there. Refresh and that should download and fix redundancies.
For more I think you should also give this a read.
How do you beta test an iphone app?
About you second issue. What would happen to apps packed with previous profiles?
Well, your app is not bundled with a particular profile and so you can create a new one and use that without pain
When I try to test my app on my jailbroken 5s I keep getting this error for some reason, it just started happening as well... I was able to test on my apps on my device this morning but now it doesn't work, and yes I tried restarting xCode.
Error message:
The identity used to sign the executable is no longer valid. Please
verify that your device’s clock is properly set, and that your signing
certificate is not expired. (0xE8008018).
My device time is set to automatic so I don't see how it could be incorrect, and the certificate is still valid, I just made a new one...
Please don't tell me I need to pay the 99 dollar developer fee to do this. I am jailbroken and I will not do this, nor will I install app sync as I didn't need it installed before. I have already created a self signing certificate and everything, even edited all the plist files and changed the build settings in my app, nothing works.
Did you try to reverify the device in Xcode? If not try that. Else something tells me the system discovered your self made certificate.
You can't use self-signed certificates with Xcode to my knowledge. You must use an Apple-issued certificate to publish using Xcode. There are special ways to install self-signed apps on jailbroken phones, and Xcode isn't one of them. In theory, you could modify the Xcode project's build procedure to use this special method, but it really isn't worth the hassle in my opinion. If $99 is honestly too much for you to have access to Apple's awesome developer community, then Android will always accept new developers. Just remember that $99 is not much money for most in the developed world, and if you own a Mac and an iPhone (or several) then you certainly can afford it, and it's definitely worth the money considering what it gets you.
I have the following error when I try to run a new project on my ipod:
Error launching remote program: failed to get the task for process 312.
The program being debugged is not being run.
I've read about Entitlements.plist, and I've tried to add the get-task-allow, but then it doesn't let me compile because of a code signing error. I only have a development provisioning profile, so it's not the same as the people who were trying to debug the distribution build (I'm also in the debug build, so that isn't a problem).
Old projects build and run fine on the ipod, just new projects.
I've tried restarting both xcode and my ipod, but it doesn't help.
I have no more ideas on how to build/run new projects on xcode, so any help is much appreciated!
Oh, and I'm using an iPod 3G with iOS 4.0.1. Xcode is 3.2.3 (64-bit).
It turns out that using a different provisioning profile (one with a wildcard rather than one without) solved this issue.
The key point is to use a Developer profile rather than a Distribution profile.
Check that you're doing signing using a development provisioning profile, not a distribution one.
This error happens when you have set Distribution Provisioning profile in code signing. Change it to Developer Provisioning Profile, then it will work. Worked for me for Xcode SDK 4.5.
There is also a case that your error would happen.
If an app with same Bundle Identifier is launched at background ( probably an App Store version ), Xcode debugger will not know which App it should attach to. To solve it, remove/uninstall the App Store version, and click Run in Xcode again.
The same story can apply if you once build the app with a bundle id then you changed the project bundle id and still kept both app versions. make sure you remove the old one.
If your certificates are not quite right or have become not quite right, this problem can start to happen and you can go round and round playing with provision and entitlement files to no effect. (In nearly all cases, you don't need an entitlement file.)
I'm talking here about debugging on a tethered device in "debug" mode, not any sort of "release" mode.
Here's how I finally determined this was the problem and fixed it:
1) Try to create the simplest Xcode project possible and in Target...General set it up for your "Team". (If you find this impossible to do, that already is a sign of this sort of problem.)
2) Tether your device and try to run on it. Normally, this would go smoothly, but if the opening screen appears on your device for a second or two and then the app crashes and Xcode says it can not attach to some positive task id, then you may have the sort of problem I had.
3) So I then went to another Mac with Xcode and did the same thing, letting Xcode 5 automatically get the needed credentials. (I'm using a "wild card" * app id for all of this.) In my case, much to my surprise the simple app I created on the new Mac ran on the tethered device just fine keeping up its opening screen indefinitely. What a relief. So I then went to keychain access on the new machine, exported all of the relevant keys into one file and then exported the relevant certificated to a .p12 file. I also made a copy of the new working project to take back to the first Mac.
4) Back at the first Mac using the app for the second Mac, it had trouble with the Team ID when I looked at the Target...General screen. Your symptoms might be different, but the point is I couldn't rebuild the app from the second Mac on the first Mac.
5) So I then opened up Keychain Access (possibly not necessary) and double-clicked on the files I brought over, first the one with the keys and then the one with the certificate, providing the p12 password when requested. (Some of this may not actually be necessary, but I'm not sure which and I am describing what worked for me.)
6) I did step 4 again and this time it worked fine! I then found that the other programs that were giving me the "failed to get task" problem now worked fine, too. I just wish I could get back all the time I lost before I tried the process described here.
Conclusion, something was wrong or had become wrong with the certificates or the keys on the first Mac. It was subtle enough that I could still do builds, make ad hoc releases, etc. but I could not run on a tethered device. Though I don't think it is a factor, I was using a corporate developer account and this Mac was set up to do development for several other developer accounts (and these did not display the problem).
After Xcode 5.0 tried and failed (it hung) to update certificates, ... which it suggested me to do. All I did then:
Restart Xcode 5.0
Open Window > Organizer
Select Devices at the top
Select my device (which had a green bullet)
Click the (+) Add to Member Center at the bottom and follow the few simple steps
Go to the Apple Developer Center and make sure that your developer certificate has not expired. Mine had expired so I renewed it and then went back into Xcode (5.1.1) and under accounts preferences I viewed the details of my apple account and hit the little refresh button at the bottom. My iOS development signing identity showed up and I was back in business.
Removing distribution profiles from device in Organizer solved this issue for me
1.Run the Application using development certificates in both debug and release area in code signing identity.
or
2.Use the development certificate in debug area and distribution certificate in release area.