ITMS-90158

After installation of XCode 8 and project migration to Swift 2.3 I started to seeing this message on archive uploading to TestFlight:ERROR ITMS-90046: Invalid Code Signing Entitlements. Your application bundle's signature contains code signing entitlements that are not supported on iOS. Specifically, value 'AAA00AAAAA.myAppId' for key 'application-identifier' in 'Payload/myApp.app/myApp' is not supported. This value should be a string starting with your TEAMID, followed by a dot '.', followed by the bundle identifier.Can anyone help me, please?

Our application uses UIApplication openUrl with the itms-services scheme to apply runtime updates.Since updating to iOS 10, the UIApplication openURL method is returning returning NO even though the update does install.This is causing a problem because we use the NO result to trigger reporting that the install has failed.We are using the canOpenUrl method first, before attempting openUrl.Is there a security change causing this, or any changes I need to make to my applications Info.plist?This is our code; NSURL * url = [NSURL URLWithString:[@itms-services://?action=download-manifest&url= stringByAppendingString:urlString]]; if (![[UIApplication sharedApplication] canOpenURL:url]) { LOG_(ERROR, @canOpenURL returned NO); return NO; } if (![[UIApplication sharedApplication] openURL:url]) { LOG_(ERROR, @openURL returned NO); return NO; }

Getting tis error but buit was not appear on iTunes Connect Please help me

We got an error, when we tried to upload new build to itunesconnect via Xcode 8 (from App Store and from http://developer.apple.com/download/more/ — the same behavior). We use Swift 2.3 in our project and some pods.ERROR ITMS-90596: Invalid Bundle. The asset catalog at 'Payload/***.app/Assets.car' can't be read. Try rebuilding the app with a non-beta version of Xcode and submit it again.Any ideas? 😕

Hi,After tens of successfull uploads to Itunes via Xcode (archive project) without any change to the plist file,After updateding Xcode to the latest version i got this error: ERROR ITMS-90046: Invalid Code Signing Entitlements. Your application bundle's signature contains code signing entitlements that are not supported on iOS. Specifically, value '7LW8YAVP6V.gates' for key 'application-identifier' in 'Payload/OmGate.app/OmGate' is not supported. This value should be a string starting with your TEAMID, followed by a dot '.', followed by the bundle identifier. Reset the MAC, clear the project, upload via Application Loader got the same error.Please advice.

iOS allows apps to communicate with bluetooth devices even when apps are backgrounded using bluetooth-central in UIBackgroundModes (Info.plist).We've ported our iOS app to tvOS and it works very well. Even when backgrounded, our tvOS app still talks to our bluetooth devices. Awesome!However, when submitting our tvOS app to iTunes Connect, the upload will fail with error messageERROR ITMS-90112: Invalid Info.plist value. The Info.plist key UIBackgroundModes contains an invalid value: 'bluetooth-central'. For more information, refer to the Information Property List Key Reference.Technically tvOS already supports bluetooth background mode, it works like a charm. So there's no obvious reason to reject apps with that background mode. Will Apple eventually allow apps with that background mode to be submitted?Thanks,Lars

have an emoji keyboard app selling on the app store and im trying to replace it with the new IOS 10 iMessaging app and keep getting this error. anyone seen this issue? see picture in link belowThankshttp://i.stack.imgur.com/mTBAW.jpg

After updating a few devices to iOS 10 to test our distribution, we found that we can't install any of our internal applications OTA.All of our devices are managed. Some are supervised and some are unsupervised. We support from iOS 6 (4th gen iPods) to iOS 10.The restriction that seems to be cause the problem is for restricting access to the Apple App Store. Previously this meant that the App Store would not show up and you couldn't install apps from the Apple App Store, but could still install our internal applications through either our web portal or an MDM solution. In iOS 10, that restriction is stopping installation OTA through our web portal. Removing the restriction allows OTA installation to work but then the devices have access to the Apple App Store, which is very undesirable for us.Our OTA installation works using the itms-services:// protocol pointed to a manifest plist. With the restriction in place, it seems to reject this protocol. All previous versions of iOS worked fine. Changing bet

I've got my Mac app through packaging, archiving, and export, in to the Application Loader. I've ended up using Application Loader because Xcode is only giving me unhelpful iTunes Store operation failed / try again messages. However I'm running in to a roadblock, which manifests as this error message:ERROR ITMS-90135: The executable could not be re-signed for submission to the App Store. The app may have been built or signed with non-compliant or pre-release tools.This is spewed out again and again in the Application Loader log - across every submission attempt I've tried, that message appears 73 times per attempt.My Mac app has a whole bunch of auxiliary executables in its Resources folder, which are invoked with NSTask to do work. There are far more than 73 executables so I don't know if that number is significant or not.There really is no other accompanying information that I can see - this single log line is all it's giving me. So there seems no way to start debugging which of the executables are

My ios project contains the dynamic framework written by swift,but i upload the ipa into apple store with xcode or applocation loader,the error message is always just ERROR ITMS-90680:The binary you uploaded was invalid,i have no idea,i upload the ipa many times.Can someone help me?