ITMS-90158

Hello! I encountered an issue while packaging and uploading the project to the Mac store. I received an email stating: ITMS-90296: App Sandbox not enabled - The following executors must include the 'com. apple. security. app sandbox' entitlement with a Boolean value of true in the entitlement property list: [[com. electron. iflyrecclient. pkg/Payload/iFlytek Listen. app/Contents/MacOS/iFlytek Listen]] Refer to App Sandbox page at https://developer.apple.com/documentation/security/app_sandbox for more information on sandboxing your app. Though you are not required to fix the following issues, we wanted to make you aware of them: ITMS-90886: 'Cannot be used with TestFlight because the signature for the bundle at' iFlytek hears. app 'is missing an application identifier but has an application identifier in the provisioning profile for the bundle.' Bundles with application identifiers in the provisioning profile are expected to have the same identifier signed into the bundle in order to be eligi

every time i am trying to post my application to appstore I got this message: ITMS-90338: Non-public API usage - The app references non-public selectors in XXXX: setNavigationBar:. 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. For further information, visit the Technical Support Information at http://developer.apple.com/support/technical/ I search inside my code and my 3rd party libraries about setNavigationBar and navigationbar = but i didn't find any matched results. i tryed to exported the application build and i searched inside the exported build abdout setNavigationBar and found one result in but couldn't find any details about location or file that generated this. what to do?

After building the app for TextFlight, I uploaded it. After that, I initially received the following message via email. ITMS-90899: Macs with Apple silicon support issue - The app isn‘t compatible with the provided minimum macOS version of 11.0. It can run on macOS 12.0 or later. Please specify an LSMinimumSystemVersion value of 12.0 or later in a new build, or select a compatible version in App Store Connect. So I added LSMinimumSystemVersion to info.plist, increased the version, and uploaded it again. Next ITMS-90863: Macs with Apple silicon support issue - The app links with libraries that aren’t present in macOS: /usr/lib/swift/libswiftCloudKit.dylib @rpath/libswiftCloudKit.dylib I received an issue email like the above. The app has supported Mac (Designed by iPad) so far. This time, this issue occurs after building in Xcode 16.0 / MacBook OS 14.6.1. The app being built supports at least iOS 14. We cannot uncheck it because we must support Mac (Designed by iPad) in the future. This issue

Recently I started getting emails from AppStoreConnect when I submit new builds The email states: ITMS-90863: Macs with Apple silicon support issue - The app links with libraries that aren’t present in macOS: /usr/lib/swift/libswiftCloudKit.dylib I can run this app on apple silicon from TestFlight or directly from Xcode and it runs just fine including all iCloud functions. This app has been using iCloud for several years now. So my question is: Should I just ignore the email or do I need to change something to bring this app into compliance?

I am trying to upload my app to TestFlight, which using CoreNFCUnfortunately, I got the error message on Testflight Validate part in (SDK version 13 and 13.1).I already tried [this]: Xcode 11 beta can't upload app to TestFlightbut it will Lose NDEF function [this]: https://stackoverflow.com/a/58128365/5588637Error messages: Invalid entitlement for core nfc framework The sdk version 13.0 and min OS version 13.0 are not compatible for the entitlement 'com. Apple developer nfc. Readersession formats because NDEF is disallowedI already choose target iOS 13.1 in XCode, but also have this error.image 1: https://user-images.githubusercontent.com/19588517/65782718-dceb9180-e180-11e9-88d9-d21c2dcb5701.pngimage 2: https://user-images.githubusercontent.com/19588517/65782843-263be100-e181-11e9-8639-48fb64c5e08d.png

We just compiled and uploaded new release with Xcode 16.1 to the App Store. A few minutes later the following email arrived: The app references non-public selectors in {app_name}: setNavigationBar:. 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. But we don’t have any setNavigationBar methods in our project. Only setNavigationBarHidden calls for navigationController. And this is not private API of course. Please let us know how to upload our update for review. Thank you!

Hello developers ! My team and I are currently trying to migrate to the new Xcode 16 version. We encounter a blocker problem with the new Xcode when submitting a new build on TestFlight. The problem : ITMS-90338: Non-public API usage - The app references non-public selectors in AccorHotelsApp: setSupportedInterfaceOrientations:. We tried several things to solve the issue : remove all the frameworks that are not built by us ; the issue is still present remove the code related to this API in our base code and the frameworks ; the issue is fixed remove only the code related to this API in our base code ; the issue is fixed This indicates that the problem is the code related to this API. The code removed : override public var supportedInterfaceOrientations: UIInterfaceOrientationMask { get { configuration.orientation } set { _ = newValue } } This code is located in our local SPM. It's used to handle orientation of our app depending on specifics configuration given as a parameter. Why Xcode 16 is detectin

We have a CD pipeline set up for many apps (we're an app dev agency, we're uploading apps all the time). Uploads of our apps to AppStoreConnect using the iTMSTransporter command line tool started failing a few days ago. If we attempt to upload the same bundle using the Mac Transporter app, it uploads just fine. The problem only seems to be the iTMSTransporter command line tool. The version of the tool we're using is: iTMSTransporter, version 3.3.0 I've also tried running these commands pointing at the version of iTMSTransporter running at /Applications/Transporter.app/Contents/itms/bin/iTMSTransporter but this won't even start due to some Java security certificate issue. An example of the command we are calling is: /usr/local/itms/bin/iTMSTransporter -m upload -v eXtreme -f /path/to/Bundle.itmsp -jwt {generatedJwtHere} The bundle appears to actually upload to the AppStore OK, after lots of logs we get a message like: INFO: Reservation committed: (CPUSource221/v4/0b/e5/74/0be57409-0479-3c02-0

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 struggling to get past the following error from Transporter. I've tried everything I can think of and I'm not sure what else to do. WARNING ITMS-90885: Cannot be used with TestFlight because the executable “${executable}” in bundle “${bundle}” is missing a provisioning profile but has an application identifier in its signature. Nested executables are expected to have provisioning profiles with application identifiers matching the identifier in the signature in order to be eligible for TestFlight. Setup I'm using electron with a main.app and nested helper apps (e.g. Main.app/Contents/Frameworks/Main Helper (Renderer).app) I'm trying to upload to the Mac App Store I'm codesign-ing the contents with Apple Distribution: ... and signing the pkg installer with 3rd Party Mac Developer Installer: ... I'm using osx-sign to manage the code signing for me: basically it's doing a whole bunch of this: codesign --sign {40-char-hash} --force --timestamp --options runtime --entitlements $CHILD_PLIST packages/mas