I had xcode 7.3.1 installed and yesterday downloaded and installed the production release of xcode 8. I click download profiles in my account area and not all will download. I tried deleting all in Finder. I tried clicking the Download button individually.
How do I get all profiles to download?
I ended up regenerating all my provisioning profiles which has worked for me. Quite strange...I don't know why that changed anything.
edit: on further investigation this is still happening...sometimes all our provisioning profiles aren't even showing up in the list to download let alone some getting stuck.
Related
I update my android studio to 3.1.3 but I cannot use platform 27 now
when I click "install platform and sync project" it pop up a download window and then disappear. But the error still exist. SDK Platforms is following:
expand SDK:
For anyone get this issue, you should uninstall Android SDK 27 then re-install it from SDK download manager.
#TrongHiue's answer didn't work for me. (Mac user, Android 3.2.1).
I had to close the IDE, go to Library/Android/sdk and rename the 'sdk' folder to 'sdk2'. Then reopen Android Studio - it will prompt you to tell you it can't find the old sdk folder but will automatically use sdk2. Hit ok. Then, let Android Studio re-index. It will now find platform 27 and you should be able to launch your app.
If you want to change your sdk folder back from skd2 to sdk, close the IDE, rename back to 'sdk', re-open the IDE, update the SDK location in File -> Project Structure, and make sure local.properties is pointing to 'sdk' folder and not 'sdk2'.
In my case, I fixed it by click "Edit" (Next to Android SDK Location) and install SDK platform at SDK Setup window.
Click here to see image
For me neither options worked.
I've updated to SKD 29 and Android Studio 3.6.
What did help was going to the SDK Manager and click the "Edit" link next to Android SDK Location. In the next screen you will see a message saying that an existing Android SDK was detected and only missing or outdated SDK components will be downloaded. Click Next and problem solved!
Ran into same problem but with API 26 and (win) studio 3.5.1. XavierDominguez solution was close to what I had to do to fix it. Close IDE, renamed Sdk to Sdk2, reopened studio, problem persisted so closed IDE, renamed it back to Sdk, reopened and worked this time around. Posted in case someone ran across same problem.
This usually happens when popup for update tools and you click on Update and after some time before finishing Update you Cancel It.
Simply Go to FIle--> Invalidate Caches/Restart
This can happen when your sdk location directory has space in it.
Change directory without space and re-build the project. It worked for me.
Old SDK Location: "C:\Users\DELL 15\android-sdks"
New Location: "C:\Users\android-sdks"
I can't find my newly uploaded build in iTunesconnect when I click "Select Version to Test" for TestFlight.
When I tried to upload again, my Xcode shows:
But where to find my binary? And how to select the newly uploaded build for beta testing for TestFlight? Thanks.
Earlier I had the same issue and got an email from iTunesConnect pointing out some errors in the build I uploaded. It appears you have to address ALL the warnings (even though those are supposed to be OK for upload) before the build become visible in iTunesConnect.
In my case, I had warnings about alpha channels in my watch app icons.
For why can't you find your newly upload versions:
Check your email.And App Store review my send you an email for lack of user usage description.
Add the key and string value to Info.plist that App Store review ask.
And for why you can't upload your binary file again:
There is a 1.0.20 existed in iTune connect. So you need let your version +1. such as 1.0.21.
And every time you try to upload a new version, you must make your version greater than your latest version in iTune connect.
Then archive and upload it again.
Good luck!
I am using Application Loader to upload my .ipa files (created with Adobe AIR v18) to iTunesConnect.
It's been working fine for months, but today I received two new errors:
The u option must have a non-empty value.
The password must have a non-empty value.
Can anyone shed some light on the issue?
I upgraded to Xcode 7.1 and that solved the problem!
Note: Xcode 7.1 comes with Application Loader 3.3.
You have 2 solutions:
1) Update your Xcode to 7.1 (but since you are not coding natively, use the solution #2 below)
or
2) Download and use the Application Loader v3.1 (Download link: https://itunespartner.apple.com/en/apps/tools ) to submit your IPA
Apart from low-belly's answer you can try to use XCode's built-in upload feature. If you go to the Organizer, just click on Upload to App Store:
This solved the problem for me in XCode 7.0.1.
Xcode 7.1 was downloading too slow (more than 4GB) and the update failed every time, so for now I downloaded the Application Loader 3.1 from iTunes Connect and it worked fine.
To download it you login into iTunes Connect -> Resources and Help -> click on View Tools (under the title Other Resources at the bottom of the page) and there is the download link.
I got the same error last night. Fixed it by signing out of Application Loader (3.6) and logging back in.
I got the same error with Application Loader 3.2. Submitting with Application Loader 3.0 (bundled with Xcode 6.2) or 3.1 (bundled with Xcode 6.4) solved the problem.
I'm trying to distribute my iOS app in OTA mode. It worked fine until now, but recently each time I try to export my archive, Xcode crashes.
I'm using OSX Mavericks and Xcode 5.0.2 (all are up to date).
Below is what I'm doing:
Product -> Archive
From the organizer -> Archives -> Distribute
Save for Enterprise or ad-hoc deployment -> Click Next
I select the provisioning profile (ad hoc profile) -> Click Export
Here the finder appears and Xcode crashes.
I tried to repair disk permissions and read the forums for about 3 hours, still crashing !
Any help would be greatly appreciated.
Best
Jerome
Go into the iOS developer centre and accept the new terms and conditions or licensing agreement.
I was having the same issue in both Xcode 6.0 & 6.1, I removed the account from Xcod Accounts & added it again, It worked like a charm
I just upgraded to xCode 4.3 and used it to generate a new revision of an iPad app about 50 beta testers have been using for several months. I distributed the beta app through TestFlight as usual.
Most testers upgraded with no problem, but several testers are getting the TestFlight message "You have not permitted this device to install this build" when they try to install the new rev. I've never seen this message before. Their iPad UDID is definitely in the build's embedded.mobileprovision file and everything was working working fine with the prior revision.
What am I -- or the testers -- doing wrong and how do we correct it?
Hi i experienced the same and it seems that you must generate your mobile provisioner profile from Xcode(instead of Apple dev site for example) and you should update your App permissions (TestFlight) with this same provisioner profile that you just generated on your machine so basically the machine that generates and archive the apps using Xcode must generate the provisioner profile and then you should update your testflight app permissions with this file.
Does that make any sense?
Hope this works for you testflight is really nice to use, i faced same problems with all of my apps and hardware devices (testers all around the world)
Thanks
Turns out this is apparently a bug in Testflight. I tried to resolve the issue through their support forum and multiple emails with no real answer. I did not want to switch services as my testers knew the Testflight system well. But eventually switched to Diawi. My testers were able to install the app using Diawi with no problems.