Search results for

ITMS-90158

1,681 results found

Post

Replies

Boosts

Views

Activity

Reply to ERROR ITMS-90165: Invalid provisioning profile signature.
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
Oct ’24
ERROR ITMS-90165: Invalid provisioning profile signature.
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?
8
0
1.4k
Oct ’24
Build not showing up after archive successfully uploaded app
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)
2
0
805
Oct ’24
Reply to iTMSTransporter -m upload fail
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
Oct ’24
Reply to iTMSTransporter -m upload fail
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
Oct ’24
Reply to iTMSTransporter -m upload fail
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.
Oct ’24
Reply to iTMSTransporter -m upload fail
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.
Oct ’24
Apple silicon Macs support issue
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
12
0
6.6k
Oct ’24
how to generate link to update private app ?
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.
0
0
549
Oct ’24
Reply to Build for Breathegolf does not appear in the Test Flight though after distributed successfully from Xcode
We have distributed the build for Breathegolf app successfully from XCocde, but it did not appear in the Test Flight section of the Breathegolf app. We have also created an internal testing group for the app and added a tester in the group. In the Test flight section, the version 1.0.0 appeared for some times but after after refreshing, it showed No Builds. We have received a mail from Apple that Action needed: The uploaded build for Breathegolf has one or more issues. In the mail, under the heading: ITMS-90078: Missing potentially required entitlement, apple said that in our app, library that's included in the app, uses Apple Push Notification service (APNs) registration APIs, but the APS Environment Entitlement isn't included in the app signature's entitlements. But there is no API or package is used for push notification. The app is developed using flutter. Packages we have used are: cupertino_icons: ^1.0.2 google_fonts: ^5.1.0 font_awesome_flutter: ^10.7.0 http: ^1.1.0 date_time_picker: ^2.1.0 fl
Oct ’24
ITMS-90426: Invalid Swift Support when uploading VisionOS app to Appstore Connect with dylib
I'm trying to upload a build to app store connect. It's a build from a Unity project with the polyspatial SDK, and I also need to include a c++ library, which I've added as a dylib signed with the same provisioning profile as the app. The profile is an Apple Distribution profile created from an enterprise account. It succesfully uploads to Appstore connect, but fails with the following error message: ITMS-90426: Invalid Swift Support - The SwiftSupport folder is missing. Rebuild your app using the current public (GM) version of Xcode and resubmit it. This is unhelpful as I'm using a current version of Xcode. I've read that it's a provisioning issue, but I'm using the provisioning profile for apple distribution on an enterprise account, not an ad hoc profile. I've tried manually adding the SwiftSupport folder from the Xcode toolchain to the ipa/xarchive, resign and upload with Transporter, but that doesn't work. After spending a day trying to troubleshoot this, I'm at a loss. Any help with this is muc
2
0
1.7k
Oct ’24
ITMS-90076: Potential Loss of Keychain Access
We have transferred our app from App Store Connect account to another. Transfer process was smooth and we we were able to move our app to new App Store account While uploading the new build for our app using the new account we received the below email. Can someone shed some lights on this and how can we make user to not to logout. ITMS-90076: Potential Loss of Keychain Access - The previous version of software has an application-identifier value of ['94B63VZT32.com.prasthana.tenmates'] and the new version of software being submitted has an application-identifier of ['G3M3U47GBZ.com.prasthana.tenmates']. This will result in a loss of keychain access.
1
0
649
Sep ’24
ITMS-91093
Hi, I'm encountering an issue when trying to upload a build to App Store Connect. I'm receiving an 'Invalid Binary' error with the following message: ITMS-91093: Invalid Binary - The app contains a binary [path to a zip file] that cannot be processed. The error appears to be linked to a folder containing zip files that is referenced in the 'Build Phases' under the 'Copy Bundle Resources' section. Everything was working fine until a few days ago.
0
0
585
Sep ’24