Search results for

“ITMS-90338”

1,704 results found

Post

Replies

Boosts

Views

Activity

ITMS-90034: Missing or invalid signature
We are currently facing an issue when attempting to deploy or update the iOS application provided by Salesforce. When signing the .ipa file shared periodically by Salesforce using Company’s Apple certificates, and attempting to upload it via Apple’s native Transporter application, we receive the following error message: ITMS-90034: Missing or invalid signature – The bundle 'com.mysalesforce.mycommunity.[CODE]' at bundle path 'Payload/CommunitiesApp.app' is not signed using an Apple submission certificate. We have strictly followed the steps described in the Salesforce document https://quip.com/yBxiAS29ZlvI We have reviewed the Apple certificates. They are the same ones currently used for other active Company's applications — valid, unchanged, and not expired.
0
0
57
Oct ’25
ITMS-90338: Non-public API usage-_cJSON_Delete
Hi, I created a new app for customers, test on local was all ok, but when submit to App Store I received a notification mail: ITMS-90338: Non-public API usage - The app references non-public symbols in Caiseyu: _cJSON_Delete, _cJSON_GetArrayItem, _cJSON_GetArraySize, _cJSON_Parse. 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. I searched the internet whole day, can't find any information about the _cJSON_XX APIs are the Non-public API. Can you help me.
1
0
72
Oct ’25
Reply to Foundation Models Framework with specialized models
Ha. got an iOS version of the app together. Validated OK. Took a long time to upload but completed OK. Remember this includes the modified model in the app bundle. Got an email from App Store Connect. Please correct the following issues and upload a new binary to App Store Connect. ITMS-90558: Thinned app size is too large - The “/Payload/PK-LLM.app” app bundle in the universal variant is 4 GB, which exceeds the maximum allowable size. Looks like I'm going to upload the specialized model to HuggingFace. Also, the current macOS version give an error after compiling (but not always). Could not launch “PK-LLM” Runningboard has returned error 5. Please check the system logs for the underlying cause of the error. The logs are full of a lot of stuff I don't understand. Maybe uploading to HuggingFace is the way to go.
Topic: Machine Learning & AI SubTopic: Core ML Tags:
Oct ’25
Reply to Unable to upload an app with ExtensionFoundation
Thank you for your answer. I tried with both AsheKube.app.a-Shell.localWebServer and com.example.example-extension. The only difference I could see is that sometimes it would fail when uploading (I would get the error message inside Xcode) and other time it would fail after uploading: I would get a kind e-mail from AppStore Connect, stating: Hello, We noticed one or more issues with a recent delivery for the following app: a-Shell App Apple ID 1473805438 Version 1.17.0 Build 500 Please correct the following issues and upload a new binary to App Store Connect. ITMS-90349: Invalid Info.plist value - The value of the EXExtensionPointIdentifier key, AsheKube.app.a-Shell.localWebServer, in the Info.plist of “a-Shell.app/Extensions/localWebServer.appex” is invalid. Please refer to the App Extension Programming Guide at https://developer.apple.com/library/content/documentation/General/Conceptual/ExtensibilityPG/Action.html#/apple_ref/doc/uid/TP40014214-CH13-SW1. Apple Developer Relations Builds 496, 497 and
Topic: App & System Services SubTopic: General Tags:
Oct ’25
Unable to upload an iOS app with Extensions to the AppStore
Hi, I've tried adding Extensions (using ExtensionFoundation) to one of my iOS apps. They work using Xcode on my devices, but when I upload them to the AppStore, I get the following error: ITMS-90349: Invalid Info.plist value - The value of the EXExtensionPointIdentifier key, AsheKube.app.a-Shell.localWebServer, in the Info.plist of “a-Shell.app/Extensions/localWebServer.appex” is invalid. Please refer to the App Extension Programming Guide at https://developer.apple.com/library/content/documentation/General/Conceptual/ExtensibilityPG/Action.html#/apple_ref/doc/uid/TP40014214-CH13-SW1. I could not find relevant information on the web page pointed. I've tried different values for the EXExtensionPointIdentifier, but none of them work. This value was generated by Xcode, since I did set the user-defined build setting EX_ENABLE_EXTENSION_POINT_GENERATION = YES, as explained in the instructions. At this point, I have no idea how to fix this issue.
2
0
244
Oct ’25
ITMS-90035: Invalid Signature with Xcode Cloud
Hello, my builds keep failing in Xcode Cloud at the creation of the archive for tesflight. I am receiving an email mentioning ITMS-90035: Invalid Signature TMS-90035: Invalid Signature - Code failed to satisfy specified code requirement(s). The file at path “BASELog.app/BASELog” is not properly signed. Make sure you have signed your application with a distribution certificate, not an ad hoc certificate or a development certificate. Verify that the code signing settings in Xcode are correct at the target level (which override any values at the project level). Additionally, make sure the bundle you are uploading was built using a Release target in Xcode, not a Simulator target. If you are certain your code signing settings are correct, choose “Clean All” in Xcode, delete the “build” directory in the Finder, and rebuild your release target. For more information, please consult https://developer.apple.com/support/code-signing. The thing is the archives which are not intended for testflight not App Store
0
0
244
Oct ’25
Reply to Invalid Swift Support Upon Submit to Testflight/AppStore
I’m facing the following issue while submitting my Flutter iOS app to App Store Connect: ITMS-90429: Invalid Swift Support - The files libswiftDarwin.dylib, libswiftMetal.dylib, libswiftCoreAudio.dylib, libswiftsimd.dylib, libswiftQuartzCore.dylib, libswiftos.dylib, libswiftObjectiveC.dylib, libswiftDispatch.dylib, libswiftCoreGraphics.dylib, libswiftCoreFoundation.dylib, libswiftUIKit.dylib, libswiftCoreMedia.dylib, libswiftCore.dylib, libswiftFoundation.dylib, libswiftCoreImage.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. My project is a Flutter iOS application that uses a static C++ .a library, which I integrated via a custom .podspec file. However, the project does not contain any Swift code. Could you please help me understand why these Swift libraries are being included in the IPA build? Also, how should I properly configure the Podspec or Xcode proj
Sep ’25
ITMS-90429: Invalid Swift Support – Swift libraries not at expected location in iOS app submission
Hello Apple Developer Community, I’m facing an issue when submitting my iOS app to App Store Connect. ITMS-90429: Invalid Swift Support libswiftDarwin.dylib, libswiftMetal.dylib, libswiftCoreAudio.dylib, libswiftsimd.dylib, libswiftQuartzCore.dylib, libswiftos.dylib, libswiftObjectiveC.dylib, libswiftDispatch.dylib, libswiftCoreGraphics.dylib, libswiftCoreFoundation.dylib, libswiftUIKit.dylib, libswiftCoreMedia.dylib, libswiftCore.dylib, libswiftFoundation.dylib, libswiftCoreImage.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. My setup: Using Flutter for iOS development Flutter version: 3.32.8 Xcode version: Version 16.3 What I have tried so far: Cleaned build folder: flutter clean Upgraded Flutter and CocoaPods to the latest version. Rebuilt the project using latest Xcode GM version. Verified that Always Embed Swift Standard Libraries is set to YES in Xcod
8
0
404
Sep ’25
Reply to App Store Connect Error ITMS-90058: This bundle is invalid
It’s part of our own framework, not a third-party dependency. For some reason, the DTPlatformName key is missing from the framework’s Info.plist, which caused the ITMS-90058 error during validation. We resolved this by adding DTPlatformName = iphoneos to the framework’s Info.plist, and the build is now passing App Store checks. Right, you won't find this key in the source Info.plist file for any target in Xcode, because it's expected to be generated as part of the build. The value can vary, as a framework can be built for different platforms, so hardcoding this value into your Info.plist isn't the right long-term solution. To figure out the right solution, are you able to share a stripped down version of your framework project with us, either through a link here to somewhere else on the Internet, or if you need to keep it private, you can open a code-level support request to get me a private copy? The stripped down version here is that I only need to see something that builds, so you could delete mos
Sep ’25
App Store validation fails with ITMS-90338 (Non-public API usage) when using TwilioVoice 6.12.1+
Hi, When submitting my iOS app that integrates the TwilioVoice SDK (v6.12.1+), validation fails with the following error: Upload failed with errors: Validation failed The app references non-public selectors in Payload/careqb.app/careqb: _isKeyDown, _modifiedInput, _modifierFlags (ID: 34774fb-ba69-4131-904f-694aead106d7) Steps to reproduce: Integrate TwilioVoice using CocoaPods (v6.12.1). Archive the app in Xcode 16.x. Validate for App Store Connect. Question: Is this a known false positive in App Store validation, or is TwilioVoice exposing private APIs internally? What’s the recommended way to proceed until Twilio releases a fix? Thanks, Ashutosh
2
0
128
Sep ’25
iTMSTransporter 4.1: --assetDescription fails with “No value present”
Until recently, I was able to upload my app with iTMSTransporter version 4.1.0 with the following command: /usr/local/itms/bin/iTMSTransporter -m upload -jwt {x.y.z} -v eXtreme -assetFile /Users/abc/Downloads/build.ipa -assetDescription /Users/abc/Downloads/AppStoreInfo.plist Starting this week, with iTMSTransporter version 4.1.0, the command fails with the following error: [2025-09-03 11:38:02 GET] <main> ERROR: No value present Package Summary: 1 package(s) were not uploaded because they had problems: /Users/abc/Downloads/build.ipa - Error Messages: No value present The same command still works when using the iTMSTransporter bundled with the Transporter app (version 4.0), so the issue appears to be specific to 4.1. Any guidance or confirmation from others experiencing this would be much appreciated.
3
0
496
Sep ’25
ITMS-90034: Missing or invalid signature
We are currently facing an issue when attempting to deploy or update the iOS application provided by Salesforce. When signing the .ipa file shared periodically by Salesforce using Company’s Apple certificates, and attempting to upload it via Apple’s native Transporter application, we receive the following error message: ITMS-90034: Missing or invalid signature – The bundle 'com.mysalesforce.mycommunity.[CODE]' at bundle path 'Payload/CommunitiesApp.app' is not signed using an Apple submission certificate. We have strictly followed the steps described in the Salesforce document https://quip.com/yBxiAS29ZlvI We have reviewed the Apple certificates. They are the same ones currently used for other active Company's applications — valid, unchanged, and not expired.
Replies
0
Boosts
0
Views
57
Activity
Oct ’25
ITMS-90338: Non-public API usage-_cJSON_Delete
Hi, I created a new app for customers, test on local was all ok, but when submit to App Store I received a notification mail: ITMS-90338: Non-public API usage - The app references non-public symbols in Caiseyu: _cJSON_Delete, _cJSON_GetArrayItem, _cJSON_GetArraySize, _cJSON_Parse. 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. I searched the internet whole day, can't find any information about the _cJSON_XX APIs are the Non-public API. Can you help me.
Replies
1
Boosts
0
Views
72
Activity
Oct ’25
Reply to Foundation Models Framework with specialized models
Ha. got an iOS version of the app together. Validated OK. Took a long time to upload but completed OK. Remember this includes the modified model in the app bundle. Got an email from App Store Connect. Please correct the following issues and upload a new binary to App Store Connect. ITMS-90558: Thinned app size is too large - The “/Payload/PK-LLM.app” app bundle in the universal variant is 4 GB, which exceeds the maximum allowable size. Looks like I'm going to upload the specialized model to HuggingFace. Also, the current macOS version give an error after compiling (but not always). Could not launch “PK-LLM” Runningboard has returned error 5. Please check the system logs for the underlying cause of the error. The logs are full of a lot of stuff I don't understand. Maybe uploading to HuggingFace is the way to go.
Topic: Machine Learning & AI SubTopic: Core ML Tags:
Replies
Boosts
Views
Activity
Oct ’25
Reply to Unable to upload an app with ExtensionFoundation
Thank you for your answer. I tried with both AsheKube.app.a-Shell.localWebServer and com.example.example-extension. The only difference I could see is that sometimes it would fail when uploading (I would get the error message inside Xcode) and other time it would fail after uploading: I would get a kind e-mail from AppStore Connect, stating: Hello, We noticed one or more issues with a recent delivery for the following app: a-Shell App Apple ID 1473805438 Version 1.17.0 Build 500 Please correct the following issues and upload a new binary to App Store Connect. ITMS-90349: Invalid Info.plist value - The value of the EXExtensionPointIdentifier key, AsheKube.app.a-Shell.localWebServer, in the Info.plist of “a-Shell.app/Extensions/localWebServer.appex” is invalid. Please refer to the App Extension Programming Guide at https://developer.apple.com/library/content/documentation/General/Conceptual/ExtensibilityPG/Action.html#/apple_ref/doc/uid/TP40014214-CH13-SW1. Apple Developer Relations Builds 496, 497 and
Topic: App & System Services SubTopic: General Tags:
Replies
Boosts
Views
Activity
Oct ’25
Unable to upload an iOS app with Extensions to the AppStore
Hi, I've tried adding Extensions (using ExtensionFoundation) to one of my iOS apps. They work using Xcode on my devices, but when I upload them to the AppStore, I get the following error: ITMS-90349: Invalid Info.plist value - The value of the EXExtensionPointIdentifier key, AsheKube.app.a-Shell.localWebServer, in the Info.plist of “a-Shell.app/Extensions/localWebServer.appex” is invalid. Please refer to the App Extension Programming Guide at https://developer.apple.com/library/content/documentation/General/Conceptual/ExtensibilityPG/Action.html#/apple_ref/doc/uid/TP40014214-CH13-SW1. I could not find relevant information on the web page pointed. I've tried different values for the EXExtensionPointIdentifier, but none of them work. This value was generated by Xcode, since I did set the user-defined build setting EX_ENABLE_EXTENSION_POINT_GENERATION = YES, as explained in the instructions. At this point, I have no idea how to fix this issue.
Replies
2
Boosts
0
Views
244
Activity
Oct ’25
ITMS-90035: Invalid Signature with Xcode Cloud
Hello, my builds keep failing in Xcode Cloud at the creation of the archive for tesflight. I am receiving an email mentioning ITMS-90035: Invalid Signature TMS-90035: Invalid Signature - Code failed to satisfy specified code requirement(s). The file at path “BASELog.app/BASELog” is not properly signed. Make sure you have signed your application with a distribution certificate, not an ad hoc certificate or a development certificate. Verify that the code signing settings in Xcode are correct at the target level (which override any values at the project level). Additionally, make sure the bundle you are uploading was built using a Release target in Xcode, not a Simulator target. If you are certain your code signing settings are correct, choose “Clean All” in Xcode, delete the “build” directory in the Finder, and rebuild your release target. For more information, please consult https://developer.apple.com/support/code-signing. The thing is the archives which are not intended for testflight not App Store
Replies
0
Boosts
0
Views
244
Activity
Oct ’25
Reply to Apple-Hosted Background Assets question
I have previously upload an aar asset with Transporter. The error message after adding the DTPlatform based on the error message ITMS-90508: Invalid Info.plist value - The value for the key 'DTPlatformName' in bundle Spatial Cat Videos.app/Extensions/HostedCatVideos.appex is invalid.
Replies
Boosts
Views
Activity
Oct ’25
Reply to Successfully uploaded iOS app builds don't appear in App Store Connect
We are having this same issue as combinatorial with the Release version of Xcode 26. Uploading one of our apps will attempt to associate with another app. We get an email with the error ITMS-90055: This bundle is invalid and it lists the bundle id of a different app than the one we uploaded.
Replies
Boosts
Views
Activity
Sep ’25
Reply to Invalid Swift Support Upon Submit to Testflight/AppStore
I’m facing the following issue while submitting my Flutter iOS app to App Store Connect: ITMS-90429: Invalid Swift Support - The files libswiftDarwin.dylib, libswiftMetal.dylib, libswiftCoreAudio.dylib, libswiftsimd.dylib, libswiftQuartzCore.dylib, libswiftos.dylib, libswiftObjectiveC.dylib, libswiftDispatch.dylib, libswiftCoreGraphics.dylib, libswiftCoreFoundation.dylib, libswiftUIKit.dylib, libswiftCoreMedia.dylib, libswiftCore.dylib, libswiftFoundation.dylib, libswiftCoreImage.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. My project is a Flutter iOS application that uses a static C++ .a library, which I integrated via a custom .podspec file. However, the project does not contain any Swift code. Could you please help me understand why these Swift libraries are being included in the IPA build? Also, how should I properly configure the Podspec or Xcode proj
Replies
Boosts
Views
Activity
Sep ’25
ITMS-90429: Invalid Swift Support – Swift libraries not at expected location in iOS app submission
Hello Apple Developer Community, I’m facing an issue when submitting my iOS app to App Store Connect. ITMS-90429: Invalid Swift Support libswiftDarwin.dylib, libswiftMetal.dylib, libswiftCoreAudio.dylib, libswiftsimd.dylib, libswiftQuartzCore.dylib, libswiftos.dylib, libswiftObjectiveC.dylib, libswiftDispatch.dylib, libswiftCoreGraphics.dylib, libswiftCoreFoundation.dylib, libswiftUIKit.dylib, libswiftCoreMedia.dylib, libswiftCore.dylib, libswiftFoundation.dylib, libswiftCoreImage.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. My setup: Using Flutter for iOS development Flutter version: 3.32.8 Xcode version: Version 16.3 What I have tried so far: Cleaned build folder: flutter clean Upgraded Flutter and CocoaPods to the latest version. Rebuilt the project using latest Xcode GM version. Verified that Always Embed Swift Standard Libraries is set to YES in Xcod
Replies
8
Boosts
0
Views
404
Activity
Sep ’25
Reply to App Store Connect Error ITMS-90058: This bundle is invalid
It’s part of our own framework, not a third-party dependency. For some reason, the DTPlatformName key is missing from the framework’s Info.plist, which caused the ITMS-90058 error during validation. We resolved this by adding DTPlatformName = iphoneos to the framework’s Info.plist, and the build is now passing App Store checks. Right, you won't find this key in the source Info.plist file for any target in Xcode, because it's expected to be generated as part of the build. The value can vary, as a framework can be built for different platforms, so hardcoding this value into your Info.plist isn't the right long-term solution. To figure out the right solution, are you able to share a stripped down version of your framework project with us, either through a link here to somewhere else on the Internet, or if you need to keep it private, you can open a code-level support request to get me a private copy? The stripped down version here is that I only need to see something that builds, so you could delete mos
Replies
Boosts
Views
Activity
Sep ’25
Reply to Icon composer icon contains alpha channel upload error
I have just tried with Xcode 26 RC and still get the same error ITMS-90717: Invalid large app icon. I have tested with only SVG files, with only PNG, where one was w/o alpha, and with combination SVG and PNG. Nothing worked. I sent feedback with attached AppIcon.icon file.
Replies
Boosts
Views
Activity
Sep ’25
App Store validation fails with ITMS-90338 (Non-public API usage) when using TwilioVoice 6.12.1+
Hi, When submitting my iOS app that integrates the TwilioVoice SDK (v6.12.1+), validation fails with the following error: Upload failed with errors: Validation failed The app references non-public selectors in Payload/careqb.app/careqb: _isKeyDown, _modifiedInput, _modifierFlags (ID: 34774fb-ba69-4131-904f-694aead106d7) Steps to reproduce: Integrate TwilioVoice using CocoaPods (v6.12.1). Archive the app in Xcode 16.x. Validate for App Store Connect. Question: Is this a known false positive in App Store validation, or is TwilioVoice exposing private APIs internally? What’s the recommended way to proceed until Twilio releases a fix? Thanks, Ashutosh
Replies
2
Boosts
0
Views
128
Activity
Sep ’25
Reply to [REQUEST] for a tool/method/guidance how to create privacy manifest (PrivacyInfo.xcprivacy) when you don't have Xcode/mac
For guidance, see the following resources: App Privacy Configuration Adding a privacy manifest to your app or third-party SDK Be sure to read Handling ITMS-91061: Missing privacy manifest.
Replies
Boosts
Views
Activity
Sep ’25
iTMSTransporter 4.1: --assetDescription fails with “No value present”
Until recently, I was able to upload my app with iTMSTransporter version 4.1.0 with the following command: /usr/local/itms/bin/iTMSTransporter -m upload -jwt {x.y.z} -v eXtreme -assetFile /Users/abc/Downloads/build.ipa -assetDescription /Users/abc/Downloads/AppStoreInfo.plist Starting this week, with iTMSTransporter version 4.1.0, the command fails with the following error: [2025-09-03 11:38:02 GET] <main> ERROR: No value present Package Summary: 1 package(s) were not uploaded because they had problems: /Users/abc/Downloads/build.ipa - Error Messages: No value present The same command still works when using the iTMSTransporter bundled with the Transporter app (version 4.0), so the issue appears to be specific to 4.1. Any guidance or confirmation from others experiencing this would be much appreciated.
Replies
3
Boosts
0
Views
496
Activity
Sep ’25