I'm trying to upload a new version of my app to the apple store, but itunes connect looks to be bugged.
I already uploaded the binary 3 times with success, and so far, it didn't show up on the "Build" section. I'm using Xcode 6.2 and Application Loader 3.0. So I met all requirements.
The "+" button does not show on the build section also.
Looking for solutions I found some complaints even from 2014 but no perfect solution that will work for everyone.
Have you any ideal about what can I do?
My last binary upload was about 8 hours ago and nothing happened yet.
Status is as "Prepare for Submission".
I got it. I found all my uploaded binaries in another App.
This happened because I was using a wildcard provisioning profile. This caused the file not to be shown on the right app.
I had the some problem, and waited for more than 8 hours without any result. Then I saw a new (tax-agreement) contract that I had not signed. I signed it, waited for a few more minutes, and then the plus-sign showed up!
Related
I cannot select the latest version I have uploaded to seed to beta in external testing. First of all whenever I upload a build two version appearing, that have upload time difference of 5 to 15 minutes between them. One of them gets changed from processing to normal available state, but other does not. But now selecting the available build also selects the processing one and my selection is blocked and I cannot select the OK button because probably my selection is blocked by the processing one. I think it is UI frontend issue at itunesconnect side but it could be something I am doing wrong. Please help me if anyone has been able to tackle this issue if they faced. Please see checkout the attached image.
Update:
I Included <key>ITSAppUsesNonExemptEncryption</key><false/> in my subsequent builds that I uploaded according to the new Export compliance message on the iTunes Connect home page. I am still facing the issue. I have contacted Apple Dev support, will keep you updated if I find a solution.
The issue has been mysteriously solved by uploading the application from Application Loader with Aspera turned off instead of using Xcode's organizer window as suggested by Apple Developer support. Make sure you add: <key>ITSAppUsesNonExemptEncryption</key><false/> in your info.plist file before archiving the build. Although mysteriously my previously uploaded builds have also become available for external testing.
Body of email that helped solve the issue:
After further research, it looks like their may be an issue from your
end with your network while trying to upload to this app record in
iTunes Connect.
First, for the best upload experience make sure that all ports and IP
addresses are accessible. Additionally, it’s important to make sure
the internet connection is very good, and that there are no firewalls
blocking the uploads. More information can be found here:
http://help.apple.com/itc/apploader/#/itc8e7ec5a60
Second, it may be beneficial to try using the latest version of
Application Loader. Please note that you can export your project from
Xcode to upload through Application Loader. As a temporary workaround,
once you have Application Loader open, you can go to the File menus
and select the following:
Application Loader > Preferences
Then, select Advanced, and as a temporary workaround you can try
deselecting Aspera and upload the build again. You can follow the
steps below to use the latest version of Application Loader.
Download the latest version of Xcode from the Mac App Store:
-http://help.apple.com/itc/apploader/#/itc8e7ec5a60
Open the latest version of Xcode
Go to the File menu and select Xcode > Open Developer Tool > Application Loader
Lastly, try uploading again to see if the issue persists.
Hello my dear friend there,
I am also having your issue yesterday, I have this similar screen with yours:
The build is duplicated which one of them are processing forever until today.
My personal problem solving was:
Increase my build number in Xcode so that I can reupload my build
Rearchive the build then export for iOS App Store Deployment in Xcode Organizer
Reupload the build using Application Loader
Then try to reconfigure the build in iTunes Connect. For a while it is processing like usual, but it will not take forever, after one hour, the build will be available for testing.
Hope my personal troubleshooting can be applied to your issue too.
After I send my app for approval to the app store I get the message 'Invalid Binary' in the iTunes Connect. Then I get the following message in an email from Apple:
Invalid Swift Support - The bundle contains an invalid implementation of Swift. The app may have been built or signed with non-compliant or pre-release tools. Visit developer.apple.com for more information.
My app is just a simple game application. No external programs are called. I have researched this message and went through and checked the following:
xcode is up to date - checked in app store
EMBEDDED_CONTENT_CONTAINS_SWIFT to YES or NO
send with the xcode app, not the application loader
did NOT build with the command line
(Xcode menu -> Preferences -> Locations tab - verified that the Command Line Tools matches Xcode version.
"Clean"ed the app, rebuilt and rearchived and then resent, same message
The app validates through the organizer fine
viewing the contents of the archive shows a SwiftSupport folder
I am only using one developer account and have never logged into any other developer account
I cannot find anything online that would help solve this problem.
I am running OS X Yosemite 10.10.1.
xcode version is 6.1.1 version 6A2008a - built, cleaned and sent with this version
I have also pressed the Option key and "Cleaned Build Folder" and resent, same message
I cannot find any other reason for this online or in any forums. Any help is greatly appreciated. Thank you for your time.
SOLUTION I FIND
Edit:
(1)
One you contact Apple and you wait long time … for reset iTunes connect because this problem coming in Apple . (Apple ask to send log of this problem)
(2)
An other solution, your create an other project application on iTunes connect and upload your work, this solution work fine, is the solution for me .
(3)
An other solution, you create a new project on Xcode, copy and paste your project in this other project.... (create new provisioning profile etc..) And upload your work in the same project application on Itunes Connect.
(4)
Step (2) + step (3), create a new project in Xcode and Itunes Connect.
(5)
Create a new project with the same name bundle identifier, it works perfectly !
See: Technical Q&A QA1881 Embedding Content with Swift in Objective-C.
It seems that you only need to set EMBEDDED_CONTENT_CONTAINS_SWIFT to YES "If you are building an app that does not use Swift but embeds content such as a framework that does".
What language is your app written in? If Swift yo do not need EMBEDDED_CONTENT_CONTAINS_SWIFT.
I ran into this problem the other day. Took some doing, but I finally figured out the problem ( for me at least). Everything I read online said the problem had to do with this setting:
EMBEDDED_CONTENT_CONTAINS_SWIFT
When this started failing, I had this set to NO. So I tried setting it to YES, and it still failed for the same reason. The GUI wouldn't let me remove this setting, I could only change it between YES and NO.
For what it's worth, my code has no EMBEDDED code, it's all just straight up SWIFT.
Anyway, so I decided to uninstall XCode and redownload it, hoping that would help.
While XCode was downloading, I fired up Beyond Compare, and compared my current project, with a backup from last week, to see what could have changed.
Beyond Compare found that a file deep inside the Projectname.xcodeproj file, changed ... a file called project.pbxproj file.
Inside this, was that line:
EMBEDDED_CONTENT_CONTAINS_SWIFT = NO;
This appeared in the current version of my project (that was failing). Interestingly enough, this line didn't exist at ALL in the old backup version from a week ago. I know that I didn't set this flag. There must have been something in Xcode that did it under the covers.
Anyway with that knowledge, Xcode finished downloading, and I reinstalled. Started it up, opened my project, and magically, Xcode REMOVED that line from the .pbxproj file, and now my project uploaded to itunesConnect sucessfully.
BottomLine: There's a bug in xcode that it may decide to add this line to your project for no reason, making your project invalid.
Solution: Editing the pbxproj file yourself and removing that line might work ... but reinstalling XCode seemed to clear up any confusion it had, and it removed it for me.
If you are submitting an app that has an AppleWatch extension, you can get this error if you try and submit the app using the Application Loader utility and a zip file. I got the error:
The bundle contains an invalid implementation of Swift. and
The bundle contains an invalid implementation of WatchKit.
I went through pretty much every solution for the first of the errors - but it was submitting via Xcode that fixed it.
well xcode 6.1 is a bit old and contains old swift. xcode 6.4 is the newest public one IIRC
"Check your code signing. I had this error when in automatic signing. I Put my dev profile for dev and production profile for release version and error is gone."
Link for the Quote
Sometimes this happens inadvertently.
To be safe, all components of your app should be built with the same version of Xcode and the Swift compiler to ensure that they work together.
I think you need to do a pod clean and install. I reckon one of your swift pods was created on a old version of Xcode, you updated Xcode and then tried to do a submission to the app store.
Read the apple swift blog about binary compatibility and frameworks
You will also want to specify that your embedded content contains swift in the build settings:
EMBEDDED_CONTENT_CONTAINS_SWIFT
Enable this setting to indicate that content embedded in a target's product contains Swift code, so that the standard Swift libraries can be included in the product.
My temporary developer license (using Visual Studio 2011 Beta and Windows 8 Consumer Preview) expired and a popup asked me to aply for a new one. This all seemed to work, but when I build and deploy to the local machine it takes me to the app store and tells me that the developer license has expired.
I've tried:
Unistalling my app from the home screen
Cleaning my project solution
Removing my developer license using powershell command Unregister-WindowsDeveloperLicense and getting new license again
Restarting machine
I can create new projects that build and deploy fine, but my existing project is stuffed. Is the old licence cached somewhere and how can I get it to forget about it.
There is this similar quesion on MSDN. Someone managed to solve it, but there solution has not worked for me and there are other people saying it hasn't worked for them.
The first month this happened to me, a reboot solved it. The second time it didn't. I went into my package manifest and changed the package ID. It looked like a GUID and I just put kmg on the end. Then everything worked fine. Later I tried changing it back but it failed again so I guess my package ID ends in kmg now :-)
I believe it's because you're trying to overwrite a package that was shipped by a "different developer". They're going to have to fix that somehow but hey, this is what betas ^H^H^H^H^H previews are for, right?
I upgraded my OSX from Snow Leopard to Lion and I downloaded Xcode 4.3.1
Now when I try to validate and publish my app I get the first screenshot.
If I click on Download Identifier button I get the second screenshot.
Any suggest?
I had this same exact error after upgrading my Xcode from 4.2.x? to 4.3.1 via the app store. I did not upgrade my OS or any hardware, and my certificates were only about 2 months old. I has submitted an app update just days before this starting happening and I feel 100% sure that something in the Xcode upgrade caused it to happen.
After a few days fiddling with it by rejecting my developer certificates and updating all the apps and provisions profiles, as well as distribution profiles. I noticed something.. See screen shot.
The certificate that I was signing the app with was in the group "Identities with out Provisioning Profiles" I went back into the developer provisioning portal and downloaded the distribution certificate for my app, and added to my system, then updated the code signing identity with the correct certificate and I was able to get past this issue.
In short this message may suggest, you signed the archive with the wrong certificate. check it and make sure its the one for your app for distribution and it should work.
Happy Programing!
The certificates you created for signing your application are only valid on the machine (+ OS) which you used to create them. They can be migrated to another machine but if you already updated without doing so, I recon that this is not an option anymore. I also don't know what the "Import Developer Profile" button does (I guess it's fairly new) but you could try that out.
If this doesn't do the trick, don't worry. Just log on your ADC account, revoke the old certificates, create new ones and modify your project accordingly. (Just like you did, when you first created them.)
I come to know how to resolve this problem, It is quite simple, you just need to add an additional distribution provision profile in ios developer center.
Log into ios developer center.
Enter ios Provision portal.
Select provision on left column.
Select the Distribution tab on top in details column.
I can't post the screenshot bcd because my reputation is not enough.
In my case it was missing distribution provisioning profile.
I had this problem when we tried to upload an app too. We solved it in a way that I still don't understand completely, but I had an App ID that included some kind of ID in front of it like this: XXXXXXXXXX.com.plexical.start.bask. I put that string in my *-Info.plistfile. After having the problem above, I switched from automatic Code Signing Identity to manual and selected the same Distribution as the automatic one. Then I got a readable error from XCode complaining that the App ID didn't match com.plexical.start.bask:
I proceeded to change the App ID to com.plexical.start.bask in the *-Info.plist file and after that I was able to submit the App. I still don't understand completely why, but it worked for me.
What happened to me was that my Distribution Provision Profile had expired. All I had to do was delete it and create/download a new Distribution Provision Profile. Xcode automatically installed it and went to the next screen.
The validation process does not work with Ad-hoc profiles. Need to create a Distribution provisioning profile. It is not specified in the instructions for beta testing. I agonized all day until realized.
Maybe your distribution provisioning profile is out-of-date. Just open your provisioning profiles here and select one from the list, and click on Edit button from the options. After that download the provisioning profile.
Ok this took some fiddling and I finally got it to work.
The issue was that I created an archive and then renamed my project. This is a big no no apparently (which makes sense) which I didn't realize at the time.
I noticed that the bundle identifier in the archive was different from the one that was in the general settings.
If this combination happens to you, simply delete the archive you created and create a new one. This will at least be your first step at cleaning up the issue.
These steps solved it for me (some of them are in the answers above):
Update to Xcode 5.0.1 (current version); otherwise Xcode crashed when pressing "Cancel"
Update of my "Distribution iOS Provisioning Profile" in the Developer Center because mine were outdated.
Xcode > Preferences > Accounts > Apple IDs > > View Details:
The list below in the popup was outdated
==> Select iOS Distribution and press "+" (I don't remember what Magic happened then, however the list was actual after that)
As in the answer above:
In Xcode go to the Build Setting and search for "code signing" and:
Change the "Code Signing Identity" for "Distribution" and "Release" to "iPhone Distribution"
Change the "Provisioning Profile" for "Distribution" and "Release" to (I could not find it before doing step 4)
I was very glad that I didn't have to revoke everything in the Developer Portal.
My announcement to Apple: Please, make this process much more easier and bugfree! It's such a hassle that costs me hours every time you force me to update to a new MacOS, Xcode, iTunes, iOS in order to keep my software running!
I've found various proposed solutions to this problem on this internet, but none of them work for me. Does anyone know why this might be happening?
http://answers.unity3d.com/questions/15294/xcode-build-and-archive-error-no-such-file-or-directory
http://blog.joshschumacher.com/2011/04/06/xcode4-the-operation-couldn%E2%80%99t-be-completed-no-such-file-or-directory/
I've tried archiving with every combination of coding signing vs not using code signing, and I've tried using every combination of provisioning profiles, but I still get the same error every time.
I'm very confused as to why I'd even be getting an error like this when trying to save a file. I'm using XCode 4, my application builds for archive fine. In fact, I can even upload my application to itunesconnect (and it was accepted!). I just can't create an IPA for sharing and beta testing before submission.
Any ideas?
The error message
Right before I get the error
After much frustration, I filed a developer support request with Apple. The technician I spoke with was able to save my archive as an .ipa on her computer -- the exact same archive that I was not able to save on mine, which pointed to a possible bug in my system (and from the sounds of it, many other people's).
She recommended that I uninstall and reinstall XCode and the developer tools, and that worked!
Here were her uninstall instructions:
Make sure that your machine is running the latest Mac OS X (10.6.7) and iTunes.
Run the following command in the Terminal application to uninstall your SKD:
sudo <Xcode>/Library/uninstall-devtools --mode=all (where <Xcode> is the path to the directory that contains your SDK.)
Drag your <Xcode> to the trash and restart your machine
Re-download and install Xcode (4.0.2) from the iOS Dev Center. Make sure that the System Tools, UNIX Development, Essentials packages in the Custom Install pane are selected before installing it.
I have the same issue after my distribution certificate was expired. I add new ones (private key and certificate) and xCode "Share" command starts to produce such error.
The problem resolves as soon as I remove old private key & certificate from Keychain Access.
Hope it helps
Selecting "Don't Re-sign" at Identity solved the same issue for me.
I actually had the same problem, but a different solution (and reason). I had Xcode 3 and Xcode 4 both running at one point. I recently deleted Xcode 3 and moved my Xcode 4 from /Xcode4 to /Developer directory. This caused me to have the same issue you describe.
I moved the directory back to /Xcode4 and now my archives save out correctly.
I also had the same problem but I could resolve the problem in the below way.
My project was on the portable disk (formatted as FAT-32) and the project referred some folders on the same disk as "add folder reference for any added folder". I could build it any configurations however I couldn't just make .ipa file with above alert.
So, I copied the referenced folders on the portable disk to the desktop of the disk installed XCode (MacOS). And adding again the folders into the project. I could make .ipa file.
I installed Xcode 4.0.2 in one directory and then manually moved it to another.
When I moved Xcode back to the first directory everything worked.