Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about programming within the scope defined in the help center.
Closed 8 years ago.
Improve this question
I am trying to submit a new version of my existing app in itunes connect but I am having difficulties. So I uploaded my build like usual and upload done. I went into pre-release and saw the status processing. This was 12 hours ago, now though it has changed from processing to inactive. I ignored that and went and chose the build anyways and clicked on "Submit for Review"
I get an error saying You must submit your builds using Xcode 5.1.1 or later, or Application Loader 2.9.1 or later. After you’ve submitted a build, select it in the Builds section below.
But I did submit a build using Xcode 6 seed version. I also tried to upload the build again but I get an error saying that a buid already exists. I figured I will try to delete the build, from the pre-release tab and try to upload a new build but I cant find a way to do this.
Makes me think it has something to do with the inactive status of the build. Is anybody else having this issue?
Okay So I was able to submit my app for review. I guess you cannot wait for too long after you submit your build. I have no proof of this but I think if your build is inactive, you cannot use that build to submit an app. Here is what I did to solve my issue
In xcode I changed the build version, not the app version,
Archive and validate
Submit
While the build was still "Processing", I went back to my apps new version page on iTunes Connect
Choose the new build and submit for review.
Dont let the build become inactive.
Good luck
I was having the same issue. I followed the guy above's advice. Here's exactly what I did to get it to work:
In iTunes Connect, remove the current build.
In Xcode, change the build (not version) number to something else. I just picked "3".
In Xcode, go to Product -> Archive
Note: If this is greyed out, ensure that you select "iOS Device" instead of a different simulator or connected hardware for testing
In the Organizer - Archives window, click Validate, then click Distribute
In the Organizer - Archives window, delete your previously submitted archive
Go back to iTunes Connect, refresh, and select the new build with the updated version number
Related
How to remove the current build from iTunes Connect where the app is in "Developer Removed from Sale" status? Also, the older version should be made "Ready for Sale". Please help me. I have unknowingly Released the version of that app.
I cannot remove the current build from iTunes Connect now. The build doesn't show up any delete button.
You have to submit a new version with a new build. It's both not possible to a) either update the build of a live version (which was on the store) nor b) to switch to an older version.
Your flow will look like this:
1) Create new version in iTunes Connect
2) Create & upload new build with fixes for this version
3) Submit to the store. If it's a critical bug fix, you might want to request an expedited app review. https://developer.apple.com/support/app-review/
Expedited App Review:
If you face extenuating circumstances, you can request the review of your app to be expedited. These circumstances include fixing a critical bug in your app on the App Store or releasing your app to coincide with an event you are directly associated with.
Urgent Bug Fix:
If you've submitted an update to fix a critical bug in your app on the App Store and you are requesting an expedited review, be sure to include the steps to reproduce the bug on the current version of your app.
Although I can upload successfully new versions of my app to iTunes Connect, I can't see them nor the previous ones under the "Prerelease" section in the app's page. Instead, I get a message saying "Upload your builds with Xcode 5.1.1 or later, or with Application Loader 3.0 or later". In the "Versions" tab, under "Builds", when I press the "+" button, I get an error saying my request couldn't be processed. Am I missing some needed configuration?
It looks like this is an issue with iTunes Connect, not something you did. There are a bunch of tweets right now of others experiencing the same issue.
What you'll see right now if you look at the itunesconnect hastag on Twitter:
Our list of pre releases in #itunesconnect disappeared for no
reason... /cc #APPLEOFFIClAL 0 retweets 0 favorites 38m ago
Weird…all of my app builds have disappeared from iTunes Connect
itunesconnect 1h ago
itunesconnect: (slow / misbehavin') for everyone or just me (dot tumblr dot com) 2hours ago
itunesconnect - no earlier uploaded binaries are seen in any application. Seems like a bug. Fix it Apple, I have to deliver to customers.
Unfortunately, the official system status says everything is green. It's not clear how you're supposed to report an issue.
Indeed it was an apple bug. After two hours, the prerelease builds appeared again.
Downloading beta app from testflight app gives error at the end, says "Unable to download app at this time" on all my devices.
No error is in itune connect upload. App displayed and received notification on adding new app to testflight beta. But everytime same error.
This happened to me when I wasn't using the correct provisioning profile. Very frustrating error that doesn't provide any useful info, and leaves the previous installed version of your test build in a state where it cannot be launched. After I switched my provisioning profile to 'Automatic', bumped the build number, and submitted a new version to iTunes connect I was able to download the new build.
I'm seeing a similar error. I don't know for sure, but I suspect doing things in this order may have something to do with it (this seems to mirror what emrys57 is facing).
You have issued a previous TestFlight release (download/install was working).
You then submitted that version for formal review for publication in the App Store.
While the app submission is still under review, now you uploaded a new TestFlight build with an updated version number (but did not resubmit for App Store review).
It could be that while the app is under review something prevents the download. I seem to recall reading about something like this in one of the guides, but I can't remember where off the top of my head. In my case, as an internal tester I even face the error "Unable to download app at this time", regardless of whether I already have a previous version with the same bundle ID already installed or if I don't have the app already installed (i.e., it's fully uninstalled). I wonder if an accepted App Store review will clear up the issue; it doesn't seem like a good idea to resubmit that latest build for further App Store review if the version previously submitted is what you actually want released.
In my case, for the general testing audience, I have a separate bundle ID that is exclusively for beta testing. And that version is never submitted for App Store review (the one that's slated for App Store review I only use for the purpose of smoketesting the upgrade process with internal testers). That bundle ID for beta had to go through the one-time full TestFlight external review for the initial TestFlight external beta testing. But I've been able to keep adding new versions to that beta-only bundle ID for subsequent TestFlight releases without an issue.
Last week I posted a question here where I explained why my Xcode is crashing when I press the refresh button. This question however got closed for being off topic but I dont really get why. (Stackoverflow should provide more information on this subject)
But I still got this problem and I cant get my app running with push notification because I think I'm using old provisioning profiles and I CANT refresh them without Xcode crashing!
I've created multiple apps with push notifications so I know the procedure but keep getting the error:
did Fail To Register For Remote Notifications With Error: Error Domain=NSCocoaErrorDomain Code=3000 "no valid 'aps-environment' entitlement string found for application" UserInfo=0x2340a0 {NSLocalizedDescription=no valid 'aps-environment' entitlement string found for application}
Does anybody know why my Xcode is crashing and how I can fix this?
Thanks.
And please post a comment if you're thinking of closing this question so I know why this question is closed.
Ravi is right. Here's Apple's official workaround:
Run /Applications/Utilities/Terminal.app and execute the following statement:
mkdir ~/Library/Developer/Xcode/OldPortalDBs; mv ~/Library/Developer/Xcode/connect1.apple.com* ~/Library/Developer/Xcode/OldPortalDBs
See: Xcode 4.6.1 crashing while interacting with the developer portal
It works for me if I removed this file "~/Library/Developer/Xcode/connect1.apple.com 4.6.1.db" before running XCode 4.6.1.
After some restarts and project cleans (and manually download!) it suddenly worked with push notifications. Xcode still crashes on refreshing and bug is reported.
I'm trying to submit an application to Apple but am coming up with an error in Application Launcher.
Once I choose the zip file I hit Send and it comes up with the error:
Exception while validating: launch path not accessible
No idea what to do here, can't find much info on it at all on the net.
I have tried reapplying my provisioning / distribution profiles with no luck. Have re-opened XCode many times in case it was confused.
I submitted the same app a week and a bit ago and it went through fine, it got rejected so I made a few small changes and now this error comes up - no big changes were made.
The only thing I can think of is that I needed to update XCode and the SDK - from xcode_3.2.4_and_ios_sdk_4.1 to xcode_3.2.5_and_ios_sdk_4.2_final as the iPad I am using was updated to 4.2.
Any ideas on where to go from here would be greatly appreciated.
i had same problem, closed App Loader, restarted App Loader, problem solved.