“ITMS-90338”

I really need help. Can anyone decrypt the following message for me: Dear Developer, We identified one or more issues with a recent delivery for your app, MYAPP 2.0 (1200). Please correct the following issues, then upload again. ITMS-90288: Invalid Code Signing Entitlements - The entitlements in your app bundle signature do not match the ones that are contained in the provisioning profile. According to the provisioning profile, the bundle contains a key value that is not allowed: '' for the key 'com.apple.application-identifier' in 'MYAPP.app/Contents/Frameworks/libsqlite3s.dylib' ITMS-90286: Invalid Code Signing Entitlements - Your application bundle's signature contains code signing entitlements that are not supported on macOS. Specifically, value '' for key 'com.apple.application-identifier' in 'MYAPP.app/Contents/Frameworks/libsqlite3s.dylib' is not supported. This value should be a string starting with your TEAMID, followed by a dot '.', followed by the bundle identifier . The 2 dylibs

Hi, I have the same bug. I don't use any map or direction features . But binary reviewer each time says, that routing app setting is missed. I went up the .geosjón thinking it was necessary and then I deleted, but no difference, the error remains.

Hello, We submitted our app on TestFlight, but received an automated response with the following error: ITMS-90426: Invalid Swift Support - The SwiftSupport folder is missing. Rebuild your app using the current public (GM) version of Xcode and resubmit it. Our app is developed entirely in Objective-C, and we’re unsure why it’s looking for SwiftSupport. Despite attempting several potential solutions, the error persists. Could someone please assist us with understanding why this is happening and advise on how to proceed with the submission? Any guidance would be greatly appreciated. Thank you for your help.

Build the archive, validating and uploading it to App Store Connect - TestFlight is successful from Xcode (16.0, macOS 15.1.1). Although after that the build is rejected stating : ITMS-90429: Invalid Swift Support - The files libswiftCoreFoundation.dylib, libswiftCoreData.dylib, libswiftCore.dylib, libswiftFoundation.dylib, libswift_Concurrency.dylib, libswiftObjectiveC.dylib aren’t at the expected location /Payload/Runner.app/Frameworks. Move the file to the expected location, rebuild your app using the current public (GM) version of Xcode, and resubmit it. Cross checked the Archive and .ipa file, where we found that the mentioned .dylib files are actually present inside the /Payload/Runner.app/Frameworks folder, and all the .dylib files are also present in the SwiftSupport/iphoneos folder. Scenario : using tdLib compilation libtdjson.xcframework (embedded & signed) for ios arm64 placed under Framworks, in my Flutter application, calling methods via Method Channels, interacting with AppDelegate.

Hi, I was notified about quarantine files but I don't know why? ITMS-91109: Invalid package contents - The package contains one or more files with the com.apple.quarantine extended file attribute The mentioned file is to project logo as PNG image. The PNG file is located here: MyApp.app/Contents/Resources

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.