ITMS-90158

When archiving and uploading a build of our tvOS app to App Store Connect with Xcode 13.3RC, it gets rejected with TMS-90562: Invalid Bundle - One or more dynamic libraries that are referenced by your app are not present in the dylib search path. When archiving and uploading with Xcode 13.2.1 the build is accepted and processed. I could not find any rpath issues when inspecting the binary with otool -L and otool -l. Has anyone else experienced the this issue with Xcode 13.3RC? I've filed feedback FB9952607

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

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) }

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.

The app references non-public symbols in : UIFontFeatureSelectorIdentifierKey_ForNewSwiftAPI, UIFontFeatureTypeIdentifierKey_ForNewSwiftAPI. 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. We got this error mail from the build-1 of the version 3.2 and we tried few more times till build number-5. We have upload same as version 3.1.

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

Hello, I am uploading an update of a test flight and it gives me this error in the final part. :( It gives me the following legend in xcode app store connection operation error error itms-90168: null In the Packaging record that is generated.... Failed for distribution item with error Error Domain=IDEFoundationErrorDomain Code=1 It generates that error right at the end, at the moment of finishing uploading the .ipa. It generates a registry folder where the .ipa and several files come out. Does anybody know what is it due to? Thanks in advance I will leave a little code of the last lines of the log with the idea that it can help something 2022-02-04 10:33:14 +0000 IDEDistributionItem init 2022-02-04 10:33:14 +0000 IDEDistributionItem init 2022-02-04 10:33:14 +0000 IDEDistributionItem init 2022-02-04 10:33:14 +0000 [OPTIONAL] Can't have a profile, not a bundle at 2022-02-04 10:33:14 +0000 IDEDistributionItem init 2022-02-04 10:33:14 +0000 IDEDistributionItem init 2022-02-04 10:33:14 +0000 Process

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?