Search results for

ITMS-90158

1,685 results found

Post

Replies

Boosts

Views

Activity

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.
Topic: App Store Distribution & Marketing SubTopic: App Store Connect
1
0
71
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.
Topic: App Store Distribution & Marketing SubTopic: App Store Connect Tags:
2
0
231
Oct ’25
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.
Topic: Code Signing SubTopic: General Tags:
2
0
1.9k
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
Successfully uploaded iOS app builds don't appear in App Store Connect
Since 1st of September archives uploaded via Xcode 26 beta 7 or builds distributed via CD (fastlane deliver) don't appear in App Store Connect. No errors reported during/after upload process, no e-mails with errors received. Xcode reports successful upload (with a few warnings regarding dSYM) I'm not getting any e-mails with ITMS errors Builds don't appear at in App Store Connect in TestFlight section (not even in Processing or Failed states). For me it seems like App Store Connect outage but all statuses in https://www.apple.com/support/systemstatus/ are green.
Topic: App Store Distribution & Marketing SubTopic: TestFlight Tags:
9
0
591
Oct ’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.
Topic: App Store Distribution & Marketing SubTopic: App Store Connect Tags:
3
0
482
Oct ’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
Topic: App Store Distribution & Marketing SubTopic: TestFlight
8
0
394
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
Topic: Developer Tools & Services SubTopic: Xcode Tags:
Sep ’25
Invalid Swift Support Upon Submit to Testflight/AppStore
Hello, i know this topic is here since ever, also in other forums, however this topic i face for a month and cant get pass it, I tried all other suggestions which didnt bring me anywhere. so, project using cmake in order for Qt creator (so c++ base project with enabled swift), however once i run a cmake which generates *.xcodeproj for Xcode, i open it via xcode and can properly build and deploy to device. however when I try to archive and sent to Testflight/AppStore, I get: ITMS-90426: Invalid Swift Support and when I try to followup guides to create it manualy, copying libs from: $(TOOLCHAIN_DIR)/usr/lib/swift-5.0/$(PLATFORM_NAME) plese here note, that ALL guides indicate to use folder swift, however there are no *.dylib files... they are only in swift-5.0 folder then I receive an error type: ITMS-90429: Invalid Swift Support - The files libswiftMetal.dylib, libswiftHomeKit.dylib, libswiftsimd.dylib, libswiftCallKit.dylib, libswiftos.dylib, libswiftNetwork.dylib, libswiftMapKit.dylib, libsw
Topic: Developer Tools & Services SubTopic: Xcode Tags:
2
0
995
Oct ’24
iOS26 - ITMS-90717: Invalid large app icon
Trying to upload an iOS26 app archive with Xcode 26 beta 7 and getting ITMS-90717: Invalid large app icon, meaning my app is not eligible for TestFlight testing. My App contains an IconComposer .icon asset, so I'm not sure what it's complaining about. I'm not seeing anything in the release notes about this, and I'm not sure if I'm doing something wrong or not.
Topic: App Store Distribution & Marketing SubTopic: App Store Connect Tags:
6
0
310
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
Topic: App Store Distribution & Marketing SubTopic: App Store Connect Tags:
2
0
124
Sep ’25