Ive uploaded an update for my App two days ago, it should be 9.0 MG, but after submitting it it shows 1.11 MG, so I've called Apple Developer Support, they told me to do the following:
Reject the current build and upload a new one - Didn't work
Upload using Xcode 5.1 instead of Xcode 6 GM seed - Didn't work
Upload more than one build, and switch between them - Didn't work
So nothing worked with Apple, so they told that if I'm sure that I've uploaded the correct build to not worry, it might be a bug from the system.
Now ive uploaded an update for another app, and faced the same issue, the app size is 2.1 instead of 16.5, so I've decided to use TestFlight Beta Testing, its requires iOS 8, so I've updated my iPhone to iOS 8 beta, and once I've sent the link to the mobile, I've found that the app size is 2.1 !!, And every time i try to install the app, it says EXPIRED, so i didn't see the app working on the phone from the AppStore new build testing.
At the end, I've decided search on Google again for more results, "Ive tried to search about this issue 3-4 days ago but no results came", and found that some people got Invalid Binary after submitting the app "1-3 days", you can check these links: Link 1, Link 2.
Nothing from what i found gave an accurate answer to this case.
Anyone faced same issue?? what should i do??
My first app was approved by Apple and everything seems to be ok, the app size is now changed to the correct one "9.0" MB, and the app is working as expected on the device.
So its seems that the size issue is related to Apple, they have a bug on the itunesconnect.
So don't worry about the size issue anymore.
Related
Trying to upload a binary, which includes a watch app. The error I'm getting (which I wasn't getting a couple days ago) is the value provided for LC_VERSION_MIN_IPHONEOS for the watchkit extension is 8.2 which is greater than the maximum allowed value of 10.3... apparently 8.2 > 10.3?
I'm updated to the latest XCode, 8.3, that didn't fix the problem. Tried changing the iOS deployment target for the watch app and extension, no apparent effect on the message.
Update: it's fixed!
I have submitted a bug to Apple. They have replied that they are aware of the problem and have people looking into it. They will contact me when they have resolved the issue. I'll post an update here when they do.
This is not related to Xcode 8.3, the error is in the Apple validation process. I had an app in review (no problems in uploading it) that got rejected because the user provided for login had expired. I made no changes to the app, just activated the user and submitted. I have the error now.
Edit: I can also confirm that if Watch support is removed everything goes well.
EDIT: This is problem on Apple side and nothing to do with Xcode. This is only effecting apps with WatchKit.
I just uploaded one my apps today that has a watchkit extension. Try this, it may or may not help.
Xcode -> Product Clean
Xcode -> Quit
In a console terminal do > rm -rf /Users/your_mac_user/library/Developer/Xcode/DerivedData/*
Relaunch Xcode and project
Go to your Xcode -> Build Settings for your iPhone app and make sure its set to 8.0 for debug and release
Now go to both your watch and watch extensions and make sure the Build setting is set to 8.2
Archive and upload again.
EDIT: Although successfully uploaded to iTunes Connect, when trying to submit a Testflight beta build, still got rejected by the same message
Invalid sdk value. The value provided for the sdk portion of
LC_VERSION_MIN_IPHONEOS in XXX.app/PlugIns/XXX WatchKit
Extension.appex/XXX WatchKit App.app/XXX WatchKit App is 8.2
which is greater than the maximum allowed value of 10.3.
Guess Apple's still working on it...
I am having this issue earlier, also with a watchOS1 target in my project.
I've tried to upload the binary again few minutes ago, no more warning shows, and passed the processing of iTunes Connect.
Everybody having this issue should give it a try!
I was submitting with an old Xcode version, I thought that was the problem, so went to the latest and it gives me the same message, that I am submitting for 8.2 which is higher than 10.3.
Now, here is where it gets really crazy. I said, OK, maybe there is an issue with 8.2, so I switched my minimum target to 8.3, cleaned, archived, submitted. I STILL GET THE MESSAGE ABOUT 8.2!!!
I exported the package I am uploading:
otool -l MyApp.app/MyApp |fgrep --after-context=3 LC_VERSION_MIN_IPHONEOS
cmd LC_VERSION_MIN_IPHONEOS
cmdsize 16
version 8.3
sdk 10.2
--
cmd LC_VERSION_MIN_IPHONEOS
cmdsize 16
version 8.3
sdk 10.2
I grepped both the package and my project directory, there is no friggin' "8.2" string anywhere. The same app without the watch extension validates fine. It seems they have broken the watch submissions (at least WatchOS1), which is something they should have noticed, yet I emailed support 2 days ago with screenshots and they were unimpressed, telling me to send them a video if I want my ticket to be processed! Take 1 minute to look at the upload log, I gave you app ID and timestamp, how hard is that?
Edit: It seems I installed the previous version of xcode, there is one newer out, but it also doesn't fix the issue, the problem appears to be on the Apple side...
Edit 2: The binary that has not been going through since the day before yesterday, just got uploaded. Maybe it is fixed?
Edit 3: But then you get the message in itunes connect when you try to submit the app. So it seems they are working on it, not completely resolved yet.
Edit 4: SUCCESS! Successfully submitted, waiting for review!
Apple fixed this bug yesterday. You can use the same binary. There's no need to make any changes.
I deleted the watch-related targets, and uploaded successfully.
If you download a new version of Xcode, make sure to switch to it:
sudo xcode-select --switch /Applications/Xcode_11.6.app/Contents/Developer
sudo xcodebuild -runFirstLaunch
Ecuador's answer about using otool is a great tip to make sure the SDK is correct before you submit.
I too had the same issue. Removed the watch app and did the upload. It has been accepted for review. So looks like the issue is with the validation of the watchkit extension. Will submit the app again with the watch app once this issue has been taken care of by Apple.
I have an app which works perfectly on the simulators. This app also worked perfectly on an iPhone* for a couple of months. After a few weeks of this app not being opened, the app crashes when I attempt to open it. It looks like its about to open but it quits.
If I double tap the Home button to display my cached apps I can see it there amongst the other cached apps and it looks fine, displaying on-screen elements and images(which are saved and retrieved from the filesystem) correctly. If I tap it, it again quits before running.
I was hoping to release this app asap as it is finished. I've searched the net for solutions but have not found any. I don't know what particular information may be needed to figure out the problem but please ask and I'll respond with it. I am relatively new to ios development.
*iPhone 5s running latest ios9 update
The latest version of Xcode is 7.3. You need to update your Xcode to the latest version to be able to upload to the latest version of iOS.
EDIT: I forgot to mention this earlier. The latest version of Xcode requires El Capitan (OS X 10.11).
EDIT 2: OP has now revealed that a provisioning profile is being used. These only last about a month. After they expire, the app is no longer trusted and will show the described behavior. This can only be solved by re-signing the code, which requires either a new provisioning profile or a Developer ID. In any case, after the code is re-signed, it has to be reinstalled, and installing onto the latest iOS requires the latest Xcode.
Sources coming soon.
OK, so I seem to be having some trouble finding the site where I found this information in the first place...
However, from the App Store:
Xcode 7.3.1 includes [...] SDKs for iOS 9.3 [...].
I downloaded Xcode 7.1 from the App Store today after working from 7.1 beta downloads from developer.apple.com and have a new iOS app build to upload. So I did:
Product > Archive
Upload to App Store (or Validate)
But the response was:
You are not authorised to use this service
Intriguingly, when I 'Export' the build to the Desktop and then use Application Loader 3, it uploads without error.
Is this an iTunes Connect bug? Or is there a new Xcode checkbox I've missed?
Note: I've also tried removing and re-adding my AppleID as suggested here, and restarted my Mac for good measure (which actually allowed the validation to work once), but still no luck uploading directly from Xcode > Organiser.
I met the same issue today and I think it is a bug of Xcode 7.1
Finally I managed to submit my app via Application Loader. There were warnings but it did work.
Here are the basic steps:
Archive
Export
Xcode menu --> Xcode --> Open Developer Tool -->
Application Loader
Double click "Deliver Your App" and choose the
file exported in step #2
click next and follow the instructions until
the end
Here's the quick solution:
Don't use Xcode beta versions to submit apps for release — it's beta for a reason and shouldn't be used with production code.
Submitting Apps
Apps that are created using beta versions of Xcode or that are built
for beta versions of operating systems will not be accepted on the App
Store and Mac App Store. Apps that you submit should be developed
using the latest version of Xcode from the Mac App Store and should be
built for publicly available versions of iOS, OS X, and watchOS —
except when GM seeds are available. When a GM Seed of Xcode becomes
available, use it to develop your app for submission. When GM seeds of
iOS, OS X, or watchOS become available, build your app for these
versions.
↳ https://developer.apple.com/support/pre-release-software/
Having the same problems as all of you, just thought I'd share that I found a way to Validate successfully, you have to disable the "Include bitcode" checkbox before moving forward. As for the actual upload to App Store, no work around for that one other than use the Application Loader...
Also I've been seeing this too since XCode 6.4, but it seems once the current version has a couple of months after it's originally released it starts working again... fingers crossed that it starts working again soon, because uploading straight from Organizer is so much better. (I saw the Beta Version post, when I say after a couple of months for current version I'm not talking about Beta versions, just in case ;) )
Same problem here.
Downloaded Xcode 7.1 from the App Store and it refuses to upload a new version.
Happily Application Loader worked ;)
Hopefully this gets fixed quickly.
One possible reason for the issue could be multiple development accounts under one name (personal and company). I've read elsewhere (apple radar) that that caused earlier problems of this kind.
Happens here if the dev account is only admin. I had to use the central account for uploading our apps. I think this problem startet sometime with XCode 6. Didnt investigate further though since Application Loader works in cases when I dont have access to the central account.
I also have the same problem today.
Finally, I used the application loader to upload successfully,too.
Theres a few solutions I have come across to solve this issue.
Most common being to remove and re-add your developer account.
This won't work on its own though, you need to also 'view details' on your account and have Xcode download your provisioning profiles again.
The other alternative is to upload your build using application loader. The disadvantage to using this solution is that should you be trying to upload using a beta build of Xcode or OSX you won't be able to change your apps .plist in the archive folder to trick iTunes connect into accepting it. In this instance all you have access to is your ipa.
Disable the "Include bitcode" checkbox worked for me.
I am beta testing my app, and a few users are getting the error "Unable to Download Application. "Okasio" could not be downloaded at this time". So far 30 users have downloaded the beta of the app, and only 2 are getting the error, so it seems user- rather than app-specific. Does anyone have a suggestion?
The message is identical to the one from this post, but with current iOS 8 formatting:
TestFlight fails to install app and cannot delete partially installed app
The most likely reason is that their iOS OS version is below the app's minimum OS version.
As strange as it might sound the official Apple TestFlight/iTunes Connect beta system does not test the OS version at all at the moment. We faced this issue while we were working on our integration with the new TestFlight system (Bitrise.io, iOS CI/CD service - CTO here).
For example one of our test apps was built with iOS 8.2 as the minimum OS version. It's even listed on the app's card in TestFlight (Compatibility: Requires iOS 8.2 or later) but you can still click on the install button and it starts to download&install it. Then of course you get the helpful error message with Unable to Download App.
Note: Tested on two different iPads, both with iOS 8.1.3.
Another, less likely issue might be the lack of storage on the device but as far as I remember that presents a different error message.
I'm updating my existing app to include support for Apple Watch (at this stage just handling of notifications), however when I archive my app and try to submit it to the app store for review I continually get this error.
I've tried playing around with the build settings and I've also tried googling the error, however I can't figure out what the issue is.
Does anyone have any ideas or has anyone come across this issue too?
You cannot submit an app for review using a beta version of Xcode.
Following today's Apple Watch official release, Apple updated Xcode to version 6.2 which in theory should allow submitting apps that contain Watch extensions. However I just tried to submit my app that includes support for Watch using the new Xcode, and got the same error. I hope this will be fixed sometime soon on the ItunesConnect site.