Search results for

“ITMS-90338”

1,703 results found

Post

Replies

Boosts

Views

Activity

Xcode 15.0 beta 15A5160n upload IPA fail
I receive this mail after deliver my app for a while: ITMS-90338: Non-public API usage - The app links to non-public libraries in Runner: /System/Library/PrivateFrameworks/AVFCapture.framework/AVFCapture, /System/Library/PrivateFrameworks/AVFCore.framework/AVFCore...... I didn't use these API in my code. By the way I could upload my app successfully with Xcode 14 without this error.
2
0
882
Jun ’23
Getting 'Undefined symbol for architecture arm64' error after switching from react-native-webview to react-native-wkwebview-reborn on iOS
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/expo/Library/Develo
0
0
1.4k
Jun ’23
FastLane Step Error WKWebView
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
0
0
1.7k
Jun ’23
LC_ENCRYPTION_INFO (ITMS-90125)
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!
0
0
1k
Jun ’23
Info.Plist localized issue
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
1
0
2.6k
May ’23
ITMS-90338: Non-public API usage
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.
2
0
1.2k
May ’23
ITMS-90885 “${executable}” in bundle “${bundle}” is missing a provisioning profile
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
16
0
4.1k
May ’23
Reply to Crypting ITMS-90886 error abound bundles identifiers and provisioning profiles
I've received the same error as well. I'm using electron with nested helper applications (e.g. Main.app/Contents/Frameworks/Helper.app) The following causes the error for me codesign -s $DISTRIBUTION_KEY -f --entitlements $CHILD_PLIST packages/mas-universal/{APP_NAME}.app/Contents/Frameworks/{APP_NAME} Helper (Renderer).app productbuild --component packages/mas-universal/{APP_NAME}.app /Applications --sign $INSTALLER_KEY packages/{APP_NAME}.pkg -- This seems to fix the error, but causes a new error codesign --sign {40-char-hash-from-electron/osx-sign} --force --timestamp --options runtime --entitlements $CHILD_PLIST packages/mas-universal/{APP_NAME}.app/Contents/Frameworks/{APP_NAME} Helper (Renderer).app productbuild --component packages/mas-universal/{APP_NAME}.app /Applications --sign $INSTALLER_KEY packages/{APP_NAME}.pkg -- WARNING ITMS-90885: Cannot be used with TestFlight because the executable “${executable}” in bundle “${bundle}” is missing a provisioning profile but has an application ident
Topic: Code Signing SubTopic: General Tags:
May ’23
Crypting ITMS-90886 error abound bundles identifiers and provisioning profiles
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.
2
0
2.0k
May ’23
Reply to App Sandbox not enabled
I was welcomed with this issue today. Been publishing this app properly signed for years. It's even visible in the package review that the binaries have this flag enabled but the build is being blocked with this message: ITMS-90296: App sandbox not enabled The following executables must include the 'com.apple.security.app-sandbox' entitlement with a Boolean value of true in the entitlements property list: [[com.aone.keka.pkg/Payload/Keka.app/Contents/MacOS/keka7z ...
Topic: Code Signing SubTopic: General Tags:
May ’23
ITMS-90755: Invalid Binary
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.
1
0
642
May ’23
Reply to When does “Waiting for Review” show in App Connect
I discovered this for my tvOS version of my App (iOS version is okay): We identified one or more issues with a recent delivery for your app, Monster Paddle Pong 1.2 (8). The following are for your information only and do not require any action: ITMS-90471: Missing Image Asset - Your app is missing the Top Shelf Image Wide 2x asset in 'Payload/Monster Paddle tvOS Game.app'. The do not require any action statement confuses me because until I correct the Missing Image Asset error, my new Version = 1.2 will not be uploaded for Review. This error is new for me that did not appear 2 months ago when I started with version 1.0 Nevertheless, I did correct it by adding the 2x asset as requested and then Archived again. This time, however, I did not get a 2x asset error email, so I assume the App Connect Site was happy because the email I did get was: The following build has completed processing: Platform: tvOS App Name: Monster Paddle Pong Build Number: 9 Version Number: 1.2 App SKU: 5683766467 App Apple ID: 1
May ’23
Build the .pkg file without Xcode and verify it with the Transporter app. An Error ERROR ITMS-90260
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 └───
0
0
647
May ’23
The right way to extend UIRequiredDeviceCapabilities
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?
1
0
889
May ’23
Xcode 15.0 beta 15A5160n upload IPA fail
I receive this mail after deliver my app for a while: ITMS-90338: Non-public API usage - The app links to non-public libraries in Runner: /System/Library/PrivateFrameworks/AVFCapture.framework/AVFCapture, /System/Library/PrivateFrameworks/AVFCore.framework/AVFCore...... I didn't use these API in my code. By the way I could upload my app successfully with Xcode 14 without this error.
Replies
2
Boosts
0
Views
882
Activity
Jun ’23
Getting 'Undefined symbol for architecture arm64' error after switching from react-native-webview to react-native-wkwebview-reborn on iOS
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/expo/Library/Develo
Replies
0
Boosts
0
Views
1.4k
Activity
Jun ’23
FastLane Step Error WKWebView
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
Replies
0
Boosts
0
Views
1.7k
Activity
Jun ’23
LC_ENCRYPTION_INFO (ITMS-90125)
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!
Replies
0
Boosts
0
Views
1k
Activity
Jun ’23
Info.Plist localized issue
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
Replies
1
Boosts
0
Views
2.6k
Activity
May ’23
ERROR ITMS-90725: SDK version issue.
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
Replies
2
Boosts
0
Views
1.5k
Activity
May ’23
ITMS-90338: Non-public API usage
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.
Replies
2
Boosts
0
Views
1.2k
Activity
May ’23
ITMS-90885 “${executable}” in bundle “${bundle}” is missing a provisioning profile
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
Replies
16
Boosts
0
Views
4.1k
Activity
May ’23
Reply to Crypting ITMS-90886 error abound bundles identifiers and provisioning profiles
I've received the same error as well. I'm using electron with nested helper applications (e.g. Main.app/Contents/Frameworks/Helper.app) The following causes the error for me codesign -s $DISTRIBUTION_KEY -f --entitlements $CHILD_PLIST packages/mas-universal/{APP_NAME}.app/Contents/Frameworks/{APP_NAME} Helper (Renderer).app productbuild --component packages/mas-universal/{APP_NAME}.app /Applications --sign $INSTALLER_KEY packages/{APP_NAME}.pkg -- This seems to fix the error, but causes a new error codesign --sign {40-char-hash-from-electron/osx-sign} --force --timestamp --options runtime --entitlements $CHILD_PLIST packages/mas-universal/{APP_NAME}.app/Contents/Frameworks/{APP_NAME} Helper (Renderer).app productbuild --component packages/mas-universal/{APP_NAME}.app /Applications --sign $INSTALLER_KEY packages/{APP_NAME}.pkg -- WARNING ITMS-90885: Cannot be used with TestFlight because the executable “${executable}” in bundle “${bundle}” is missing a provisioning profile but has an application ident
Topic: Code Signing SubTopic: General Tags:
Replies
Boosts
Views
Activity
May ’23
Crypting ITMS-90886 error abound bundles identifiers and provisioning profiles
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.
Replies
2
Boosts
0
Views
2.0k
Activity
May ’23
Reply to App Sandbox not enabled
I was welcomed with this issue today. Been publishing this app properly signed for years. It's even visible in the package review that the binaries have this flag enabled but the build is being blocked with this message: ITMS-90296: App sandbox not enabled The following executables must include the 'com.apple.security.app-sandbox' entitlement with a Boolean value of true in the entitlements property list: [[com.aone.keka.pkg/Payload/Keka.app/Contents/MacOS/keka7z ...
Topic: Code Signing SubTopic: General Tags:
Replies
Boosts
Views
Activity
May ’23
ITMS-90755: Invalid Binary
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.
Replies
1
Boosts
0
Views
642
Activity
May ’23
Reply to When does “Waiting for Review” show in App Connect
I discovered this for my tvOS version of my App (iOS version is okay): We identified one or more issues with a recent delivery for your app, Monster Paddle Pong 1.2 (8). The following are for your information only and do not require any action: ITMS-90471: Missing Image Asset - Your app is missing the Top Shelf Image Wide 2x asset in 'Payload/Monster Paddle tvOS Game.app'. The do not require any action statement confuses me because until I correct the Missing Image Asset error, my new Version = 1.2 will not be uploaded for Review. This error is new for me that did not appear 2 months ago when I started with version 1.0 Nevertheless, I did correct it by adding the 2x asset as requested and then Archived again. This time, however, I did not get a 2x asset error email, so I assume the App Connect Site was happy because the email I did get was: The following build has completed processing: Platform: tvOS App Name: Monster Paddle Pong Build Number: 9 Version Number: 1.2 App SKU: 5683766467 App Apple ID: 1
Replies
Boosts
Views
Activity
May ’23
Build the .pkg file without Xcode and verify it with the Transporter app. An Error ERROR ITMS-90260
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 └───
Replies
0
Boosts
0
Views
647
Activity
May ’23
The right way to extend UIRequiredDeviceCapabilities
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?
Replies
1
Boosts
0
Views
889
Activity
May ’23