ITMS-90158

I've complied with the reason declaration following the links sent by the autogenerated emails for the surface level Runner declaration, however libswift has the incorrect values for the reason codes for UserDefaults. I've checked their github and there is no way to add issues since it is read-only. I'm also in the dark for who to contact regarding this. Does anyone have any idea how to resolve this aside from manually changing the privacy files? I don't want to have to do this each time I do pod install. ITMS-91055: Invalid API reason declaration - The PrivacyInfo.xcprivacy for the “Frameworks/libswiftObjectiveC.dylib” file contains “DDA9.1” as the value for a NSPrivacyAccessedAPITypeReasons key instead of a valid reason code for using an API in the NSPrivacyAccessedAPICategoryUserDefaults category.

We started receiving this error a few days ago when it appeared to be a wide spread problem on Apple's end. https://developer.apple.com/forums/thread/127678?answerId=715975022#715975022 Although it is supposedly resolved, I am still getting this error. I have incremented build and version numbers along with tweaking code. Also, the build agent is running macOS 12.4 and Xcode 13.4.1. ITMS-90338: Non-public API usage - The app contains one or more corrupted binaries. Rebuild the app and resubmit.,The app references non-public selectors in Align-Dev: isActivated. 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/ The only

I have an app with a fairly small watch extension. I've moved it to a watchOS 2.0 and when I try to upload, I'm getting this error.My app code is pretty small - less than a megabyte - and I don't have any significant resources. When I look in the build archive, my WatchKit app inside my iOS app's bundle's Watch folder is 30.3MB, of which 25.7MB is libswiftCore.dylib. Not sure why I'm running into this limit, since my WatchKit app is less than 50MB, and my own code is less than 1MB.Anyone else running into this? There are zero Google hits for ITMS-90389, which makes me think it's not a common problem.Thanks-- Steve

I have an issue that has prevented me from releasing two of my new apps so far. I created two new SwiftUI projects in Xcode 12 since WWDC20, both built with SwiftUI. By default these don’t include a LaunchScreen.storyboard, as you can now set the Launch Image in the info.plist. That was too fiddly and I didn’t like it, so I added a LaunchScreen.storyboard to my bundle, set it up, and set the Launch screen interface file base name value in my info.plist. The launch screen looks and works great when testing on my devices and simulators. However, when trying to upload to App Store Connect, I get the following error: ERROR ITMS-90476: Invalid Bundle. Your app supports multitasking on iPad, so you must include the launch storyboard file, 'LaunchScreen.storyboard', in your bundle, 'com.companyname.appname.' I’ve searched online several times, but all the answers just say ‘Check the Requires Full Screen box on your target’ - completely unhelpful as I want to support multitasking, and as of April 2020 multit

I uploaded the wrong times to the app, and I did as I was told, but it still didn't work. System 10.14.4, xcode10.2.1, i hope someone can help me.here is the error:ERROR ITMS-90730: Found Metal shader source code. The metal library file, 'Payload/xxx.app/default.metallib', contains source code or debugging information intended only for development. To resolve this issue, set the “Produce debugging information” build setting in Xcode to “No” and upload your app again. Learn more (https://developer.apple.com/documentation/metal/tools_profiling_and_debugging/developing_shaders_and_resolving_shader_issues_with_the_shader_debugger).

Hi. My client's app has 1-2GB purchases for sale, and they want to have dozens of them. We recently encountered ERROR ITMS-4162 in the Application Loader which states that there is a 5GB limit for all IAP hosted content.Is that accurate? I can't find any documentation one way or the other, and only a few hits come up on Google and the Dev Forums. I see a lot of corroboration, but it would be great to get something definitive from Apple.Rich, do you know if there's any way to host more than 5GB total content?Application Loader screenshot:http://cl.ly/1n1f2q2X1P3N

HELP. PLEASE. I am so close...where oh where do i fix these and HOW. App Store Connect Operation ErrorERROR ITMS-90685: CFBundleIdentifier Collision. There is more than one bundle with the CFBundleIdentifier value 'com.XXX.XXXXXXXX' under the iOS application 'XXXXXX'.App Store Connect Operation ErrorERROR ITMS-90347: Bad bundle identifier. The bundle identifier 'XXXXX of the application extension XXXXXXXX should start with the application's bundle identifier 'XXXXXXXXX and not contain more than one period “.” after the application's bundle ID.

Hi, community, when I build my project I have the same reject from App Store: ITMS-90430: Invalid Swift Support - The file libswiftAVFoundation.dylib doesn’t have a signing ID. Sign the file, rebuild your app using the current public (GM) version of Xcode, and resubmit it I follow a procedure before the build, but this works one time on X times... cleanup pods - cd ios & pod deintegrate & pod update cleanup Xcode derived data - rm -rf ~/Library/Developer/Xcode/DerivedData/* clean build folder Product->Clean Build Folder in Xcode Specs below: OSX: big sure 11.4 XCode: 13.2.1 Libs: native-base: ^2.15.2, npm: ^7.10.0, react: 17.0.1, react-native: 0.64.1, react-redux: ^7.2.4, redux: ^4.1.0, rxjs: ^6.6.7, @types/react-native: ^0.64.0, typescript: ^3.8.3 This bothers me ... I waste hours on builds. Regards AA

I'm using Xcode 10.1 - My app compiles to Archive fine with no errors or warning. While uploading it to app store connect generates the following error after the upload starts:ERROR ITMS-90710: Invalid Image Asset. The image asset 'App Icon' in 'Payload/GoVegas.app' has an issue with one of its layers at index '2'. Ensure each layer has an image for each scale value that is used.I have two sections with App IconApp Icon - App StoreandApp IconI have gone over these images with a fine toothed comb and cannot see why it's failing. I even replaced the middle and back icons with jpg instead of png, to insure they have no transparency channel.I have no warnings at all creating the archive. There are no images flaged in the issue navigaor nor when examining assets.xcassets.I hope somone can help. This is a very high profile project and I feel I'm so close, but...

Yesterday it was still able to submit iOS App normally, but today it is not allowed because of this. I not import AVFCapture/AVFCore fmwk, and _CMTimebaseCreateWithMasterClock isn't non-public. ITMS-90338: Non-public API usage - The app references non-public symbols in Frameworks/libksygpulive.framework/libksygpulive: _CMTimebaseCreateWithMasterClock,The app links to non-public libraries in zhibo: /System/Library/PrivateFrameworks/AVFCapture.framework/AVFCapture, /System/Library/PrivateFrameworks/AVFCore.framework/AVFCore. 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/ etc._CMTimebaseCreateWithMasterClock -… | Apple

Dear Developer, We identified one or more issues with a recent delivery for your app Please correct the following issues, then upload again. ITMS-90338: Non-public API usage - The app references non-public symbols in Loupe: _CGImageGetImageSource. 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 There are two problems, one is that our release/production build is succeeding and uploading to TestFlight. The other problem is we do not understand what the issue is even when reading your automatic message. How can we debug this ? How can we identify the source of the problem ? Do you have a

Hello,Have a problem to submit app to itunesconnect, done before several times with Xcode9 and it was working fine, now I can't find any solution over the web. Can you plase help me.Its a Sticker Pack App build in Xcode 10, just draged the images and that's it, didn't add anything in plist.Thanks,ERROR ITMS-90039: Type Mismatch. The value for the Info.plist key LSApplicationLaunchProhibited is not of the required type for that key. See the Information Property List Key Reference at https://developer.apple.com/library/ios/documentation/general/Reference/InfoPlistKeyReference/Introduction/Introduction.html#//apple_ref/doc/uid/TP40009248-SW1

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