ITMS-90158

Hello everyone, I have an app on React Native and I am using Windows OS. I built this app and when I tried to submit (with EAS) I got email from Apple with the thext below: ITMS-90809: Deprecated API Usage - New apps that use UIWebView are no longer accepted. Instead, use WKWebView for improved security and reliability. Learn more (https://developer.apple.com/documentation/uikit/uiwebview). The app is old and I am working on updates. It had WebView from react-native-webview, I changed the component to WKWebView and react-native-wkwebview-reborn. And now I am getting this error: ❌ Undefined symbols for architecture arm64 ┌─ Symbol: _RCTJSNavigationScheme └─ Referenced from: -[CRAWKWebView webView:decidePolicyForNavigationAction:decisionHandler:] in libreact-native-wkwebview.a(CRAWKWebView.o) 1040 ❌ ld: symbol(s) not found for architecture arm64 ❌ clang: error: linker command failed with exit code 1 (use -v to see invocation) ▸ ** ARCHIVE FAILED ** ▸ The following build commands failed: ▸ Ld /Users/exp

Hi, I've tried multiple ways of solving this issue, including adding scripts, DISABLE Bitcode and non works. ERROR ITMS-90125: The binary is invalid. The encryption info in the LC_ENCRYPTION_INFO load command is either missing or invalid, or the binary is already encrypted. This binary does not seem to have been built with Apple's linker. I am currently building a games with Unity, and trying to publish to test flight but no success at the moment. Non of the online solutions works on my side. Appreciate for your inputs, thanks in advance!

when I submit my product recently, I meet the below issue from Apple, but such product before already submit successfully and my xxx-Info.plist and InfoPlist.strings are matched, but why happen The “NSContactsUsageDescription” value for the NSContactsUsageDescription key isn’t allowed in “xxx.app”? any rule changed recently? thanks for your help! App Store Connect Dear Developer, We identified one or more issues with a recent delivery for your app, 1.0.25 (84). Your delivery was successful, but you may wish to correct the following issues in your next delivery: ITMS-90738: Invalid purpose string value - The “NSContactsUsageDescription” value for the NSContactsUsageDescription key isn’t allowed in “xxx.app”. Your app’s code references one or more APIs that access sensitive user data, or the app has one or more entitlements that permit such access. The Info.plist file for the “xxx.app” bundle should contain a NSContactsUsageDescription key with a user-facing purpose string explaining clearly and comple

ERROR ITMS-90725: SDK version issue. This app was built with the iOS 15.2 SDK. All iOS and iPadOS apps submitted to the App Store must be built with the iOS 16.1 SDK or later, included in Xcode 14.1 or later. Submits my app to testFlight but I am facing this error. I updated but it didn't fix macOS: Big Sur 11.7.7 Xcode: 13.2.1

We are facing the below mentioned error frequently while submitting the different apps in the App Store. When we are uploading the first build, we are receiving the below mentioned error and if we increment the build version, and on re submitting we are not facing the same issue again. Could you please guide us on what caused this issue? Xcode Version: 14.2 Error : ITMS-90338: Non-public API usage - The app contains one or more corrupted binaries. Rebuild the app and resubmit.. 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.

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

I suddenly started to receive the following email with the error in it stating that my uploaded app is not available to be used in TestFlight: ITMS-90886: 'Cannot be used with TestFlight because the signature for the bundle at “MyApp.app/Contents/PlugIns/MyAppWidgetExtension.appex” 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 eligible for TestFlight.' It was all working fine and now I am not sure even where to start looking. Signing, provisioning and everything else is managed automatically.

After uploading a debug build to testflight getting an email stating ITMS-90755: Invalid Binary - The following binaries in your app contains prohibited instructions: AppName.app/App. Remove the instructions from the binaries, rebuild and resubmit.. To the best of our knowledge we haven't added any prohibited instructions of any kind, and the email also doesn't provide any information on what the offending instruction is. After much trial and error we found switching a property from an array to a non-array makes the error go away and testflight accepts the build, which obviously doesn't make any sense as to why that change produces this error. Is this some kind of false positive happening or what else is going wrong? Any help to resolving the issue is much appreciated.

I write this macOS app with Python PyQt and build a “.pkg” file, without using Xcode, and use Transporter app to verify. I successfully build the “.pkg” file which can pass Transporter app’s verification. When I do the code signing with my.app, I get the error message my.app: replacing existing signature my.app: bundle format unrecognized, invalid, or unsuitable In subcomponent: my.app/Contents/MacOS/lib/PyQt5/Qt5/qml/QtQml/Models.2 so I find the answer https://github.com/pyinstaller/pyinstaller/wiki/Recipe-OSX-Code-Signing-Qt to solve this problem. Below is my command: python Installer/mac/fix_app_qt_folder_names_for_codesign.py Installer/my.app pkgbuild --install-location /Applications --component my.app my.pkg productbuild --distribution dist.xml --package-path ./my.pkg ./my_final.pkg productsign --sign xxx my.pkg my_signed.pkg my.app directory tree my.app ├───Contents ├───_CodeSignature ├───embedded.provisionprofile ├───Frameworks ├───Info.plist ├───MacOS └───Resources ├───icon.icns └───lib └───PyQt5 └───

I've added NFC support for my app. So, my UIRequiredDeviceCapabilities were extended from armv7 to armv7 nfc. This means I've prevented this application from running on devices supported by previous versions. Now I've received a message from Apple: ITMS-90109: This bundle is invalid - The key UIRequiredDeviceCapabilities in the Info.plist may not contain values that would prevent this application from running on devices that were supported by previous versions. What is the right way to add new functions?

Hello, we are having this response when submitting our application, but in the return email from the Apple Store Connect it does not show what would be the point to correct. Is anyone else having this too? any idea what to do? Thanks in advance.. Dear Developer, We identified one or more issues with a recent delivery for your app, []. Please correct the following issues, then upload again. ITMS-90338: Non-public API usage - The app contains one or more corrupted binaries. Rebuild the app and resubmit.. 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/ Best regards, The App Store Team

Do any Apple tools exist that currently enable Bulk IAP management? I have been trying to use the iTMSTransporter, and the following command does respond appropriately, but the metadata.xml that is returned is incredibly bare, and does not include any of the 50+ IAPs we have in our app. ./Transporter.app/Contents/itms/bin/iTMSTransporter -m lookupMetadata -u *** -p *** -destination ~/Desktop/IAP -apple_id *** -app_platform ios -subitemtype InAppPurchase