ITMS-90158

please help to solve this error when I upload app via transporter get this : upload failed (7 issues errors ) : ERROR ITMS-90035: Invalid Signature. Invalid Info.plist (plist or signature have been modified). The file at path [8b787a9f7862.app/vbulletin] 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/library/ios/documentation/Security/Conceptual/CodeSigningGuide/Introduction/Introduction.html ERROR ITMS-90046: Invalid

Hi We're trying to publish an app build to Testflight. We've successfully done the build, but when we archive the build, we get this error: error itms-90168 null. We are able to upload the build, it then SEEMS like the build is successfully archived. Then we validate the app, which is successful, but then when we click distribute, it gives an error: error itms-90168 null We've been struggling with this for quite a while and have tried things to solve the issue, but we haven't been successful this far. It's difficult to try figure out what is wrong, as the error message merely says Null instead of giving specific details.

I have watchOS app and I want to give link in app to open App Store app (on watch) to easily update from there. I have tried below code but its not working. let urlString = itms://itunes.apple.com/app/id_YOUR_APP_ID if let url = URL(string: urlString) { WKExtension.shared().openSystemURL(url) }

My submission is stuck at “Prepare for submission”.I inadvertently uploaded a build created with XCode 7.1 beta. Therefore, if I try to Submit for Review in iTunes Connect I get an error message stating that the app cannot be uploaded with a beta version of the SDK. So I prepared a new buildusing the current version of Xcode and try to upload. But the upload in XCode failed with the error “ERROR ITMS-4238:Redundant Binary Upload. There already exists a binary upload with build version ‘2.1’ for train ‘2.1’” at SoftwareAssets/PreReleaseSoftwareAsset”.iTunes Connect does not give me the option to delete the uploaded build. And the + sign under My Apps in iTunes Connect does not allow me to create a new version. If I anyway attempt to upload a newer version from XCode, iTunes Connect sees the uploaded version but doesn't five me the option to submit it for review. Therefore, my submission process is completely stuck. Any advice?

Hello, TLDR; Are there any guidelines (Apple or 3rd party) to deploy a Python + QT + PyInstaller app on macOS App Store? Why should we have one? Python is currently the most popular language, QT is the most popular desktop app platform to use with Python and PyInstaller is pretty much the only game in town to package this type of app for macOS. Problem: By following the guidance on several forums and many sleepless nights we were able to package and notarize the app. However, when we submit the .pkg for review using Transporter we get ~200 signature errors in an email like the below. Pretty much for all .so .dylib files except ours where we individually signed with a script as recommended. We are aware of the famous Signing a Mac Product For Distribution forum post, yet we don't know how not to use --deep to sign since we use several popular 3rd party libraries from PyPi (pip install) and leaving out --deep will even prevent notarization. And clearly, --deep is not working for the App Store scenario. A soluti

I am trying to submit a new App to the Mac AppStore. In App Store Connect, I create a new and enter the app's bundle identifier in the proper field. Then when I use Xcode to submit the application I get the following error codes:ERROR ITMS-90511: CFBundleIdentifier Collision. The Info.plist CFBundleIdentifier value '$(PRODUCT_BUNDLE_IDENTIFIER)' of 'Mad Octahedron.app/Contents/Resources/MadOctahedron' is already in use by another application.An unknown error occurred.ERROR ITMS-90277: Invalid Bundle Identifier. The application bundle contains a tool or framework $(PRODUCT_NAME) [com.Ambraw.MadOctahedron.pkg/Payload/Mad Octahedron.app/Contents/Resources/MadOctahedron] using the bundle identifier '$(PRODUCT_BUNDLE_IDENTIFIER)', which is not a valid bundle identifier.An unknown error occurred.ERROR ITMS-90261: Bad CFBundleExecutable. Cannot find executable file that matches the value of CFBundleExecutable in the nested bundle $(PRODUCT_NAME) [com.Ambraw.MadOctahedron.pkg/Payload/Mad Oc

Since the 20th of April, 2021 my apps have been sporadically (1 in 2) failing for the ITMS-90725 issue and is explained as follows: ITMS-90725: SDK Version Issue - This app was built with the iOS SDK. All iOS apps submitted to the App Store must be built with the iOS 13 SDK or later, included in Xcode 11 or later. Further, starting April 26, 2021 iOS apps submitted to the App Store must be built with the iOS 14 SDK or later, included in Xcode 12 or later. Which is very odd as I'm using XCode 12.4, has anyone else experienced this issue and/or fixed it?

Hi, Maybe someone here can help me ... I have an app (ios xcode swift) that I need to distribute unsigned. So far so good (in the xcode project target settings I have inserted the field: 'CODE_SIGNING_ALLOWED setting for release' NO '. In this way using' Archive 'I get the package in xcarchive format. Just a problem, the app has some 'entitlement' settings like push notifications, background use of bluetooth .. .etc. When my client tries to distribute the app with 'Organizer', he signs it with his certificate and provisioning file, and then downloads to the app store. but I always get the error 'ITMS-90078: Missing Push Notification Entitlement' Has anyone of you already distributed an app with the 'manual' signature as I do in practice?

Hello. Please let me preface my question with this: I am new to IOS development, XCode and Mac computers, in general. So, apologies if my question sounds uniformed. I have built a prototype game, which I would like to put on the App Store, so that my friends and partners can test. I only want this available via the internet, so that they can access the app and test, internally. It is not ready to go into production. I build the app in Unity and ported to Xcode. I build the applications Archive and follow the process to upload it. I receive no errors. But, after I upload the application, and it finishes processing, the status (under iOS Builds) is Invalid Binary. I also received an email that said: ITMS-90562: Invalid Bundle - The app cannot be processed because options not allowed to be embedded in bitcode are detected in the submission. It is likely that you are not building the app with the toolchain provided in Xcode. Rebuild your entire app with the latest GM Xcode and submit the app again. How c

I'm build an iOS 15 app in Xcode 13 and whenever I try to submit to the App Store for TestFlight testing I get the following error: ERROR ITMS-90345: Metadata/Info.plist Mismatch. The value for bundle_identifier in the metadata.xml file does not match the value for CFBundleIdentifier in xxxxx [Payload/xxxxx.app]. (App name removed because it doesn't matter) Based on some other forum answers, I doubled checked that there are no spaces in the bundle ID, and have tried repeatedly re-typing it, and copy and pasting it from an alternate version of the project that used to submit to TestFlight fine, but nothing has worked. Honestly, I have no idea where metadata.xml lives or how to even check what value is in it, which is part of the problem. Any advice or guidance here would be greatly appreciated, because I'm not sure what else I can do at this point, other than throwing everything away and starting over in Xcode 12 and iOS 14. Thanks!

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

Hello everyone, I have been developing a game in UE4 and I would like to send my build to TestFlight. I'm working on a windows machine and remote build my project on a updated Mac book pro with Monterey and Xcode 13.1 I have no problem generating the development build and the shipping build on the windows side. However when I try to upload the .ipa using transporter I get this error message that suggest that the SDK used to compile is not the right one. ERROR ITMS-90725: SDK Version Issue. This app was built with the iOS 13.2 SDK. All iOS apps submitted to the App Store must be built with the iOS 14 SDK or later, included in Xcode 12 or later. I should add that, in the past, I have been able to upload the game on iTunes connect. Any help would be greatly appreciate Best