Since upgrading to iOS 6 I have been unable to install the "TestFlight Access" profile, and my clients running 6.0 are experiencing the same issues. I have googled the issue but I am not finding any results.
The error message is just after you enter your device password and reads:
"Profile Installation Failed
A network error has occurred"
I have verified I have a good network connection, and the error is happening at multiple physical locations (different service providers and internet access)
Thanks in advance!
I just had the same problem with our build and one of our testers found this solution:
" advise people to go to settings > general > profiles and remove their profile and then clear cookies / cache, reboot the phone and it should work"
Make sure to remove the TestFlight WebClip profile as well.
Hope this helps!
Ryan
Related
I'm trying to upload a new build to the app store connect. I usually use my CI for this but since the boss forgot to renew the CI's plan, I need to do it manually from XCode for now. Building and uploading from CI always work so far.
So I've Archived it successfully. But when I tried to Validate or Distribute the app from the Organizer, it failed with the error:
No accounts with App Store Connect access have been found for "TEAM_NAME". App Store Connect access is required for App Store Distribution.
I am using XCode Version 11.6 (11E708), and have already added the account that has App Store Connect access to XCode. The account has the admin role. So far, these are all the fixes that I have tried to no avail:
Restart XCode
Restart Mac
Delete and add the account again
Delete DerivedData
Redownload the certificates and add them to Keychain
Change the signing type to Automatic from Manual, or vice versa
Make sure to disable my VPN
Any combination of the steps above
I have also tried exporting and uploading using xcrun altool --upload-app but it returned these errors:
2021-01-19 22:03:00.239 altool[6155:75984] *** Error: Connection failed! Error Message - The request timed out.
2021-01-19 22:03:00.404 altool[6155:75978] *** Error: Error uploading 'Kolibree.ipa'.
2021-01-19 22:03:00.404 altool[6155:75978] *** Error: code -1011 (Unable to get authorization for username 'USERNAME' and password provided. Authentication failed.)
The network is most certainly working so I don't know why it timed out. Is it from Apple's side? Can anybody help me here? Thanks in advance.
UPDATE: I'm still using Catalina 10.15.4. Does that make any difference? Should I update my macOS?
Okay, after looking it up some more, I found out that the culprit is the ISP. It was blocked by the ISP since I can actually upload when I tethered to my phone. I've also checked the router and it doesn't have any firewall so it's definitely the ISP. Maybe I'll try the steps in #Paulw11's comment in using port 443 to upload now. Thanks.
UPDATE: After more investigation, it is actually much more silly. The ISP injected their ads into the packets that use any port except 443. And that includes uploading the app to the App Store. I tried turning on my VPN and it worked because there's no injection. Thanks again.
For error "Error Finding App Store Connect Credentials", Please go to Xcode>Preferences>Accounts and see if your app store account has been added. In some case when you update the password you need to provide your credentials again here to upload the build to app store.
I distributed version 1.0, build 1, of my app via TestFlight, and everything worked perfectly.
Yesterday I archived and sent out build 2, and now upon tapping the update button, every user seems to be getting an error:
Unable to Download App
[App name] could not be installed at this time
I haven't heard from any users who didn't have build 1 installed already, but looking at iTunes Connect, no user has build 2 installed.
Encountered exactly the same problem today, trying to install a new testflight version downloading it through our company WiFi. We noticed that we could still download and install the app from mobile devices through LTE which lead us to the conclusion that for whatever reason testflight must have blocked our office IP (temporarily) for unknown reasons.
I hope this actually works for someone else. I was seeing the same result over and over again. I restarted my phone. I took my account off the Test Flight list and re-invited myself. Same result. 2 other people were able to install, but I wasn't. I furiously tapped "Install" several times as fast as I could, then tapped "Retry" when the alert box came up. Continued to tap "Install" over and over again, then "Retry". Install, Retry, Install, Retry. Then it finally started installing...
I wish I were making this up.
Bump the build number and resubmit your app. This is a TestFlight/iTunes Connect-side error that, as far as I can tell, we can do nothing about.
Update 12/7: The bug I filed on this (rdar://23296795) was recently returned to me as "We believe this issue has been addressed through changes on our side." – So if you're still seeing this error, please file another radar and let them know it's still not working.
Update 12/10: According to Remy in the comments below, it is still not fixed.
For future readers
This could be a Certificate / Provisioning profile issue.
I just had this issue after wiping my mac and reinstalling OS X (i.e. all my certificates and profiles was gone from my keychain), and I did the following to fix it:
Delete / Revoke any existing certificates and Prov. profiles. (In my case Xcode had tried to download the certificates for my old computer, and they somehow became invalid in doing so).
Then, in the following order:
Create a new Development AND Distribution Certificate
THEN create a Provisioning profile for Development AND Distribution
Xcode signs your app with your Distribution certificate when it builds it for TestFlight, or the app store for that matter. That's why it is important to have a Dist. Cert. when uploading to test flight even thought it's just for internal testing. I don't know if it matters wether you have a valid Dev. certificate and Prov. profile for test flight, but it doesn't harm to have it. You need it to build to your phone anyways
I hope this helps.
]
I've got this error many times, but I saw a really strange pattern and I have a pretty weird theory.
Next time, after you submit your app to Apple, don't submit it immediately for beta review. Download the app at least once with TestFlight on your iOS device as an internal tester. Do that before you submit the app for beta review and it should work.
Sounds crazy and I can't really confirm if downloading the app as an internal tester "triggers" anything, but it seems to be working for me that way. Could be a random coincidence though, would be interesting if someone can confirm/deny my theory.
Definitely one of the more annoying bugs of TestFlight right now. :/
Same error for me. The only thing that worked for me was to uninstall the TestFlight app and then reinstalling.
I faced the same issue under the follow case:
Created a Test users group in iTunes Connect even before the Build was approved (i.e. it was in "Waiting for Review" state). We did receive notifications from TestFlight, but when clicked on "View in TestFlight", received this error.
I added the approved build to the Group and Resent the invites. This worked perfect for me.
We had a user who had, for reasons only they know, disabled cellular access for the Testflight app. Later, when he'd also turned off Wifi (again, for reasons...) he was in a situation where Testflight had no connectivity.
The error he saw was "could not load apps". It was driving us crazy as our other users were able to install and run without issue!
I had a previous version of this app with the same name. Just deleted it from my device and testflight installation worked.
I encountered the same issue. Not only it fails in TestFlight but also it is rejected by Apple Team in the submission process for not launching. I was able to solve this problem by renaming Project and Target names excluding wildcard characters.
The names were like following;
I spent almost two days to discover the issue. Hope it helps!
I was able to fix this problem by removing the 0s from my build number as described here.
As funny as it sounds, TestFlight currently has a bug that prevents deployment if your buildnumber has a 0 in it.
Buildnumber 102 failed to install on all devices I tested it on, simply changing the buildnumber to 112 (nothing else changed!) and uploading it again fixed it immediately.
One of my user is having trouble installing the TestFlight App (not Apple's TestFlight).
He encountered the error: "Profile Installation Failed, the SCEP server return an invalid response."
I advise him to follow the steps listed here:
http://help.testflightapp.com/customer/portal/articles/402816-registration-issues
He told me that he has no profile installed in his profiles and after following the steps, he still encounter the same error.
I at a lost as to what to do now and any advise will be appreciated.
I finally got my testers to get past this SCEP error. Hopefully this works for you too.
Workaround:
Open the iOS Settings app, select Safari then tap on "Clear History and Website Data"
Open the Safari app and go to testflightapp.com
Log into your TestFlight account
On the "Connect this device by installing profile" screen, tap the green button "Connect Device"
Tap "Install" on the "Install Profile" screen
If you have an unlock passcode on your device, you may be will be prompted to enter it
When the SCEP error comes up, tap "OK"
Tap "Cancel" on the "Install Profile" screen
You should then be redirected to TestFlight in Safari with the "Device successfully connected!" message
Ok follow these steps,
1 - Delete TestFlight Web Clip or icon from home screen.
2 - Delete TestFlight Profile
3 - Important (Go to Safari in settings and Clear History and Website Data)
Restart your device.
Login to https://testflightapp.com/m/login on Mobile Safari.
Tap Connect Device.
Hope this worked for you :D
Bye!
I just had the same issue. The Testflight-App from the AppStore won't install, saying iOS 8 is required (although we have other iPads with iOS 7.x running the app). The "invalid response"-error occured when logging into testflightapp.com on the device and trying to register it as proposed in testflightapp.com's Help section.
I solved this issue by clearing Safari's cookies and data (Settings -> Safari -> Clear Cache) and then restarting the device.
After going to testflightapp.com again, the device was already connected an everything worked. Hope that helps!
We just saw this yesterday. The issue was the firewall at work! I had the user turn off Wifi and just connect on the cellular network. It worked fine for her then. If the device is an iPod, just wait until you get home, hopefully your home wifi is different from your work wifi.
Looks like it's often caused by firewall rules.
Try using another wifi/cellular network.
https://twitter.com/testflightapp/status/389838663494156290
Sometimes I have selected to build the program under "iOS Device" instead of my actual "iPhone" device. When this has happened none of my users were able to download and this error shows up.
This is also a common issue when you didn't register his UDID correct on the provisioning profile on developer.apple.com. Double check your provisioning profile entry of his UDID and if it is incorrect change it to the correct one. Build, export and upload your app again and it should be fine.
This has happened to me twice. Good luck!
I've downloaded the CloudKitAtlas sample code from Apple dated Sept 8. I did:
Setup the App ID
Enable the iCloud in Xcode capability
Setup the provisioning profile
Login to my iCloud Account in my Simulator (the different account from my developer account).
But the app crashes when I click the Discoverability in application. The error message is:
An error occured in requestDiscoverabilityPermission:: CKError
0x7fd7f162c1c0: "Not Authenticated" (9/1004); "Account couldn't get
container scoped user id, no underlying error received"; Retry after
3.0 seconds>
Do I miss anything setting up the iCloud? Thanks
I had the same problem on my app. Deleting the application from the simulator and restarting it fixed the problem. Take a clean build if necessary
Also, make sure that you are logged in to iCloud in Settings app.
i am developing an native ios application on mac os mavericks image on vmware, i am doing a training in a company. this application contain PushNotification service. i have download a video tutorial and i complete all the tasks as the video show. but in the end when i install the provisioning profile it show this warning message : "valid signing identity not found" . i have work on this issue many days.
i am new in ios developing, so day by day i read questions of developers that have this issue also and i've read the answers and try to fix it but no result.
can anyone help me and guide what to do. down i will notice what i've see and i feel that this could be the problem and i can't do anything:
- when i create the provisioning profile , they gave me numbers of certificates to chose, none of these certificates is the one that i create.
There are probably many reasons for this message and many more potential solutions.
I often see this error message display when building. Quitting and restarting Xcode usually resolves the issue for me.
Have you tried downloading the provisioning direct from apple site? Sometimes I have problems when I try to update directly from xcode.