Snapchat also uses 4 integers, currently being 9.31.1.0 - https://itunes.apple.com/en/app/snapchat/id447188370?mt=8However, when I use Application Loader to upload my binary, I get: ERROR ITMS-90060: This bundle is invalid. The value for key CFBundleShortVersionString '2.6.0.0' in the Info.plist file must be a period-separated list of at most three non-negative integers.This is the same question asked in: https://forums.developer.apple.com/message/45597But it's been 10 months without a response from Apple, and I need an answer now, so I'm posting again hoping get more visibility.Thanks
Search results for
ITMS-90158
1,681 results found
Selecting any option will automatically load the page
Post
Replies
Boosts
Views
Activity
In our IOS app, we have few libraries that do not spport BITCODE so we had ENABLE_BITCODE set to NO for the iOS APP and Yes for the Watch App.And, this setting has worked for us in the past but now we are getting error during submission. ERROR ITMS-90635: Invalid Mach-o formatThe Error descriptions mainly says that all targets for a platform should have a consistent value of ENABLE_BITCODE.Is bitcode now required for iOS Apps too if we have a Watch App?
HiWe have solved this conundrum in our case, we have an Apple Watch companion app. We tried re-building and uploading again. XCode uploader actually reported an error this time round during the upload:-ERROR ITMS-90635: Invalid Mach-O Format. The Mach-O in bundle SeaNav-GB.app/PlugIns/SeaNav_Core WatchKit Extension.appex isn’t consistent with the Mach-O in the main bundle. The main bundle Mach-O contains armv7(machine code) and arm64(machine code), while the nested bundle Mach-O contains armv7(bitcode) and arm64(bitcode). Verify that all of the targets for a platform have a consistent value for the ENABLE_BITCODE build setting.ERROR ITMS-90635: Invalid Mach-O Format. The Mach-O in bundle SeaNav-GB.app/PlugIns/SeaNav_Core WatchKit Extension.appex isn’t consistent with the Mach-O in the main bundle. The main bundle Mach-O contains armv7(machine code) and arm64(machine code), while the nested bundle Mach-O contains armv7(bitcode) and arm64(bitcode). Verify that all of the targets for a platform
Topic:
App Store Distribution & Marketing
SubTopic:
App Store Connect
Tags:
I thinked to make a wrong thing in my project ! Ouf ! I'm not alone !I have also the ERROR ITMS-90164: Invalid Code Signing Entitlements and somes WARNING ITMS-90080EDIT: May be an answer here : http://stackoverflow.com/questions/37613550/xcode-error-itms-90635-invalid-mach-o-in-bundle-submitting-to-app-store
Topic:
App Store Distribution & Marketing
SubTopic:
App Review
Tags:
Thanks Orel for linking to this: https://stackoverflow.com/questions/37613550/xcode-error-itms-90635-invalid-mach-o-in-bundle-submitting-to-app-store/37624641#37624641It seems that apple just started enforcing this yesterday. If your main binary has bitcode disabled, but you include a static library or framework that has bitcode enabled, it will fail validation. It goes the other way too: if your main binary has bitcode enabled, but you include a library/framework that has bitcode disabled, it will fail validation.I had a few dependencies from GoogleMaps and Amazon that made it non trivial to switch everything to enable bitcode, so I simply disabled it and removed bitcode from one static library I had imported in my project. You can strip bitcode from any binary by using this following command$ xcrun bitcode_strip -r {Framework}.dylib -o tmp.dylib$ mv tmp.dylib {Framework}.dylibhttps://developer.apple.com/library/watchos/releasenotes/DeveloperTools/RN-Xcode/Chapters/xc7_release_notes.htmlWhile the ab
Topic:
App Store Distribution & Marketing
SubTopic:
App Review
Tags:
For the past few days I've tried several times to upload an app and keep getting the below error. I am cusing 2 CocoaPods, which its is complaining about. Two weeks ago I uploaded a new app and never got errors like this.According to Apple's docs I think I have my settings correct.https://developer.apple.com/library/ios/qa/qa1788/_index.html#/apple_ref/doc/uid/DTS40013354Anyway, I'm curious if A) has anyone solved this or heard explaination from Apple and B) will Apple still approve my update with these warnings.Google foo shows others having the same issue.https://github.com/CocoaPods/CocoaPods/issues/5453http://stackoverflow.com/questions/37611069/warning-itms-90080-the-executable-payload-myapp-app-frameworks-some-frameworkThanks!
Uploading an app to iTunes Connect and keep getting this errorERROR ITMS-90347: Bad bundle identifier. The bundle identifier 'our.bundle.id' of the application extension App Name.app/PlugIns/Hidden Here.appex should start with the application's bundle identifier 'our.bundle.id' and not contain more than one period “.” after the application's bundle ID.ERROR ITMS-90347: Bad bundle identifier. The bundle identifier 'our.bundle.id' of the application extension App Name.app/PlugIns/Hidden Here.appex should start with the application's bundle identifier our.bundle.id' and not contain more than one period “.” after the application's bundle ID.Have looked at everything I can think of but still not getting anywhere.Anyone able to help?
I have an enterprise iPhone app distributed to more than 500 users and apps provisioning get expired now it stop working for all users now. App also contains itms-service for upgrade app but it too not working because app is not in foreground. Is there anyway to make working same app or update app for all users?Thanks in advance.
Topic:
Code Signing
SubTopic:
Certificates, Identifiers & Profiles
Tags:
Signing Certificates
Provisioning Profiles
I have also the ITMS-90208. Even bumping the minimum OS Version to 9.0 does not help.
Topic:
App Store Distribution & Marketing
SubTopic:
App Review
Tags:
When I attempt to upload the app to ITunes Connect from Xcode I receive the following error: Metadata/Info.plist Mismatch. The value for bundle_version in the metadata.xml file does not match the value for CFBundleVersion
I followed the App distribution Guide and went through all the necessary steps, 1. creating an archive record on Itunes Connect, then try to create an archive which passes Itunes connect validation tests, however when I click upload to App Store, it says Error Itms 90211, also my distribution provisioning profile says invalid even though I would have just recreated one via member centre and activated Distribution Code signing Identities on Xcode. Also the Distribution Provisioning profile I create manually via Member Centre says 0 devices, really stuck
When putting my IPA file into Application Loader, I get these two error messages. I was able to fix the icons the message was talking about, I just had to resize them, I did so by going into my zip file, was this the correct thing to do?Also, once I have resized them, do I completely need to redo my whole IPA file? And if so how do I do that? I've been using phonegap to develop an iPhone app.Thank you
after upgrading to macOS SierraI can no longer submit the built to testflight successfullyit just appears ERROR ITMS - 90167 No. app bundles found in the package error message....
ERROR ITMS-90211: Invalid Code Signing Entitlements. The signature for your app bundle contains entitlement values that are not supported. For the 'com.apple.developer.icloud-container-identifiers' entitlement, the values in the array must start with the prefix provided by Apple in the provisioning profile, followed by characters that are uppercase or lowercase Roman letters [A-Z, a-z], the digits 0 through 9, dot ['.'], or hyphen ['-'], and not contain any wildcard characters. Specifically, value 'iCloud.Prince_Dzonga.myEuro16' for the key 'com.apple.developer.icloud-container-identifiers' in 'Payload/myEuro16.app/myEuro16' is not supported.ERROR ITMS-90211: Invalid Code Signing Entitlements. The signature for your app bundle contains entitlement values that are not supported. For the 'com.apple.developer.icloud-container-identifiers' entitlement, the values in the array must start with the prefix provided by Apple in the provisioning profile, followed by characters that are uppercase or lo
Topic:
App Store Distribution & Marketing
SubTopic:
App Review
Tags:
More info and possible workaround here: http://stackoverflow.com/questions/37838487/error-itms-90167-no-app-bundles-found-in-the-package
Topic:
App & System Services
SubTopic:
Core OS
Tags: