“ITMS-90338”

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

I understand that this error is because Organizer is submitting a binary with the same version number, but I have changed the version numbers. I've done the homework and looked up similar forum posts on this error, but the problem is not as simple as incrementing the build number.Here's what I did:My current version in the store is 2.0.4In iTunesConenct, I created a new version submission for 2.1.0. I filled out all fields (except Build) and clicked Save. It is now marked Ready for Submission.In Xcode, I changed the Version to 2.1.0 and the Build to 2.1.0.In Xcode, I built and ran the app. It works!I opened Organizer. In Archives, it shows Version 2.0.4, and my last submission was months ago.In Organizer, I clicked Submit and followed the steps. I got the Redundant Binary error that 2.0.4 already exists.To double-check, I opened my -Info.plist file and it shows both Bundle Version and Bundle Versions string, short as 2.1.0To triple-check, I looked in my Target > Build Settings > Packaging. I can see tha

After uploading a new App to the App Store Connect i receive an e-mail stating:ITMS-90034: Missing or invalid signature - The bundle '...' at bundle path 'Payload/...' is not signed using an Apple submission certificate.The App don't use any capability.I've used Xcode to upload, as in a previous App which now is on the App Store.All the apps use the default configuration: Automatically manage signing, Provisioning profile Xcode Managed Profile, Signing Certificate Apple Development: ############The requested Signing Certificate is present in the keychain in 3 versions, the last one is valid (the older 2 are revoked).What I should correct?

Hi all, Im trying tu publish an app for iOS and I get it rejected by the lack of this privacy manifest, but unless I understood this wrong, this manifest is needed for external tools used, or maybe Im wrong, Im publishing an app made in Unity, so in this case, one has to include a privacy manifest by default? Sorry Im lost in all these terms, so I don't know if im asking something redundant, if you know how to fix this issue please tell me or direct me to the process because I haven't been able to identify the issue. Thanks a lot for any clue beforehand really

I have a maccatalyst App on the store, uploaded 20 March. Am now attempting to upload a new version but it fails with:Unable to process application at this time due to the following error: Invalid Provisioning Profile. The provisioning profile included in the bundle maccatalyst.com.plugh.XYZZY [maccatalyst.com.plugh.XYZZY.pkg/Payload/XYZZY.app] is invalid. [Invalid 'com.apple.application-identifier' entitlement value.] For more information, visit the macOS Developer PortalAs I mentioned this App is already on the store and nothing has change in the project relating to profiles/signing to my knowledge other than a new Xcode. In fact, signing and provisioning is all automatic, and the maccatalyst app id is auto-generatedInterestingly, I still have the previous App bundle that was successfully uploaded to the store, and when I (re-)verify it there is an identical error to the above. So I am at a loss as to how to move ahead at this point in time.

Hi, I receive the following mail after the upload of my app form xCode to the Apple Connect platform. Before uploading, I correctly validate the version, and xcode gives me the validation. Do someone know how resolve this issue? Thanks in advance

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?

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.

Since yesterday (03/22/24) we are unable to upload new or existing builds to AppStoreConnect. We get the following error - “Error ITMS-90432 Unexpected file found in Frameworks. MyApp.app/Frameworks/Configurations” file is in the Frameworks directory, but the Swift runtime libraries are the only files permitted in that directory. Please remove this file and upload a new build. (ID: 57e219ea-d27e-465d-9e9b-ec41d3a0b1f7). We have tried rebuilding targerts with no changes for Builds that use to upload ok and they now get the same error too. Is this an appstoreconnect bug? If not where is the Frameworks directory and how do we remove the file?