Search results for

ITMS-90158

1,681 results found

Post

Replies

Boosts

Views

Activity

ITMS-90334: Invalid Code Signature Identifier
I get the following error in Xcode Cloud when attempting to prepare a build for App Store: ITMS-90334: Invalid Code Signature Identifier. The identifier SwiftCharts-555549449cfa473253483215b74c174849d2ec9c in your code signature for SwiftCharts must match its Bundle Identifier SwiftCharts. This is an iOS app and Swift Charts is swift package dependency which the app depends on. Since it is a dynamic library, it is included via the Embed & Sign option. This was reported on SO by another user. They worked around it by making changes to the source package, I believe. That workaround may be difficult in my case as I do not control the source package. It's a 3rd party dependency that I'd prefer not to maintain a fork of. Any ideas of why Xcode cloud is hitting this issue or any other workarounds? I've confirmed via a codesign check that the Identifier is resolving to that special hash when doing this from Xcode Cloud. It does not have that hash when I attempt to build/archive/upload locally. $ codesig
2
0
1.2k
Oct ’22
ERROR ITMS-90725 can't upload app with transporter
Hello everyone, I have been developing a game in UE4 and I would like to send my build to TestFlight. I'm working on a windows machine and remote build my project on a updated Mac book pro with Monterey and Xcode 13.1 I have no problem generating the development build and the shipping build on the windows side. However when I try to upload the .ipa using transporter I get this error message that suggest that the SDK used to compile is not the right one. ERROR ITMS-90725: SDK Version Issue. This app was built with the iOS 13.2 SDK. All iOS apps submitted to the App Store must be built with the iOS 14 SDK or later, included in Xcode 12 or later. I should add that, in the past, I have been able to upload the game on iTunes connect. Any help would be greatly appreciate Best
1
0
730
Nov ’21
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
64
Oct ’25
Cannot upload in-app purchase content ITMS-4267 Error
I have been using Applicatioin Loader to upload iOS in-app purchase content without incident for several days. Now I am getting the following error:ERROR ITMS-4267: Invalid Platform. This app already supports iOS. Apps cannot support both iOS and macOS at Software/SoftwareMetadata/SoftwareInAppPurchase/SoftwareAssets/ContentHostedIAPAssetDoes anyone know what's going on? As far as I can see, there is nothing different about my creation of in-app purchase archives. I suspect a server-side problem.
1
0
560
Aug ’16
ITMS-90338: Non-public API usage
Dear Developer, We identified one or more issues with a recent delivery for your app, AisleGo Weddings 2.1.8 (6). Please correct the following issues, then upload again. ITMS-90338: Non-public API usage - The app references non-public selectors in AisleGo: _isKeyDown, _modifiedInput, _modifierFlags. 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 We already have our application production, nothing changed this time, now changed dev REST APIs endpoint to Prod and uploading on the test flight for App store release but getting this error upon test flight.
0
0
428
Mar ’23
We got ITMS-90433 - libswiftcore.dylib doent have the correct code signature
We got ITMS-90433 - libswiftcore.dylib doent have the correct code signatureWe tried below things:1. verified signature for libswiftcore.dylib under frameworks folder2. compared the frameworks & swiftsupport/iphoneos/.dylib , same number3. codesign is valid too4. compared with older IPA which was approved no changesany other things we can check ?
6
0
6.0k
Jun ’20
ITMS-90363: Xcode reject NSLocationWhenInUseUsageDescription key in info.plist App
Hello. I am developing a watchOS standalone app. I have added NSLocationWhenInUseUsageDescription key to info.plist Extension file successfully. When I try adding the same key to info.plist App, Xcode rejects my build with error ITMS-90363. So, I submit my build with a key added to info.plist Extension and receive the following warning via email: ITMS-90683: Missing Purpose String in Info.plist - Your app's code references one or more APIs that access sensitive user data. The app's Info.plist file should contain a NSLocationWhenInUseUsageDescription key with a user-facing purpose string explaining clearly and completely why your app needs the data. Starting Spring 2019, all apps submitted to the App Store that access user data are required to include a purpose string. If you're using external libraries or SDKs, they may reference APIs that require a purpose string. While your app might not use these APIs, a purpose string is still required. You can contact the developer of the library or SDK
2
0
3.7k
Jun ’20
Reply to Cant upload to AppStore with Xcode 7
It did not for me, unfortunately; I still get the same generic error and the following details from the Application Loader:/Applications/Xcode.app/Contents/Applications/Application Loader.app/Contents/itms/bin/iTMSTransporter: line 171: [: Loader.app/Contents/itms/java/lib/rt.jar: integer expression expectedError occurred during initialization of VMjava/lang/ClassNotFoundException: error in opening JAR file <Zip file open error> /Applications/Xcode.app/Contents/Applications/Application Loader.app/Contents/itms/java/lib/rt.jar
Oct ’15
iTMSTransporter invalid locale name error (ITMS-4136)
Trying to use iTMSTransporter to upload our game's achievement metadata, since I'd rather write an XML exporter than go through the mind-numbing task of entering all that stuff by hand.I'm getting this super weird error message:ERROR ITMS-4136: Invalid achievement locale name (language) for achievement 'achievement_dedication' - unsupported language: 'Swiss German'. at Software/SoftwareMetadata/SoftwareGameCenter'Needless to say, I'm not using Swiss German. My locales are as follows:enfritdeesruptAccording to the iTunesConnectAppMetadataSpecification5.2.pdf document, de sure looks like German and not Swiss German. What gives?
1
0
371
Jul ’15
ITMS-90626: Invalid Siri Support - No example phrase was provided for INSearchForMessagesInten
I've gotten the following error message a few times, does anyone know anything about it? I currently have a WidgetExtension and am suspecting that this is the circle. Your delivery was successful, but you may wish to correct the following issues in your next delivery: ITMS-90626: Invalid Siri Support - No example phrase was provided for INSearchForMessagesIntent in the 'en' language. Please refer to 'https://developer.apple.com/documentation/sirikit/registering_custom_vocabulary_with_sirikit/global_vocabulary_reference/intent_phrases' ITMS-90626: Invalid Siri Support - No example phrase was provided for INSetMessageAttributeIntent in the 'ko' language. Please refer to 'https://developer.apple.com/documentation/sirikit/registering_custom_vocabulary_with_sirikit/global_vocabulary_reference/intent_phrases' ITMS-90626: Invalid Siri Support - No example phrase was provided for INSetMessageAttributeIntent in the 'en' language. Please refer to 'https://developer.apple.com/documentation/sir
0
0
1.1k
Nov ’23
Mac OS/Electron - ERROR ITMS-90207
Hello there,I have some problems whit submitting my app to the Mac App Store.I am using Electron with React-js for my app and Electron-builder to create my distribution bundle.build info:“build”: { “appId”: “com.smarterback.smbapp”, “mac”: { “category”: “public.app-category.utilities”, “target”: [ “pkg”, “dmg”, “zip” ], “identity”: “iPhone Distribution: JENGO LLC (63UV74H5Q5)“, “entitlements”: “Info.plist”, “type”: “distribution”, “icon”: “test.icns” }, “mas”: { “category”: “public.app-category.utilities”, “target”: [ “pkg”, “dmg”, “zip” ], “identity”: “iPhone Distribution: JENGO LLC (63UV74H5Q5)“, “entitlements”: “Info.plist”, “type”: “distribution”, “icon”: “test.icns” }In Application Loader i upload zip include: SmarterBack.app:Screenshot URL: http://i.imgur.com/6k2SFyV.pngI had few errors on the way and I have fixed all exept this one:“ERROR ITMS-90207: “Invalid Bundle. The bundle at ‘SmarterBack.app’ does not contain a bundle executable”. ( http://i.imgur.com/wD3MmCN.png (57kB)) I’ve tried to ch
0
0
872
Aug ’17
ITMS-90683: Missing purpose string in Info.plist
I have an app that is getting rejected from TestFlight because of this error: ITMS-90683: Missing purpose string in Info.plist - 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 “TurtleTuner.app” bundle should contain a NSCameraUsageDescription key with a user-facing purpose string explaining clearly and completely why your app needs the data. If you’re using external libraries or SDKs, they may reference APIs that require a purpose string. While your app might not use these APIs, a purpose string is still required. For details, visit: https://developer.apple.com/documentation/uikit/protecting_the_user_s_privacy/requesting_access_to_protected_resources. The app does not use the camera, only the microphone. I cannot find references to the camera in any of the third party libraries I'm using. What are some ways to troubleshoot this beyond looking for camera in the few dependencies? F
0
0
1.1k
Jan ’24