ITMS-90158

With Xcode 8 beta 2, App Submission causes ERROR ITMS-90534.Full Message is:ERROR ITMS-90534: Invalid Toolchain. New apps and app updates must be built with the public (GM) versions of Xcode 6 or later, OS X, and iOS SDK or later. Don't submit apps built with beta software including beta OS X builds.PS. I don't use macOS beta.I think that this is a temporary issue on iTunesConnect side. Any idea?

Hi.is anyone else seeing problems uploading iOS apps to iTunes Connect from Sierra (Beta 1 or 2)? Whether i use Application Loader or fastlane/deliver, i always get ERROR ITMS-90167: No .app bundles found in the package. But if i copy the exact same .IPA over to a El Capitan machine, it uploads ok...—marc

xCode Error ITMS- 90086: Missing 64bit support / for my Unity App.But if Unity Scripting backend is IL2CPP it won't build, so I have been told to put it as Mono 2Xwhich builds but gives me the xCode Error when trying to submit to iTunes ConnectERROR ITMS-90086: Missing 64-bit support. iOS apps submitted to the App Store must include 64-bit support and be built with the iOS 8 SDK or later. We recommend using the default Standard Architectures build setting for Architectures in Xcode, to build a single binary with both 32-bit and 64-bit support.ERROR ITMS-90086: Missing 64-bit support. iOS apps submitted to the App Store must include 64-bit support and be built with the iOS 8 SDK or later. We recommend using the default Standard Architectures build setting for Architectures in Xcode, to build a single binary with both 32-bit and 64-bit support.

I try to upload my app to App Store and I get this error1. ERROR ITMS-900087: Unsupported Architecture. The executables for xxxxxx.app/Frameworks/Alamofire.framework contains unsupported architectures '[x86_64, i386]'2. ERROR ITMS-90209: Invalid Segment Alignment. The app binary at xxxxx.app/Frameworks/Alamofire.framework/Alamofire does not have proper segment alignment. Try rebuilding the app with the latest Xcode versionThank You.

Hello.When we try to upload app, we received an error message that our build has an invalid binary file. (ERROR ITMS-90205)We researched this issue many times and can’t fix this issue. Could you give a more detail description for this issue or any workaround please? Thanks.

Hi am trying to upload my app to the appStore and begin to test with testFlight, but i have this error: ERROR ITMS-90046: Invalid Code Signing Entitlements. Your application bundle's signature contains code signing entitlements that are not supported on tvOS. Specifically, value '*' for key 'com.apple.developer.associated-domains' in 'Payload/myapp.app/myapp' is not supported., It is a tvOS app and for this AppID already have an iOS app that use Associate domains to support universal links. is there a way to use the same appId from my ios app with associated domains enabled, in my tvOS app?

When I go to upload my app to iTunes (like I've done successfully before), it now gives me an ERROR ITMS-90023: Missing required icon file. The bundle does not contain an app icon for iPad of exactly '76x76' pixels, in .png format for iOS versions >= 7.0.However, the icon file IS there, and the reference to it in plist appears to be correct. What am I missing? What should I check, in what order? I'm not a native Mac user. I'm a windows developer, using Cordova to build mobile apps. I only use the Mac for Apple deployments.On a secondary rant... I can put out an Android AND website release in 5 minutes, but end up spending HOURS on the Apple deployments. Why can't Apple just scale the icon by default and allow overrides for specific resolutions? I'm sure we can find a college freshman to explain image scaling to them. This requiring dozens of icon files is ridiculous. I'm now on my 2nd DAY of trying to fix the Apple deploy. Somebody help!-- one very frustrated developer

I created a new version of (older ios8 application) the app in XCode beta 8 for io10. I am trying to submit it for internal testing through itunes-connect TESTFlight via XCOde. However, I keep getting the error as below. Can some one let me know how I can upload this to itunes-connect for internal testing?ERROR ITMS-90534: Invalid Toolchain. New apps and app updates must be built with the public (GM) versions of Xcode 6 or later, OS X, and iOS SDK or later. Don't submit apps built with beta software including beta OS X builds.Thanks,Swati

While uploading an archive using Xcode 7.3.1, and a codebase that has been built and pushed to TestFlight over 150 times. Most recently last week when a build was submitted to Apple review for Beta Testing. Does anyone have any idea what is causing this?

I get the folling error when trying to upload an app to TestFlight with an iMessage stickers extension with XCode 8.0 beta 3:ERROR ITMS-90644: Missing Image Asset. Your app is missing the Large App Icon asset 'iMessage App Icon' in 'Payload/App.app/PlugIns/StickerPackExtension.appex'.Is ITC accepting TestFlight builds at the moment, or is there something wrong with my extension? I've allocated images to every space in my iMessages App Icon in my .xcstickers bundle.I did notice though that the various settings images and the 1024x768 iMessages App Store image don't make it through to the built .appex file though.

I'm getting this error:ERROR ITMS-90034: Missing or invalid signature.

I'm using Xcode 8 Beta 3 to upload a Messages extension to iTunes Connect. During the upload I can see the app is being processed in the All Builds section of iTunes Connect's Activity tab. The moment Xcode finished uploading (Xcode shows an upload successful, thank you for uploading your app the App Store message), the listing of the app in iTunes Connect's Activity tab dissapears. The All Builds screen is empty.Attempting to upload the same build again using Xcode doesn't work either. Xcode shows an error message a version of the app with the same the version and build number already has been uploaded (which is correct): ERROR ITMS-4238: Redundant Binary Upload. There already exists a binary upload with build version '4' for train '0.2' at SoftwareAssets/PreReleaseSoftwareAssetHas anyone come across this issue?