ITMS-90158

I have an app that I'm building and signing and deploying for the Mac App Store. I received an email that there were problems with the deployment that make no sense to me. ITMS-90286: Invalid Code Signing Entitlements - Your application bundle's signature contains code signing entitlements that are not supported on macOS. Specifically, value '367****Y2.com.foo.foo-one.electron' for key 'com.apple.application-identifier' in 'Foo One.app/Contents/MacOS/Foo.app/Contents/Frameworks/Electron Framework.framework/Versions/A/Libraries/libEGL.dylib' is not supported. This value should be a string starting with your TEAMID, followed by a dot '.', followed by the bundle identifier . Say what now? This value should be a string starting with your TEAMID, followed by a dot '.', followed by the bundle identifier . But that is exactly what it is set to: 367****Y2.com.foo.foo-one.electron (asterisks just here to obscure our actual TeamID) I have no idea how to proceed. Any advice? Similar to this question thread 6984

When archiving and uploading a build of our tvOS app to App Store Connect with Xcode 13.3RC, it gets rejected with TMS-90562: Invalid Bundle - One or more dynamic libraries that are referenced by your app are not present in the dylib search path. When archiving and uploading with Xcode 13.2.1 the build is accepted and processed. I could not find any rpath issues when inspecting the binary with otool -L and otool -l. Has anyone else experienced the this issue with Xcode 13.3RC? I've filed feedback FB9952607

Our app uploads successfully, but then I get the following message in an email from App Store Connect about an Invalid Code Signing Entitlements: ITMS-90286: Invalid Code Signing Entitlements - Your application bundle's signature contains code signing entitlements that are not supported on macOS. Specifically, value 'BFZC26JH2W.humansarehuman.blue2factor.macosbackground' for key 'com.apple.application-identifier' in 'Blue2Factor.app/Contents/Library/LoginItems/Blue2FactorBackground.app/Contents/MacOS/Blue2FactorBackground' is not supported. This value should be a string starting with your TEAMID, followed by a dot '.', followed by the bundle identifier . The value for the key mentioned, BFZC26JH2W.humansarehuman.blue2factor.macosbackground, IS our TEAMID, followed by a dot, followed by the bundle identifier. The bundle is a target in our project, though it is not only target, and it is not the bundle ID that is identified as the BundleID on the App Store Connect - App Information page under the Gener

ITMS-90338: Non-public API usage - The app references non-public selectors in HouseMartApp.iOS: checkFocusGroupTreeForEnvironment:, commissioningComplete:, determineAppInstallationAttributionWithCompletionHandler:, errorForCHIPErrorCode:, errorToCHIPErrorCode:, lookupAdConversionDetails:, setButtonsView:, setDoubleTapGestureRecognizer:, setGrid:, setListenPort:, setLongPressRecognizer:, setTextLabel:, sharedController, sleep:, test:, toggle:. If method names in your source code match the private Apple APIs listed above, altering your method names will help prevent this app from being flagged in future submissions. In addition, note that one or more of the above APIs may be located in a static library that was included with your app. If so, they must be removed. we are not able to find issue.can you provide where is exactly isssue.

Dear Support, I'm unable to push a build to TestFlight. This is using Xamarin.Forms as the build creator. I'm getting the error I have pasted below. Please advise how to resolve. Thank you, Joshua Lowenthal Dear Developer, We identified one or more issues with a recent delivery for your app, WoundMatrix Patient 1.57 (13). Please correct the following issues, then upload again. ITMS-90338: Non-public API usage - The app references non-public selectors in WoundMatrixHC.iOS: accumulatorPrecisionOption, alignCorners, assetForIdentifier:, attackTime, batchStart, bytesPerImage, calibrationMode, checkFocusGroupTreeForEnvironment:, classesLossDescriptor, clipRect, colorTransform, columns, commissioningComplete:, computeStatistics, confidenceLossDescriptor, curveType, deactivate, determineAppInstallationAttributionWithCompletionHandler:, encodeToCommandBuffer:sourceTexture:destinationTexture:, envelope, first, forward, frontFacingWinding, gradientForWeights, initWithBuffer:offset:, initWithCoder:device:, init

I submitted an Mac Appstore App which has an embedded Java JRE. The first upload with ApplicationLoader went fine, but was automatically rejected due to a code signing error, which is now corrected. But I cannot upload the corrected build, getting ITMS-90511: CFBundleidemtifier Collision. The Info.plist CFBundleidentifier value 'com.oracle.java.8u45.jdk' of MyApp.app/Contents/Plugins/jdk1.8.0_45.jdk' is already in use by another application.Any suggestions are highly appreciated.Thanks, Manfred

Hi I have built an application and trying to publish it to App Store Connect to do a TestFlight. My application is called Meeting Reminder App with an SKU of DanD.meeting-reminder. For some reason, every time I try to distribute the app to the App Store Connect, an email gets sent to me with this error: We identified one or more issues with a recent delivery for your app, Meeting Reminder App 1.0 (21). Please correct the following issues, then upload again. ITMS-90683: Missing Purpose String in Info.plist - Your app‘s code references one or more APIs that access sensitive user data. The app‘s Info.plist file should contain a NSCalendarsUsageDescription key with a user-facing purpose string explaining clearly and completely why your app needs the data. If you're using external libraries or SDKs, they may reference APIs that require a purpose string. While your app might not use these APIs, a purpose string is still required. For details, visit: https://developer.apple.com/documentation/uikit/protectin

Hi, When we try to build our app on Xcode Cloud, after the app finishes archiving, we get the following error: ITMS-90486: Invalid WatchKit Support. The expected app is missing from the app’s root location, such as /Payload/[AppName].app/Watch. How can we fix this? We have an iOS target + a dependent watchOS target. Thank you!