“ITMS-90158”

I have a service that returns the itms-service:// url to perform a update on the app that makes the request.I also NSURLProtocol to handle https challenges and authentication space trust with my backend.when I unregister the NSURLProtocol, the system loads the itms-services:// download request fine. When I add my own protocol, the unsupported URL message starts to happen.I tried returning NO to canInitWithRequest: methods containing the itms-services URL scheme with no success. The only way I got it to work is:unregistering the custom NSURLProtocol for the time the service update and the subsequent call to itms-services occuradding an arbitrary statement that returns no when a request to my app update backend URL is detected, therefore not performing custom trust verification to my backend to avoid MITM.Does anyone know how to solve this?

Does anyone know where this is wrong?Dear Developer,We identified one or more issues with a recent delivery for your app, APPNAME. Please correct the following issues, then upload again.ITMS-90427: Invalid Swift Support - The expected dylibs are missing from the app’s Framework location, such as /Payload/appname.app/Frameworks.

Hi, When submitting manually signed macOS apps then this warning is shown after submission: WARNING ITMS-90889: Cannot be used with TestFlight because the bundle at is missing a provisioning profile. Main bundles are expected to have provisioning profiles in order to be eligible for TestFlight. I use the following commands for signing the app: export VM_CERTIFICATE=Apple Distribution codesign --deep -f -s $VM_CERTIFICATE -v --entitlements $VM_SOURCE_PATH/macos/App.entitlements $VM_APPNAME productbuild --component $VM_APPNAME /Applications --sign 3rd Party Mac Developer Installer: MyCompany outmac.pkg How can I get rid of the warning, so that the package can be used in TestFlight? Regards,

Hello to all,I have read almost all the posts related to this error, both on this forum and on other external ones, but apparently the origin is varied and often unknown.Like everyone, I compiled the App and sent it via Transporter, but the result is ITMS-90111: Invalid Toolchain - Your app was built with a beta version of Xcode or SDK ....These are the environmental characteristics:MacOS Catalina Version 10.15.2Xcode: 11.3 (15712)Tools: 11.3 (64532.3)SDK: iOS: 13,2: (17B102) iOS Simulator: 13,2: (17B102) macOS: 10,15: (19B90) 19,0: tvOS: 13,2: (17K90) tvOS Simulator: 13,2: (17K90) watchOS: 6,1: (17S80) watchOS Simulator: 6,1: (17S80)Note: the App is the first build and contains purchases in the AppStore and admob advertising.I also recreated all the certificates.I also tried compiling with MacOS High sierra (xcode 10.1), same result.Clearly I don't have beta software, what can be the cause? does it happen to someone else?Thank you

Trying to submit a tvOS build of an app I'm working on, and I'm getting the following error:ERROR ITMS-90471: Missing Image Asset. Your app is missing the Large App Icon asset 'App Icon - Small' in 'Payload/MadBombzTV.app'.Confused on what it thinks is missing? Large or small? Either way I have all the assets setup in the Assets.xcassets, 'App Icon - Large', 'App Icon - Small', 'Top Shelf Image', and 'LaunchImage'.Any thoughts to what's going on?Thanks!Kevin

Hello Recently I updated one pod version and because of that I needed to set the ALWAYSEMBEDSWIFTSTANDARDLIBRARIES setting to YES. But then while sending the build to the iTunes there was an error with code ITMS-90668 that mentions Bitcode problem. But I have bitcode disabled for the project and all of the pods. However by looking to the build logs I can see that the bitcode was being stripped from that standard Swift libraries which means that it is enabled for them. My question is why is that and how to disable bitcode for swift standard libs as well? The pod mentioned earlier is Helpshift 7.9.1-withCampaigns.

ITMS-90534: Invalid toolchain. New apps and app updates must be built with the public (GM) versions of XCode 6or later, and ios 8 SDK or later. ios 9 apps for internal TestFlight testers must be built with the latest seed of the ios SDK and uploaded with the latest seed of XcodeI just got this error when Submitting my app. I am using xCode beta currently. Does anyone know how to get around this problem??Thanks!!Coleman

ITMS-90809: Deprecated API Usage - Apple will no longer accept submissions of new apps that use UIWebView as of April 30, 2020 and app updates that use UIWebView as of December 2020. Instead, use WKWebView for improved security and reliability. Learn more (https://developer.apple.com/documentation/uikit/uiwebview). We have removed every single instance of UIWebView from our app mostly the pods were using that and we fixed that but still we are getting the error. We don't understand how to submit our app to App Store

HI, I'm trying to publish the first version of my iOS application in TestFlight.My app runs succesfully in my iPhone but I cannot publish it in TestFlight due to following error:ERROR ITMS.90328 Your package contains a file 'Applaudi.app/ApplaudiLocalStorageModel.momd/VersionInfo.plist' with a name that contains invalid characters. Avoid using control characters in the file names.I cannot find this file in proyect, and I have no idea how to solve the problem.Any suggestion????Thanks!!PD- I'm using Core Data for model Local Database.

While uploading archive after a minor update, I'm encountering ITMS error:90096 that reads as follows.------------------------------------------------------------------------------------------------------------------------------------------------------ERROR ITMS-90096: Your binary is not optimized for iPhone 5 - New iPhone apps and app updates submitted must support the 4-inch display on iPhone 5 and must include a launch image referenced in the Info.plist under UILaunchImages with a UILaunchImageSize value set to {320, 568}. Launch images must be PNG files and located at the top-level of your bundle ...-------------------------------------------------------------------------------------------------------------------------------------------------------What is the Info.plist entry needed to correct this?I already have LaunchImage (320, 568) and (320, 480) in top level of the project.MacOS Sierra 10.12.3 and Xcode 8.2.1 (8C1002).Thanks!

Our application should support locales for Albanian and Albanian(Kosovo). Xcode creates sq.lproj and sq-XK.lproj folders accordingly Everything works fine in xcode, but if we upload to appstore we always see this warning. I tried specifying other names for sq-XK to match https://developer.apple.com/library/archive/documentation/MacOSX/Conceptual/BPInternational/LanguageandLocaleIDs/LanguageandLocaleIDs.html aln, sq-RS, sq-KV, sq-KS, sq-Latn-XQ. The varning was always present. Is there any way to get rid of it? WARNING ITMS-90176: Unrecognized Locale - The locale used in localization directories at (Payload/{AppName}.app/base.lproj) are invalid. iTunes supports BCP47 but not the UN M.49 specification. Refer to the Language and Locale Designations guide for more information on naming your language-specific directories.

Hi,I'm just updating a tvOS app to the App Store - which is already on the store. I've only bumped the version and included some new assets, and now I'm getting the error: ERROR ITMS-90502: Invalid Bundle. Apps that only contain the arm64 slice must also have 'arm64' in the list of UIRequiredDeviceCapabilities in Info.plist. The key and value is already in the Info.plist, and I've havent experiences this - since I fixed it when uploading v1.0 - so am I the only one experiencing this problem?Regards,Kristian Trenskow

Hi I have tried to submit an application to the app store connect, but it has always given the following error: 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 problem is that I can't identify any reference to UIWebView in my solution. I used xamarin to make the app and I have xamarin forms in the most updated version. In the linker behavior I already have a link all.