My client trying to install app using TestFlight it is showing Couldn't Load App (TestFlight couldn't connect to itunes to itunes connect. Try again later.)
I have read lots of blogs and post regarding this issue. And tried many things like :
remove build and upload build again.
remove TestFlight testers and add them again.
un-install TestFlight and re-install again.
Restarting the iPad. And Resetting all settings on the iPad (factory defaults).
But issue was still there. Then finally I have asked to my client, What is iOS version in his iPad? Actually he was use 11.2.6. Then I have told him to update iOS in iPad to 11.3 because I have set 11.3 in project's Deployment Target.
And finally issue have been resolved.
I hope this will help to others.
Related
I have an application built on Xcode. I am trying to add it to my phone for testing but continue to get the message "Iphone has denied the Launch Request".
The app is a tutorial downloaded from Github for CORENFC.
I have restarted my XCODE and Iphone many times with no change.
I also generating IPA and then tried to install, still I can't.
Please Give me any solution.
Have you made sure that you have accepted your app in the developer profiles on your phone? If you want to check go settings > General > Device Managment and it should have your app under the developer app section.
This should be the reason the iPhone is denying the request to launch your app.
Hope I have helped, Toby
My testers have problem with an app I had uploaded to Fabric Beta. During normal testing they uninstall already installed app from their devices and they download new version from Fabric. In that case everything works fine. App will download and launch properly.
Problems begins when they want to test situation when future app's users update my app from AppStore. My testers want to check if updated app will not crash.
Test case is easy:
List item
Download app from AppStore.
Launch it.
Download new version from Fabric (new version should override old)
Launch it.
App should not crash.
Problem appears in (4), Fabric shows error "download problem detected". (Note that everything works if there is no old app on device.).
Fabric has problems with overriding apps?
Fabric (1.7.7)
iOS 11
iPhone 6s Plus
PS. This test is important. Crash will appears when I change database model without migration for example.
Paul from Fabric here. Did you uninstall the App Store version of your app first? Since iOS 9, Apple changed its policy to prevent apps from being installed over the existing App Store version by 3rd parties, so you need to delete the original app before installing the Beta version. For more information, see our docs here: https://docs.fabric.io/apple/beta/tester-experience.html.
And the other reason could be if any other app is installing or updating parallelly, Fabric will not be able to install. Just faced the issue :)
I downloaded Xcode 7.1 from the App Store today after working from 7.1 beta downloads from developer.apple.com and have a new iOS app build to upload. So I did:
Product > Archive
Upload to App Store (or Validate)
But the response was:
You are not authorised to use this service
Intriguingly, when I 'Export' the build to the Desktop and then use Application Loader 3, it uploads without error.
Is this an iTunes Connect bug? Or is there a new Xcode checkbox I've missed?
Note: I've also tried removing and re-adding my AppleID as suggested here, and restarted my Mac for good measure (which actually allowed the validation to work once), but still no luck uploading directly from Xcode > Organiser.
I met the same issue today and I think it is a bug of Xcode 7.1
Finally I managed to submit my app via Application Loader. There were warnings but it did work.
Here are the basic steps:
Archive
Export
Xcode menu --> Xcode --> Open Developer Tool -->
Application Loader
Double click "Deliver Your App" and choose the
file exported in step #2
click next and follow the instructions until
the end
Here's the quick solution:
Don't use Xcode beta versions to submit apps for release — it's beta for a reason and shouldn't be used with production code.
Submitting Apps
Apps that are created using beta versions of Xcode or that are built
for beta versions of operating systems will not be accepted on the App
Store and Mac App Store. Apps that you submit should be developed
using the latest version of Xcode from the Mac App Store and should be
built for publicly available versions of iOS, OS X, and watchOS —
except when GM seeds are available. When a GM Seed of Xcode becomes
available, use it to develop your app for submission. When GM seeds of
iOS, OS X, or watchOS become available, build your app for these
versions.
↳ https://developer.apple.com/support/pre-release-software/
Having the same problems as all of you, just thought I'd share that I found a way to Validate successfully, you have to disable the "Include bitcode" checkbox before moving forward. As for the actual upload to App Store, no work around for that one other than use the Application Loader...
Also I've been seeing this too since XCode 6.4, but it seems once the current version has a couple of months after it's originally released it starts working again... fingers crossed that it starts working again soon, because uploading straight from Organizer is so much better. (I saw the Beta Version post, when I say after a couple of months for current version I'm not talking about Beta versions, just in case ;) )
Same problem here.
Downloaded Xcode 7.1 from the App Store and it refuses to upload a new version.
Happily Application Loader worked ;)
Hopefully this gets fixed quickly.
One possible reason for the issue could be multiple development accounts under one name (personal and company). I've read elsewhere (apple radar) that that caused earlier problems of this kind.
Happens here if the dev account is only admin. I had to use the central account for uploading our apps. I think this problem startet sometime with XCode 6. Didnt investigate further though since Application Loader works in cases when I dont have access to the central account.
I also have the same problem today.
Finally, I used the application loader to upload successfully,too.
Theres a few solutions I have come across to solve this issue.
Most common being to remove and re-add your developer account.
This won't work on its own though, you need to also 'view details' on your account and have Xcode download your provisioning profiles again.
The other alternative is to upload your build using application loader. The disadvantage to using this solution is that should you be trying to upload using a beta build of Xcode or OSX you won't be able to change your apps .plist in the archive folder to trick iTunes connect into accepting it. In this instance all you have access to is your ipa.
Disable the "Include bitcode" checkbox worked for me.
I updated to iOS 8 yesterday and I can not install a testflight build.
It displays the dialog "do you want to install..." I tap yes, and nothing happens. I've heard that that the browser no longer closes, but the application just never shows up with no errors.
I've unregistered, registered, even signed up for testflight under a new account. Nothin'.
Others are able to install on iOS 8. And up until my upgrading, it was working fine on iOS 7.
(This is all through the browser still, not the new testflight application, btw)
Any ideas? Thank you!
Open the link you receive from the iOS mail app (not a 3rd party) and it will work.
We just solved the issue by reset the phone to factory settings. Just be sure to enabled iCloud backup before to restore the device.
All tricks and checks by searching for a code signing issue, profile problem or test flight bug was without success.
The weird thing about the problem was, that it occurred only on one device. 5 other test devices could install the test flight build after the iOS8 update.
I did factory reset and reinstalled my last backup, that worked.
You have probably already done this but you'll need to make sure you download the new test flight app from the appstore too.
Normal HTTP Distribution (without Testflight) is also not working. So it seems like a new security measure with iOS 8.
The only workaround at the moment is installation of an ipa via iTunes.
Try changing the Bundle Id. Worked for me now. There is some problem with previously installed app versions.
We've been having this issue also. Mostly, the 'install' button in the testflight email was absent or didn't work.
Rebooting the phone worked for all of our team members. No need to clear caches, reset settings etc.
Re-initializing TestFlight as described here - http://help.testflightapp.com/customer/portal/articles/867631-re-initializing-testflight-on-a-mobile-device- helped me on iPhone 5 iOS 8.1 with this issue.
Maybe this will help someone. It sure kept me busy for a while, and itunes support gave me the solution.
I am running TestFlight 1.0.2 (55) on my iPhone 5S with IOS 8.1.3 (12B466). I was unable to open my app for testing in TestFlight when clicking on the "Open in TestFlight" link. Apple gave me the following 2 steps that solved my issue
Uninstall and re-install test flight (not sure if this really did anything, but step 2 was the answer)
Click on the "Open in TestFlight" link from the Apple Mail app, not Gmail or something else
My app got strucked on iPad while i try to install ipa from iTunes.I made an ipa from xcode 5.0.2. and my ipad ios version is 5.1.1.Will this be any problem to install ipa.
My ipa is installing more than 50% and from there its not moving further.
How are you installing your app from iTunes? There are many other ways to do it:
With Apple Configurator
From Xcode itself
In the newer version of iOS, I believe that you are able to remove apps that are stuck like this, but in iOS 5, I will try to restart the device and then just tap and hold until it wiggles then remove it manually. Then try to use Xcode or Apple Configurator.
i solved my issue by changing Architecture "Standard architectures(including 64-bit)(armv7,armv7s,armv64)" To "Standard architectures(armv7,armv7s)"
I Though problem is with my provision profile or iTunes.But my problem solved by just changing Architecures in Build Settings.