ITMS-90158

The following error occurred when I uploaded the application for distribution in the test flight. After rebuilding, the problem resolved. What was the cause? I recently upgraded the Xcode version from 15.2 to 16.0, and this was my first build, so is it an environmental factor? ITMS-90433: Invalid Swift Support - The file libswifCore.dylib doesn’t have the correct code signature. Make sure you’re using the correct signature, rebuild your app using the current public (GM) version of Xcode, and resubmit it. Don’t just modify the code signature of libswiftCore.dylib.

When Submitting new App version for Review, the status changed to Invalid Binary and I got an email saying the following: We identified one or more issues with a recent submission for App Store review for your app, ****************. Please correct the following issues, then upload again. ITMS-90118: Invalid routing app setting: To upload a routing app coverage file on App Store Connect, you must define the app binary as a routing app.

I have made an app with Python and Kivy and am trying to get it going on TestFlight. The app also uses the Pyrebase module and its dependencies. I am Archiving it just fine with Xcode and moving through the steps just fine except when I try upload it. It fails and has about 38 very similar errors pop up saying: App Store Connect Operation Error ERROR ITMS-90171: Invalid Bundle Structure - The binary file 'weatherstrip.app/lib/python3.9/site-packages/Cryptodome/Hash/_MD2.abi3.so' is not permitted. Your app can’t contain standalone executables or libraries, other than a valid CFBundleExecutable of supported bundles. Refer to the Bundle Programming Guide at https://developer.apple.com/go/?id=bundle-structure for information on the iOS app bundle structure. But with different file names in each error. It seems that all of the listed errors are from the Cryptodome module from either the Hash or Cipher folders. All of the listed errors also happen to be .so files... I have tried to find answers all over bu

I published my app on the App Store and requested a review, but within a short period of time I received a response saying Bad Binary with the corresponding error code. ITMS-91056: Invalid privacy manifest - The PrivacyInfo.xcprivacy file from the following path is invalid: “Frameworks/Reachability.framework/ReachabilitySwift.bundle/PrivacyInfo.xcprivacy”. Keys and values in your app’s privacy manifests must be valid. For more details about privacy manifest files, visit: https://developer.apple.com/documentation/bundleresources/privacy_manifest_files. NSPrivacyTrackingDomains NSPrivacyTracking NSPrivacyAccessedAPITypes NSPrivacyAccessedAPIType NSPrivacyAccessedAPICategoryDiskSpace NSPrivacyAccessedAPITypeReasons E174.1 NSPrivacyAccessedAPIType NSPrivacyAccessedAPICategoryFileTimestamp NSPrivacyAccessedAPITypeReasons C617.1 3B52.1 DDA9.1 NSPrivacyAccessedAPIType NSPrivacyAccessedAPICategoryFileTimestamp NSPrivacyAccessedAPITypeReasons 3B52.1 NSPrivacyAccessedAPIType NSPrivacyAccess

Hi all, I received the following email from Apple: ITMS-91061: Missing privacy manifest - Your app includes “Frameworks/share_plus.framework/share_plus”, which includes share_plus, an SDK that was identified in the documentation as a privacy-impacting third-party SDK. Starting February 12, 2025, if a new app includes a privacy-impacting SDK, or an app update adds a new privacy-impacting SDK, the SDK must include a privacy manifest file. Please contact the provider of the SDK that includes this file to get an updated SDK version with a privacy manifest. For more details about this policy, including a list of SDKs that are required to include signatures and manifests I use Share Plus version 7.2.2 which does not have privacy manifest file yet but I am currently unable to upgrade it to a newer version since it would then bring a restriction that I should start using Dart version 3 where I am not there yet considering my other dependencies! So I am wondering what options I have... Will Apple accept my ap

After uploading a new App to the App Store Connect i receive an e-mail stating:ITMS-90034: Missing or invalid signature - The bundle '...' at bundle path 'Payload/...' is not signed using an Apple submission certificate.The App don't use any capability.I've used Xcode to upload, as in a previous App which now is on the App Store.All the apps use the default configuration: Automatically manage signing, Provisioning profile Xcode Managed Profile, Signing Certificate Apple Development: ############The requested Signing Certificate is present in the keychain in 3 versions, the last one is valid (the older 2 are revoked).What I should correct?

We were able to validate and upload a mac arcade build to ASC, but when submitting it for review we got this message from Apple: ITMS-90812: Arcade static library missing or not correctly linked. The app does not link against the library performing the Arcade subscription check. I've never seen this error message before. For context, we recently upgraded to Unity 2020 to support Apple silicon. The build launches and runs without any issues so not sure how to address the issue. FYI 'Mac Store App Validation' is checked in the build settings. Any help would be appreciated!

I applied for an app to the store the other day, and It has been Rejcted due to the following reasons. ITMS-90433 Invalid Swift support - File libswiftCore.dylib does not have the correct code signature. Make sure you're using the correct signature, rebuild your app using the current public (GM) version of Xcode, and resubmit. Don't just change the code signature of libswiftCore.dylib. ーーー For the application side, Xcode 15.4 was used. but, only libswiftCore.dylib was build with Xcode 16. However, this is not a beta version. When implementing a build,clean all has been carried out. Is the cause due to an Xcode version mismatch? I want someone to tell me the reason.

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