My device is registered in the distribution provisioning profile, the profile is uploaded to Test Flight, a build is prepared and sent to my device. I got the email, clicked in the Install button, and I start getting a screen with button that says Reconnect Device, I connected my device through Safari, logged in to test flight and TF said that my device now is successfully connectedso I build another ipa and sent it to my device, but gotting always the same issue, Reconnect Device button. Am I missing something? Thank you.
I had the same trouble recently. Tried reconnected my devices (2) a few times, only to find out that their UDIDs got changed in TestFlight on uploading a new build, so the build was still not available for my devices. I tried removing wrong UDID's in TestFlight, keeping the right ones, but it didn't solve the problem.
What finally helped was this:
removing all apps installed from TestFlight on all of my devices
removing all UDID's from my TestFlight account
reconnecting my devices to TestFlight
Let me know if it helps in your case. Good luck!
We have received a lot of "reconnect device" messages on iPhones lately and, at least for one tester, we have found a workaround. Instead of following the email links, the user had do install the build from within the TestFlight mobile app.
Related
I have noticed on iOS 15, when I install an app from TestFlight, my app icon is not appearing on the device. Only placeholder for app icon appears on physical device.
All app icon assets for every resolution are correctly added to Assets. The app icon appears in the test flight app and in appstoreconnect everywhere including TestFlight and builds.
The only place it doesn't appear is on the device. It appears normally on the simulator.
The only fix I found was to add a version of the app to add a build where you submit for review and save it. No need to submit. Then install from TestFlight and reboot device. The problem is as soon as I uploaded a new build to TestFlight it stopped showing icon and had to go through this silly process again.
I have never had this issue with past apps and wondering what the issue is and how to resolve it.
I encountered the same issue with testflight on iOS 15. I found this from apple developer forum that might of help:
https://developer.apple.com/forums/thread/682648
According to the accepted answer by #vladweinstein, a temporary solution is to restart the device after installing the app.
This works for me too.
We are still having the same issue with TestFlight apps (iOS 14.7 and iOS 15+)
The only solution we found is to restart the device as Raphael Rex mentioned.
I'm trying to create a project in Xcode, Version 8.0 beta 6 (8S201h) and I'm getting this error.
The apple account is a free one because I'm just playing around with Xcode but it is forcing me to set it as a Team. Any help?
Check the schemes menu at the top of the Xcode project window. Look at the destination you're trying to run in. If you run in the simulator, you don't need to sign your project.
If you run in a device, you need to attach the actual device. It must not say "generic device".
In my case this error disappeared when I changed the "Bundle Identifier" to something less generic (e.g. adding some random numbers at the end)
Change the bundle identifier to something more unique.
If you are following a tutorial and just put a generic identifier then adding a few numbers to the end will likely solve your issues.
i.e. if you had HelloWorld change it to HelloWorld12345
After struggling for an hour, I just unchecked the "Automatically manage signing" and went back to the old school way of specifying my profiles. Probably not the best thing to do but works.
Profiling your Phone takes a few minutes. . . watch the status bar on the top to be sure that your phone is being profiled on the top.
Next, be sure you choose YOUR PHONE as the target, not iPhone 7 or iPhone 8... your exact phone. This is done by choosing: Product > Destination > (pick your phone)
Your phone will only show up after it's been plugged in, turned on, and left running for a few minutes while Xcode creates a profile.
Check these things.
1.A device is connected to your system or not.
2.Deployment target in xcode. (General->Deployment info->Deployment target)
It should match with the ios version of your device.
3.Change your bundle identifier. Follow general rules of setting a unique bundle identifier for yourproject while running in device.
See this what is correct format of bundle identifier in iOS?
Also be careful with the number of bundle identifiers you set in the project. Please remember all bundle identifiers or note it down somewhere. Since you are using a free account you have limited access to the number of bundle id's.
You should also disable push notifications in the "Capabilities" section of the project. Try changing "App groups" as well in the format of group.com.someString.
These things helped me run my app in real device without any errors.
I had same problem with provisioning profile. If you have any kind of iPhone, you can connect to your Mac with cable and provisioning profile is automatically defined.
After some time with the same disturbing error and after I write a unique Bundle Identifier and it didn't help,
I searched the web and found here that my error was that I selected a virtual device and not an real device. The solution was:
1.I plugged my iPhone
2.I clicked on the button - set the active scheme. and there it was on the top - device iPhone.
the error has gone.
I have had this error multiple times and what solves it for me is the following:
In the list with the view of all certificates, right click on each row and move each certificate to trash (go to Xcode > Preferences > Choose account > Click View Details)
Go to member center download the right certificates again and click on them so
Restart Xcode
Go to build settings and set the right Code signing for debug/release - you should be able to see an option on the row that says "Identities from profile..."
If this doesn't work then you should consider revoking your certificate and then create a new one and the do the steps above again.
The issue behind this error is Unavailability of App ID with given Bundle Identifier
Solution: Change Bundle Identifier simple :)
Adding this because it took me 4 hours to figure out..
Xcode will fail to create the provisioning profile for a device with no name, i.e. "" or " ". When I changed my device name to something else, the steps above worked.
Both of these errors arise as a result of a provisioning profile not existing. To create one, simply do the following as suggested in the error message:
Plug in your Apple device
Choose the device from the schemes/simulator menu
Thereafter, provisioning profile will automatically be created
This error is because you selected a target rather than a project name, so please, at the left side of general in Xcode you will find your project name. Click on it and change it from target to project section.
Change Deployment Target to newer version and then solved
For me this happened when I was making a tvOS app and didn't have a appleTV registered.
In general, you need to plug in the device or have logged into it (connected to it)..then it shows up here: https://developer.apple.com/account/resources/devices/list
You can also add devices there..you need to click reset to be able to add a new device. the reset button should be labeled modify because it doesn't reset anything.
for example, if you need to make a tvOS app then you need to have an apple TV in the device list. Once you add that then you're good to go. kisses.
Manual:
Go to your apple developer account and hit certificates
Select devices from the left side
Add the device name and its UDID. Close Xcode and hit automatic signing
Automatic:
Attach your iPhone to Xcode. and run the app on that. Xcode will automatically create a profile.
To set up WITHOUT an iPhone, you can manually download certificates from Apple's website and create a profile. The certificates you install on the Mac and the Profile you import into XCode after download. It worked for me. Follow the links:
Documentation:
https://developer.apple.com/pt/support/certificates/
Certificates:
https://developer.apple.com/account/resources/certificates/list
Profile:
https://developer.apple.com/account/resources/profiles/list
It's just as it says.
To have xCode automate something, you need to get your own iPhone registered there with the UDID, which you can find on Finder or System Information (USB section) when you connect to your iPhone.
Failed to create provisioning profile. There are no devices registered in your account on the developer website. Select a device run destination to have Xcode register it.
Adding a fake device on Apple dev account helped me since I have no iPhone:
https://developer.apple.com/account/resources/devices/list
Example of device you can add:
Name: "NotARealDevice"
Device ID: "1234567890123456789012345678901234567890"
For me this happened when I tried to run on a device with a newer version of iOS than supported by the version of Xcode I was running.
There are basically two way to solve the issue.
Add a device on your mac. Then you can choose that device by selecting Product => Destination => Select your connected device. After this, Xcode will try to add the device in apple developer platform and also create a profile against the same.
Go to https://developer.apple.com/account/resources/devices/list. Add a iPhone device by providing device name and device UDID number. you can google it (How to get the UDID number for iphone). Then you can create the profile and then retry.
By adding my iphone device here solved my problem.
https://developer.apple.com/account/resources/devices/list
and getting apple UUID use this website https://udid.tech no need of xcode and itunes.
Change bundle identifier, Straight solution
What saved me from this error was when I changed my Bundle Identifier.
Try and do that
Just updated to Xcode 7.1 and getting this error.
Was able to upload fine using 7.0.1
Hmmm, well a restart of Xcode, a fresh clean, build and archive seems to have fixed it.
If you encounter this error, you have two options:
Option A - Engage in an activity that takes a minute or two. Could be any of the activities described in the other answers, like re-install XCode, renew certificates, do a new build from scratch after clearing caches. Or simply go get a coffee.
or
Option B - Do nothing at all for a little while.
Then, try again. If it doesn't work, repeat.
Just updated to Xcode 7.1 and getting this error. Was able to upload
fine using 7.0.1
same here - restart, clean build, archive and upload was successful.
Same problem here. Grabbing a cup of ☕️ worked for me.
Exporting the app as an .ipa and uploading via Application Loader 3.0 worked for me. (Restarting xcode, cleaning, and re-archiving did not.)
I first tried to upload and got the "cannot verify client"-error.
Then i did a validate, which was successfull and then again a upload which also was successfull. No restart etc. needed.
Same problem here. Clean build and deleting project caches worked.
Had the same issue and tried everything including Application Loader but still would not load into iTunes Connect. I'm running XCode 7.1.1 and OS X El Capitan.
I also have Avira (free version) installed and once I disable it, everything went through. Hope this helps someone.
Stackoverflow has been my savior and goto source for Obj C and now Swift!!
I had this problem for all night. Got 🍵 ☕️🍺🍼 but didn't work.
Solved my problem only with:
Switching lan to wifi connection
Uploading App by Application Loader
Wasn't useful but i saw than in Xcode uploading start works as well after connection switching, so maybe was a connection my problem.
Clean project not work with me in XCode 7.2. But I solve the problem by export Archive and using Application Loader.
Step:
Archive you build.
In Organizer: Chose your archive.
Export "Save for iOS App Store Deployment".
Open Application Loader (Xcode -> Open Developer Tool -> Application Loader: Download it if you don't have).
Select "Deliver your App" -> Select your exported ipa.
Upload.
=> Done
I've been having this problem since Xcode 7.1 (for more than a month). I did everything I could trying to solve this: restart Xcode, clean project, clean build folder, build with a device connected, reinstall Xcode multiple times, even formatting the whole disk and starting from scratch. None of this worked.
During this time my colleague was always able to upload the very same builds to App Store without any problem.
Curiously, what solved this problem for me was disconnecting my non-Apple wireless mouse.
I found this out when I tried to submit an app from my home computer and got the same error. I disconnected the mouse dongle, tried again and it went through.
I've verified this three times both on my home (MacBook Pro 2013) and work computer (Mac Mini 2014).
This leads me to believe that during the app submission process Apple may check if your environment is purely made by Apple or not, and may block your submission based on that. This would explain the "Cannot verify client" message.
For what it's worth: I got this error when my startdisk was almost full (less than a few hundred MB left).
Cleaning up some space and re-submitting resolved this issue.
Experiencing the same problem. Tried a number of the suggestions above. Ended up using the Application Uploader instead.
Xcode > Open Developer Tools > Application Loader
From the rest of the answers it seems that a lot of different things "resolve" this issue. Here are the particulars of what solved it for me:
The iPad had to be plugged in.
The iPad had to be signed in (i.e. not locked).
After I satisfied those two conditions, it validates and uploads reliably. If either one isn't done, I am not able to validate or upload to iTunesConnect and I get the Cannot verify client (3000) error.
You can use Application Loader to upload your build and solve it!
Download Provisiononing Profiles of app on Apple Developer,
Quit and restart Xcode,
Run Provisiononing Profiles by Xcode,
Open app again,
In General -> get "fix" at Identity.
You can Archive and Upload to Apple Store
When it fails two times in a row, choosing "Validate" and after that "Upload to App Store" does the trick for me.
I tried most of the things here, but what finally did it for me was using the Application Loader instead of trying to upload my app from the Organizer.
Once I did it from the Application Loader I got an error message related to this: ITMS-90535 Unable to publish iOS app with latest Google Signin SDK, which was the real cause of the error.
I remade the app with "App Store" provisioning profile. Earlier it was "Ad-hoc" provisioning profile.
I submitted the app from "Application Loader" instead of traditional "Organizer".
Above two steps enabled me to submit the app to iTunes Connect for beta testing also.
There is always an element for surprise whenever apple releases an updated XCode.
After trying a few things, this is what worked for me:
Just before uploading your executable, validate it, you then have a modal where you get to pick your binary. On the right, there's the name of the provisioning profile used. There's an arrow next to it.
Click on the arrow which opens the finder to the location of the provisioning profile.
Delete this file.
Restart XCode
Clean
Rebuild/Archive
Upload
Xcode gives me this message every-time I try running my app on my iPhone. (Works fine on the simulator.) (And this occurs in every project I have.) (I also just downloaded Xcode again.)
This is the message I get.
App Installation Failed.
Unknown Error Occurred.
How do I fix this error?
Unplugging iOS Device and plugging it back it in fixed it for me.
Alright, it was a simple fix:
Go into Xcode Preferences -> Accounts -> More Info. Hit the refresh icon.
Clean your project. Project -> Clean.
Force quit Xcode.
Reboot Mac and Device.
If you have the same App but downloaded from AppStore, I suggest to remove the App manually from your device, then try to run the new version with XCode.
After following the suggestions in this thread (restarting iPhone, cleaning Xcode project, quitting and re-launching Xcode) and others (setting Team to None then back to my Team) and unplugging and replugging Lightning connector from my iPhone 6 I was still experiencing this problem. Xcode would even display an error that my iPhone 6 was locked, even though it was not.
I was able to fix it by unplugging the USB-A connector of the USB to Lightning cable from my MacBook Pro, then plugging it back in. I'm not sure why that made the difference, but glad that it did resolve this annoying problem.
I have this issue regularly. There are a number of techniques that help me overcome it, including the classic "turn it off and back on again."
One thing that isn't mentioned here is that the iPhone should be switched on, unlocked, connected to the mac and then the app should be run (with the iPhone unlocked). Don't lock it!
Make sure your device name doesn't have any emoji (Xcode 11.0)
if you using vpn services, then you need to turn off vpn. Works for me
Using Xcode 4.5.2 and building for iOS4 or newer, I get this message when building for my device (iOS 6.0.1 on 4s). I dismiss the dialog then relaunch the app on my device which seems to work. I am newer to iOS development, so I aplogize in advance if this is a silly question.
Thank you in advance for your help.
My issue was using Distribution provisioning profile for signing the app, once I made a development provisioning profile, the app installed and ran on iPhone just fine.
The answer seems to be "you need to fix your provisioning profile", but can happen for several reasons, as indicated by other answers on here.
In my case, I hadn't added a new device to an existing developer provisioning profile, so I just re-created the profile with the new device, and it worked!
In my case happens all time I add a new device ID then update the provision profile, download and "install it on Xcode 5".
To fix this:
Go to Xcode>Preferences>Account Tab>Select Apple ID>View
Details>Refresh Button (Bottom left corner).
Reinitiate Xcode.
Start again the app, you will be able to test the app in the device.
Here's what my situation was and how I solved the problem:
I had been running the app from Xcode to my phone and all was fine
I switched to a different code signing identity (I had to change the bundle name also to match)
I ran the app to my phone and got the error. The app would install, but not open.
Did a bunch of stuff like Clean, close n open Xcode; delete the app from the phone. All to no good effect.
SOLUTION: turned the phone off n on.
Coincidence? I think not. :-)
XCode 6:
Just create provisioning profile for development and assing it to Project -> Build settings -> Provisioning profile
For upload you have to change provisioning profile for Distribution profile.