Hello, i know this topic is here since ever, also in other forums, however this topic i face for a month and cant get pass it, I tried all other suggestions which didnt bring me anywhere. so, project using cmake in order for Qt creator (so c++ base project with enabled swift), however once i run a cmake which generates *.xcodeproj for Xcode, i open it via xcode and can properly build and deploy to device. however when I try to archive and sent to Testflight/AppStore, I get: ITMS-90426: Invalid Swift Support and when I try to followup guides to create it manualy, copying libs from: $(TOOLCHAIN_DIR)/usr/lib/swift-5.0/$(PLATFORM_NAME) plese here note, that ALL guides indicate to use folder swift, however there are no *.dylib files... they are only in swift-5.0 folder then I receive an error type: ITMS-90429: Invalid Swift Support - The files libswiftMetal.dylib, libswiftHomeKit.dylib, libswiftsimd.dylib, libswiftCallKit.dylib, libswiftos.dylib, libswiftNetwork.dylib, libswiftMapKit.dylib, libsw
ITMS-90338
1,571 results found
Post
Replies
Boosts
Views
Activity
For others to know, in the meantime we did a testfligh submission with 4 + ODR and it failed with the following message: ITMS-90559: Thinned app size is too large - The “/Payload/MyApp.app” app bundle in the universal variant is 5 GB, which exceeds the maximum allowable size. After app thinning, if your iOS app contains on-demand resources, the app bundle in any variant must be less than 2 GB. For details, visit: https://developer.apple.com/help/app-store-connect/reference/on-demand-resources-size-limits. So it looks that if you don't have ODR then your app size can < 4GB, but if you do have ODR then the thinned app size must be 2 GB Hope it helps someone searching for the same info. Thanks
Recently, I’ve started receiving the following error when submitting a new app version: ITMS-90863: Macs with Apple silicon support issue - The app links with libraries that aren’t present in macOS: /usr/lib/swift/libswiftCloudKit.dylib This has led to my app (previously available on the Mac App Store as “Designed for iPad”) no longer being downloadable on macOS. Recent Changes: No updates were made in the code related to CloudKit or other libraries. Upgraded to macOS 15.0, then 15.1, and Xcode 16.0, then 16.1. Problem: I’ve tried clearing the build folder, adding libswiftCloudKit.tbd, and adjusting the LSMinimumSystemVersion value, but the issue persists. The message lacks specific guidance on the issue or resolution. I’ve reviewed project settings but found nothing relevant. Any help or similar experiences would be appreciated! Thanks!
We have a CD pipeline set up for many apps (we're an app dev agency, we're uploading apps all the time). Uploads of our apps to AppStoreConnect using the iTMSTransporter command line tool started failing a few days ago. If we attempt to upload the same bundle using the Mac Transporter app, it uploads just fine. The problem only seems to be the iTMSTransporter command line tool. The version of the tool we're using is: iTMSTransporter, version 3.3.0 I've also tried running these commands pointing at the version of iTMSTransporter running at /Applications/Transporter.app/Contents/itms/bin/iTMSTransporter but this won't even start due to some Java security certificate issue. An example of the command we are calling is: /usr/local/itms/bin/iTMSTransporter -m upload -v eXtreme -f /path/to/Bundle.itmsp -jwt {generatedJwtHere} The bundle appears to actually upload to the AppStore OK, after lots of logs we get a message like: INFO: Reservation committed: (CPUSource221/v4/0b/e5/74/0be57409-0479-3c02-0
I am trying to set up a workflow where Apple Vision Pro users in my organization can install a signed enterprise .ipa file from an internal web page. The relevant link looks something like this: <a role=button href=itms-services://?action=download-manifest&url=https://my.example.com/path/manifest.plist>Click here to download</a> After verifying that all the mime types were correct on the server and the certificate was valid, I finally attached my AVP headset to my Mac's console app and saw that the errors look like this: [com.example.myapp] Skipping due to incompatible platform: com.apple.platform.xros Could not load download manifest with underlying error: Error Domain=ASDErrorDomain Code=752 Not compatible with this platform: com.apple.platform.xros UserInfo={NSDebugDescription=Not compatible with this platform: com.apple.platform.xros} This manifest.plist was made by the Distribute App workflow in Xcode 16.0. Multipart question: Is installing VisionOS apps via m
I am running the iTMS Transporter on a OL7 k8s pod. The issue appeared when I have set the read-only filesystem. Trace: Exception in thread main java.lang.ExceptionInInitializerError at com.apple.transporter.launcher.Application.start(Application.java:120) at com.apple.transporter.launcher.Application.main(Application.java:766) Caused by: java.lang.NullPointerException: Cannot invoke com.apple.transporter.launcher.api.LaunchLogger.warn(String) because com.apple.transporter.launcher.util.FileUtil.logger is null at com.apple.transporter.launcher.util.FileUtil.logWarning(FileUtil.java:151) at com.apple.transporter.launcher.util.FileUtil.userHomeDirectory(FileUtil.java:110) at com.apple.transporter.launcher.util.FileUtil.localConfigHome0(FileUtil.java:188) at com.apple.transporter.launcher.util.FileUtil.(FileUtil.java:25) ... 2 more I have to have the pod filesystem read-only it is a security compliance requirement, so I need to find a solution for this issue. Before setting the the FS to read-only every
We also face the same issue. For our case we are using iTMSTransporter 3.3.0.16 What we try is if we run #> /usr/local/itms/bin/iTMSTransporter -m upload -f ./upload.itmsp then we will see the Invalid provisioning profile signature but if we run #> /usr/local/itms/bin/iTMSTransporter -m upload -assetFile ./upload.itmsp/upload.ipa then the file will upload successfully. Based on the log, looks like the error is from Apple 's web service Using operation named: validateAssets
Hi, I have an error while uploading to test flight by fastlane and transporter. 07:13:05 [Transporter Error Output]: Return status of iTunes Transporter was 1: ERROR ITMS-90165: Invalid provisioning profile signature. The provisioning profile included in the com.test.example bundle [“Payload/Example.app”] can't be used to upload apps to App Store Connect until it has a valid signature from Apple. My xcode version is 15.4 and the iTMSTransporter is 3.3.0. It seems like this error has been reported the other internet recently. https://stackoverflow.com/questions/79118087/getting-error-invalid-provisioning-profile-signature-in-transporter-while-ios-ap https://www.yunedit.com/article/error90165 Has anyone solved this?
Hi, I uploaded an updated version of my app to App Store Connect yesterday, usually my build would show up under half an hour but this time it hasn't after over 16 hours. It's a simple app. I cleared an earlier version, then there was an email saying 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-90899: Macs with Apple silicon support issue - The app isn‘t compatible with the provided minimum macOS version of 13.5. It can run on macOS 14.0 or later. I unchecked the box that says use for Mac option. I have written to Apple support, yet to hear from them, Meanwhile should I re upload the app with a newer build number and version? Thanks a lot. (I saw quite a few threads on this topic with no one close to any solution so asking again just in case)
I roughly followed the steps above outlined by / above and was able to get my fastlane build to succeed. Clean-up current build environment: Remove AppStore version of Transporter (I think this optional) Download and install the latest pkg file for iTMSTransporter from: https://help.apple.com/itc/transporteruserguide/en.lproj/static.html#apdAe41970bd As this point you can either update your build configuration, or symlink the java binary into the right location. Do one of the following... Update your build-config (this is what I did): Ensure that the following to environment variables are set in the build environment export FASTLANE_ITUNES_TRANSPORTER_USE_SHELL_SCRIPT=1; export FASTLANE_ITUNES_TRANSPORTER_PATH=/usr/local/itms; To sym-link the installation: mkdir -p /Applications/Transporter.app/Contents/itms/bin -- may require sudo or switching to root user (e.g. sudo su -) ln -s /usr/local/itms/bin/iTMSTransporter /Applications/Transporter.app/Contents/itms/bin/iTMSTranspo
Even I am facing similar issue. Even though timezone is different the cert expiry time matches. xcrun iTMSTransporter --version Running iTMSTransporter at path '/Applications/Transporter.app/Contents/itms/bin/iTMSTransporter'... java.util.concurrent.ExecutionException: java.lang.SecurityException: java.security.cert.CertificateExpiredException: NotAfter: Thu Oct 10 23:07:19 IST 2024 at java.base/java.util.concurrent.CompletableFuture.reportGet(CompletableFuture.java:396) at java.base/java.util.concurrent.CompletableFuture.get(CompletableFuture.java:2073) at com.apple.transporter.launcher.Application.start(Application.java:214) at com.apple.transporter.launcher.Application.main(Application.java:766) Caused by: java.lang.SecurityException: java.security.cert.CertificateExpiredException: NotAfter: Thu Oct 10 23:07:19 IST 2024 at com.apple.transporter.launcher.loader.PinnedX509TrustManager.verifyCertificateChain(PinnedX509TrustManager.java:141) at com.apple.transporter.launcher.loader.SignatureVerifier.v
You can check your iTMSTransporter position is in Transporter.app or download from Apple webview. I've downloaded iTMSTransporter from https://help.apple.com/itc/transporteruserguide/en.lproj/static.html#apdAe41970bd and change my command line from /Applications/Transporter.app/Contents/itms/bin/iTMSTransporter to /usr/local/itms/bin/iTMSTransporter to solve this problem.
Hi, I had a same problem on last friday. I think the Transporter app has some problem. I solved it by following the steps below. Remove Transporter.app Install iTMSTransporter - https://itunesconnect.apple.com/WebObjects/iTunesConnect.woa/ra/resources/download/public/Transporter__OSX/bin/ Install the pkg mkdir -p /Applications/Transporter.app/Contents/itms/bin ln -s /usr/local/itms/bin/iTMSTransporter /Applications/Transporter.app/Contents/itms/bin/iTMSTransporter Maybe you need to add a path.
After building the app for TextFlight, I uploaded it. After that, I initially received the following message via email. ITMS-90899: Macs with Apple silicon support issue - The app isn‘t compatible with the provided minimum macOS version of 11.0. It can run on macOS 12.0 or later. Please specify an LSMinimumSystemVersion value of 12.0 or later in a new build, or select a compatible version in App Store Connect. So I added LSMinimumSystemVersion to info.plist, increased the version, and uploaded it again. Next ITMS-90863: Macs with Apple silicon support issue - The app links with libraries that aren’t present in macOS: /usr/lib/swift/libswiftCloudKit.dylib @rpath/libswiftCloudKit.dylib I received an issue email like the above. The app has supported Mac (Designed by iPad) so far. This time, this issue occurs after building in Xcode 16.0 / MacBook OS 14.6.1. The app being built supports at least iOS 14. We cannot uncheck it because we must support Mac (Designed by iPad) in the future. This issue
Hi, I already distributed private app for my company, but I stuck with the big problem that I cannot solve. I distributed private app through generate redeem link to the employee and the problem is how to generate link to update app directly ? I try all normal link but cannot link to private app. Some link alert Not available in your country but the country of the app is all the same. https://apps.apple.com/us/app/app-name/app-id itms-apps://itunes.apple.com/th/app/app-name/app-id Thank you for your help.