“ITMS-90158”

Hello, At my company, we're trying to run an App Store A/B test on alternate app icons. However, the App Store is rejecting the binary when we upload it (see email below). We're hoping someone out there knows the solution to this issue. Background Currently, our app is built with one target from amongst several different schemes. These schemes are used for various versions, including developer debug builds, TestFlight builds, App Store builds, and others. Each scheme has its own distinct app icon specified in Xcode, as shown in the image below: In our project, we've added the alternate app icons for the two App Store treatments as recommended according to Apple's documentation (we named them AppIcon-T1 and AppIcon-T2). These are located inside our Images.xcassets asset catalog. Each alternate app icon's properties are configured as: iOS: Single Size macOS: None watchOS: None Appearances: None Gamut: Any The Problem After making the changes above, creating an App Store build succeeds as usual. However, every t

ITMS-90338: Non-public API usage - The app references non-public selectors in WcBc.iOS: behaviorTypes, convolutionState, discoverAllContactUserInfosWithCompletionHandler:, discoverAllContactsCompletionBlock, discoverUserInfoWithEmailAddress:completionHandler:, discoverUserInfoWithUserRecordID:completionHandler:, discoverUserInfosCompletionBlock, displayContact, drawableResizesAsynchronously, encodeToCommandBuffer:sourceImage:convolutionState:, encodeToCommandBuffer:sourceImage:destinationImage:state:, getProperty:onChannel:responseHandler:, hasProperty:onChannel:responseHandler:, initWithEmailAddresses:userRecordIDs:, initWithMIDIEntity:dataReadyHandler:, initWithZoneID:options:, initWithZoneID:subscriptionID:options:, isPublicDatabase, mouseUpAction, newDrawable, propertyChangedCallback, removeAllAppearanceStreams, replaceTextStorage:, retrieveConnectedPeripherals, retrievePeripherals:, setDiscoverAllContactsCompletionBlock:, setDiscoverUserInfosCompletionBlock:, setDrawableResizesAsynchronously:, s

We have an existing iOS/tvOS app on the App Store available to customers as a Universal Purchase (same bundleId). Via Mac Catalyst we are looking to port the iOS app to MacOS and submit/release with the same bundleId. However, uploading to the store via Apple Transporter gives the following error: ERROR ITMS-90283: Invalid Provisioning Profile. The provisioning profile included in the bundle com.XYZ.ABC [com.XYZ.pkg/Payload/MyApp.app/Contents/Resources/ABC.bundle] is invalid. [Invalid 'com.apple.application-identifier' entitlement value.] For more information, visit the macOS Developer Portal. The app is built with Xcode 12.3 and contains a Mac bundle (ABC) embedded inside My.app

App Store Connect returns the following message when the NSExtensionPointIdentifier key in the Info.plist of a Device Activity Monitor extension contains an invalid value: ITMS-90349: Invalid Info.plist value - The value of the NSExtensionPointIdentifier key, , in the Info.plist of .../PlugIns/...appex is invalid. To resolve this issue, set NSExtensionPointIdentifier to com.apple.deviceactivity.monitor-extension. The expected Info.plist structure for a Device Activity Monitor extension is: NSExtension NSExtensionPointIdentifier com.apple.deviceactivity.monitor-extension NSExtensionPrincipalClass $(PRODUCT_MODULE_NAME).DeviceActivityMonitorExtension After you apply this fix, build and archive your app, then re-upload to App Store Connect to confirm the error is resolved.

App Store Connect rejects the build with the following error: Please correct the following issues and upload a new binary to App Store Connect. ITMS-90058: This bundle is invalid - The value for key CFBundleVersion [iphoneos] in the Info.plist file must be a period-separated list of at most three non-negative integers. Please find more information about CFBundleVersion at https://developer.apple.com/documentation/bundleresources/information_property_list/cfbundleversion But we double-checked at the app level; in all places the CFBundleVersion and versions is mentioned in the correct format. Even though we tried to upload via Xcode and Transporter, both show success. but the build is not reflecting in TestFlight. Receive the above error message via mail. data: { attributes: { cfBundleShortVersionString: 3.25.9, cfBundleVersion: 25, p Validated with the delivery log, but the delivery log also shows correct versioning only.

We are received the following error while uploading the application into TestFlight. **ITMS-90714: Invalid binary - The app contains one or more corrupted binaries. Please rebuild the app and resubmit. ** After sometimes we submit the same application without changing the configurations application submitted successfully into the App Store. We are using the Xcode 15.3 version.

SInce upgrading to Xcode 7.3, I can no longer submit IAP content using Application Loader. I was able to upload content before upgrading to Xcode 7.3. Now I need to update my IAP content and I'm getting this error in Application Loader:ERROR ITMS-10001: Multiple items in this package use the same vendor ID. Use unique vendor IDs for the items [software_assets] and resubmit the package.Is anyone else seeing this error?UPDATE:I downgraded to Xcode 7.2.1 and am still seeing this error. It appears that the problem is on the iTunes Connect side.

I'm having a whole host of issues come back from iTunes Connect when trying to upload an iOS 9 app with watchOS 2 app and both Watch and CocoaTouch frameworks embedded. I've waited a week before posting this in case it was an issue with the iTunes Connect server.For the iOS 9 app, I received ITMS-90086: Missing 64-bit support. Architectures is set to $(ARCHS_STANDARD) (armv7, arm64) and Build Active Architecture Only set to NO for Release.For the Watch Framework, I receive ITMS-90087: Unsupported archtectures...[armv7k]. Architectures is set to $(ARCHS_STANDARD) (armv7k) and Build Active Architecture Only set to NO for Release.Also for the Watch Framework, I receive ITMS-90362: Invalid Info.plist value. The value of the key 'MinimumOSVersion' is invalid. The minimum value is 8.0. This key was not set in Info.plist at all. I manually added this key with the value 9.0, rebuilt, and resubmitted, with no change in error message.I also receive ITMS-90125: The binary is invalid.

Hi We're trying to publish an app build to Testflight. We've successfully done the build, but when we archive the build, we get this error: error itms-90168 null. We are able to upload the build, it then SEEMS like the build is successfully archived. Then we validate the app, which is successful, but then when we click distribute, it gives an error: error itms-90168 null We've been struggling with this for quite a while and have tried things to solve the issue, but we haven't been successful this far. It's difficult to try figure out what is wrong, as the error message merely says Null instead of giving specific details.

I'm trying to send an app to AppStoreConnect using XCode Version 12.4 (12D4e), but I get an ITMS-90725 error and can't upload. I'm building with iOS13 SDK or above, the Development target is 13.2, and I deleted XCode and put it back in, but it didn't work. Is there anyone who can't upload in the same way? I want to know how to upload. Thank you.