“ITMS-90158”

Yesterday with xcode7 package online, has been the problem, can I put this part set full set again, but still can't, why

Application validated sucessfully but when i clicked on submit apps to App store then it show error as following. (Archive submission failed with error). ERROR ITMS-90086 “Missing 64-bit support”.

I have an iPad app that we just added iPhone support to. It runs fine on the iPhone devices we've tested on. When we try to distribute the app by uploading it to App Store Connect the build doesn't show up in the TestFlight iOS Builds and we get an email from Apple Developer Relations that says this: Please correct the following issues and upload a new binary to App Store Connect. ITMS-90891: Missing required icon - The bundle does not contain an alternate app icon for iPhone / iPod Touch of exactly '120x120' pixels, in .png format for iOS versions >= 10.0. To support older versions of iOS, the icon may be required in the bundle outside of an asset catalog. Make sure the Info.plist file includes appropriate entries referencing the file. See https://developer.apple.com/documentation/bundleresources/information_property_list/cfbundleicons Apple Developer Relations We have followed the instructions on the web site and we have followed the instructions on other posts in this forum but nothing works. W

When I'm using itms-services://?action=download-manifest&url={URL}, itms-services seem to be working. But, when I'm using itms-services://?action=download-manifest&url={SAS URL}, it doesn't seem to work (nothing happens). Can someone explain the issue and show possible alternatives to this?

Im trying to upload my first app through Application Loader and Im getting this error:ERROR ITMS-90190: Invalid Info.plist Key. The key 'UISupportedDevices' in the Info.plist file is not valid.I have no idea what it means and I can't find info or support in Apple documentationMy app has also an Apple Watch application targetAlso I have searched through all my files in the project looking for UISupportedDevices and I don't have any key with this name. Hope anyone could help me!

Hi When I'm using itms-services://?action=download-manifest&url=url-to-plist, everything works fine and I'm able to download the application. But, when I'm using itms-services://?action=download-manifest&url=presigned-url-to-plist, it doesn't seem to work. It shows a popup saying Open this page in iTunes? After clicking yes nothing happens. Can someone please tell me what's the exact issue here? Thank you. P.S. - The presigned url correctly redirects to the manifest file.

ITMS-90338: Non-public API usage - The app references non-public selectors in HouseMartApp.iOS: checkFocusGroupTreeForEnvironment:, commissioningComplete:, determineAppInstallationAttributionWithCompletionHandler:, errorForCHIPErrorCode:, errorToCHIPErrorCode:, lookupAdConversionDetails:, setButtonsView:, setDoubleTapGestureRecognizer:, setGrid:, setListenPort:, setLongPressRecognizer:, setTextLabel:, sharedController, sleep:, test:, toggle:. 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. we are not able to find issue.can you provide where is exactly isssue.

Hi, I am unable to upload my app with mac book pro (13 inch ,M1) , Xcode 13.2.1 (13C100), swift 5, and cocoapods-1.10.1 version, receiving following mail from App Store connect after 10 mins of upload to TestFlight or AppStore. Error : We identified one or more issues with a recent delivery for your app, MyApp 1.4.6 (89). Please correct the following issues, then upload again. ITMS-90429: Invalid Swift Support - The files libswiftDarwin.dylib, libswiftMetal.dylib, libswiftCoreAudio.dylib, libswiftsimd.dylib, libswiftQuartzCore.dylib, libswift_Concurrency.dylib, libswiftos.dylib, libswiftObjectiveC.dylib, libswiftDispatch.dylib, libswiftCoreLocation.dylib, libswiftAccelerate.dylib, libswiftCoreGraphics.dylib, libswiftCoreData.dylib, libswiftCoreFoundation.dylib, libswiftUIKit.dylib, libswiftCoreMedia.dylib, libswiftAVFoundation.dylib, libswiftCore.dylib, libswiftFoundation.dylib, libswiftPhotos.dylib, libswiftMediaPlayer.dylib, libswiftCoreImage.dylib aren’t at the expected location /Payload/MyApp.app

when i try to deploy application in test flight, the build goes successful, but it gives me a error email saying below. ITMS-90381: Too many symbol files - These symbols have no corresponding slice in any binary [D08A95DF-6230-3140-A7A6-3D39CB0E9AC5.symbols, CEFE32B6-DE82-34B8-843D-AB9C58AD7302.symbols, 41B74E00-709D-3407-AB85-A8187E917ACF.symbols]. Kindly let me know, how can i understand the issue and what will be the fix. Thanks.

