ITMS-90158

Hi guys, need some help on this issue when I submit my testing app to TestFlight using GitHub Actions and Fastlane, I get this warning from App Store Connect: We noticed one or more issues with a recent delivery for the following app: Although delivery was successful, you may want to correct the following issues in your next delivery. Once you've corrected the issues, upload a new binary to App Store Connect. ITMS-90725: SDK version issue - This app was built with the iOS 16.2 SDK. Starting April 29, 2024, all iOS and iPadOS apps must be built with the iOS 17 SDK or later, included in Xcode 15 or later, in order to be uploaded to App Store Connect or submitted for distribution. I am using React Native CLI, and Fastlane to run and build my app through Github Actions. After scouring around, from what I understood was that all I needed to do was just to update my Xcode and iOS SDK to the latest, which I did. Currently my Xcode is 15.2 and iOS SDK is on 17 already. However, I still receive this warning w

From appstore receive email with this issues: ITMS-90738: Invalid purpose string value - The “NSPhotoLibraryUsageDescription” value for the NSPhotoLibraryUsageDescription key isn’t allowed in “.....”. 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 “.....” bundle should contain a NSPhotoLibraryUsageDescription key with a user-facing purpose string explaining clearly and completely why your app needs the data. ITMS-90738: Invalid purpose string value - The “NSCameraUsageDescription” value for the NSCameraUsageDescription key isn’t allowed in “....”. 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 “.....” bundle should contain a NSCameraUsageDescription key with a user-facing purpose string explaining clearly and completely why your app needs the data. I

After uploading our 3rd party app for shipping to the Mac App Store, we always receive a message from apple with this issue, but i cant find a good answer how to solve it: ITMS-90284: Invalid Code Signing - The executable 'com.xy.xy.pkg/Payload/xy.app/Contents/MacOS/xy' must be signed with the certificate that is contained in the provisioning profile. I changed and renewed the certs but no chance to solve it. Im using latest catalina macOS. Not using Xcode for code signing, using terminal as this is a unreal engine game: codesign -f -v -s 3rd Party Mac Developer Application: --entitlements entitlements.plist xy.app/ and for packaging: productbuild --component xy.app/ /Applications --sign 3rd Party Mac Developer Installer: xy.pkg thank you for ideas

I am trying to submit my updated iOS app via application loader but I keep getting an SDK Version Issue. ERROR ITMS-90725: SDK Version Issue. This app was built with the iOS 8.0 SDK. All iOS apps submitted to the App Store must be built with the iOS 11 SDK or later, included in Xcode 9 or later. Further, starting March 2019, all iOS apps submitted to the App Store must be built with the iOS 12.1 SDK or later, included in Xcode 10.1 or later. My apps are built from a third party but unfortunately they do not support anymore. Is there a way to rebuild the app using command line tools. I searched and tried to build using xcodebuild command but nothing seems to work. Is there an alternative?

We were able to validate and upload a mac arcade build to ASC, but when submitting it for review we got this message from Apple: ITMS-90812: Arcade static library missing or not correctly linked. The app does not link against the library performing the Arcade subscription check. I've never seen this error message before. For context, we recently upgraded to Unity 2020 to support Apple silicon. The build launches and runs without any issues so not sure how to address the issue. FYI 'Mac Store App Validation' is checked in the build settings. Any help would be appreciated!

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.

Hi all, I was having an issue which my APP was got rejected and I received an email said the following ITMS-90165: Invalid Provisioning Profile Signature. The provisioning profile included in the bundle 'app' (ios.app) cannot be used to submit apps to the iOS App Store until it has a valid signature from Apple. (Expired profile signing certificate.) However, I can see my certificate and profile are still valid till 2022 May from the developer portal. Can someone let me know why I encounter this issue please? I was able to submit an iOS APP back in 2022 Mar. Could anyone please advise what I need to do to resolve the current situation and how I can prevent the same case in ongoing please? Also, it will be great if anyone can let me know any limitation or standard of using the APPLE related certificate to do distribution and development.

Howdy,I've got an iOS 9 + watchOS 2 app I'm trying to upload to iTunesConnect. I'm using Xcode 7 (Organizer) and not the separate Application Loader app. There are other errors present, but the one that looks particularly interesting is:ITMS-90081 Applications built for more than one architecture require a iOS Deployment Target of 3.0 or later.The only target that isn't iOS9 is, interestingly enough, watchOS 2.0 in the Watch App and Watch Extension targets. Googling around the 3.0 or later hasn't been mentioned in many years - I'm wondering if there's some glitch in the code that is recognizing watchOS 2.0 as <3.0.Has anyone else been able to successfully upload a watchOS 2 app?Joe

I'm not sure what type of provisioning profile I need to create for my Mac App to allow TestFlight. I am archiving the app through Xcode and allowing it to control the provisioning but it still does not work.

My application always fails to upload due to this Error message: Incorrect Platform. You Included arm64 executable /app name/ in your iOS bundle. The app only targets armv7 devices and all extensions and targets are set to armv7. Just out of curiosity I created a empty Xcode project and without any modifications tried uploading it again. The same result... has anyone got an idea how I could solve that? I am using Xcode 12 and the transporter app to upload because Xcode is not working

Our app submission is being rejected with the following error message: TMS-90809: Deprecated API Usage - New apps that use UIWebView are no longer accepted. Instead, use WKWebView for improved security and reliability. We have thoroughly scanned our code and all dependent libraries for references to UIWebView and found none. looking for help, on how to address this issue