We are trying to upload new build for our already existing app to appstore, with a build script to embed framework(Which is just copying from build directory to MyApp.app/Frameworks). Everything builds and works fine in my local machine. But getting this error while uploading to appstore. ITMS-90432: Invalid Swift Support - The file MyApp.app/Frameworks/Framework1.framework, MyApp.app/Frameworks/Framework2.framework doesn’t have the correct file type for this location. Ensure you’re using the correct file, rebuild your app using the current public (GM) version of Xcode, and resubmit it. We are copying to the correct directory, but still getting the above error while uploading. Are we missing the obvious here?

An ITMS-91061: Missing privacy manifest rejection email looks as follows: ITMS-91061: Missing privacy manifest- Your app includes , which includes , an SDK that was identified in the documentation as a privacy-impacting third-party SDK. Starting February 12, 2025, if a new app includes a privacy-impacting SDK, or an app update adds a new privacy-impacting SDK, the SDK must include a privacy manifest file. Please contact the provider of the SDK that includes this file to get an updated SDK version with a privacy manifest. For more details about this policy, including a list of SDKs that are required to include signatures and manifests, visit: https://developer.apple.com/support/third-party-SDK-requirements. Glossary ITMS-91061: Missing privacy manifest: An email that includes the name and path of privacy-impacting SDK(s) with no privacy manifest files in your app bundle. For more information, see https://developer.apple.com/support/third-party-SDK-requirements. : The specified privac

Hi all, I have repeatedly the issue that a certain .strings file in my app's bundle has the extended files attribute com.apple.quarantine set. Consequently the submission fails with the following mail notification: We noticed one or more issues with a recent delivery for the following app: [...] ITMS-91109: Invalid package contents - The package contains one or more files with the com.apple.quarantine extended file attribute, such as “abcdef.strings”. This attribute isn’t permitted in macOS apps distributed on TestFlight or the App Store. Please remove the attribute from all files within your app and upload again. I'm able to resubmit the bundle after cleaning the file attribute via xattr -d -r com.apple.quarantine..., but the funny thing is it happens again and again - on a .strings file which hasn't been downloaded (but manually created), shouldn't be under Gatekeeper's quarantine, and wasn't edited in the meantime. Is anybody else observing the same issue with macOS 15.4.1, Xcode 16.3? Greetings,

We have prepared the Package of our Application for MacOS using Delphi Sydney 10.4. When we upload it using Transporter the delivery appears correct, but after a few minutes we received an eMail from AppStore Connect reporting errors ITMS-90238: Invalid Signature. The errors refer to dynamic libraries, .a, that we have located in the Frameworks folder of our package, all the libraries have been developed with XCode and signed with CodeSign using Certificate 3rd Party Mac Developer Application ....., the same certificate that we use to sign the application. Installing the package generated by Delphi on our MAC and analyzing the signature of the libraries with CodeSign, we see that the signatures have not been lost and are correct. WE DO NOT KNOW WHAT WAY WE SHOULD TAKE, we would ask you to indicate a solution to finally be able to publish our Application in the AppStore. THANK YOU.

I have had the same problem. The apple ids I have used include com.appname, com.domain.appname, com.domain.appname.XXX. None of these bundle identifiers have worked. This is the error message I receive each time:ERROR ITMS-90347: Bad bundle identifier. The bundle identifier 'com.Signal' of the application extension Signal.app/PlugIns/Signal.appex should start with the application's bundle identifier 'com.Signal' and not contain more than one period “.” after the application's bundle ID. ERROR ITMS-90347: Bad bundle identifier. The bundle identifier 'com.Signal' of the application extension Signal.app/PlugIns/Signal.appex should start with the application's bundle identifier 'com.Signal' and not contain more than one period “.” after the application's bundle ID.The domain is always drewbennettappname: SignalI have looked at all of these sites:An App ID with Identifier 'com.example.app.extention' is not available. Please enter a different stringhttps://forums.developer.apple.com/thread/15712ER

We have prepared the Package of our Application for MacOS using Delphi Sydney 10.4. When we upload it using Transporter the delivery appears correct, but after a few minutes we received an eMail from AppStore Connect reporting errors ITMS-90238: Invalid Signature. The errors refer to dynamic libraries, .a, that we have located in the Frameworks folder of our package, all the libraries have been developed with XCode and signed with CodeSign using Certificate 3rd Party Mac Developer Application ....., the same certificate that we use to sign the application. Installing the package generated by Delphi on our MAC and analyzing the signature of the libraries with CodeSign, we see that the signatures have not been lost and are correct. WE DO NOT KNOW WHAT WAY WE SHOULD TAKE, we would ask you to indicate a solution to finally be able to publish our Application in the AppStore. THANK YOU.