Hello I've released a production IPA to upload to TestFlight for internal testing. When we're trying to upload the IPA to TestFlight we're getting an ITMS-90165 error. while it was working fine a couple of days back Can anyone help me find out what this error means? Thank you.
Search results for
ITMS-90158
1,681 results found
Selecting any option will automatically load the page
Post
Replies
Boosts
Views
Activity
https://twitter.com/JI/status/1514043544897425408 Hi everyone, I found this tweet for ERROR ITMS-90165: Invalid Provisioning Profile Signature. issue while submitting to app store. Please try to create new distribution provisioning profile & use it.
Topic:
App Store Distribution & Marketing
SubTopic:
App Store Connect
Tags:
<main> DBG-X: parameter FilesToUpload = [metadata.xml, JS.ipa]<main> DBG-X: parameter MinimumFileSizeThresholdForCheckum = 104857600<main> ERROR: ERROR ITMS-90161: Invalid Provisioning Profile. The provisioning profile included in the bundle com.jschat.jschatapp [Payload/JS.app] is invalid. [Missing code-signing certificate]. A Distribution Provisioning profile should be used when submitting apps to the App Store. For more information, visit the iOS Developer Portal.<main> DBG-X: The error code is: 1102<main> INFO: Done performing authentication.<main> DBG-X: Returning 1First thanks to viewing my issue.I dont know why i'm facing this issue i have created the provisioning file according to the apple documentation.My app is done just to upload on app store.Please help me as soon as possible.I shall be very thankful to you.Thanks
Same here! No hope. Xcode Version 13.3.1 (13E500a) #ITM-90165 / ITM-90165
Topic:
App Store Distribution & Marketing
SubTopic:
App Store Connect
Tags:
Same issue on my side ITMS-90165: Invalid Provisioning Profile Signature - The provisioning profile included in the bundle 'xxx' cannot be used to submit apps to the iOS App Store until it has a valid signature from Apple. For more information, visit the iOS Developer Portal.
Topic:
App Store Distribution & Marketing
SubTopic:
App Store Connect
Tags:
I'm receiving the following errors and warning when uploading my archive to iTunes Connect via Xcode. There appears to be an issue with the embedded framework. I've run out of ideas on what exactly is causing the issue. Any ideas?ERROR ITMS-90087: “Unsupported Architectures. The executable for zulily.app/Frameworks/ChasePaymentech.framework contains unsupported architectures ‘[x86_64, i386]’.”ERROR ITMS-90209: “Invalid Segment Alignment. The app binary at ‘zulily.app/Frameworks/ChasePaymentech.framework/ChasePaymentech’ does not have proper segment alignment. Try rebuilding the app with the latest Xcode version.”ERROR ITMS-90125: “The binary is invalid. The encryption info in the LC_ENCRYPTION_INFO load command is either missing or invalid, or the binary is already encrypted. This binary does not seem to have been built with Apple’s linker.”WARNING ITMS-90080: “The executable ‘Payload/zulily.app/Frameworks/ChasePaymentech.framework’ is not a Position Independent Executable.
I've gone through every single framework / plugin / binary in the app bundle with otool -L and found nothing. What's annoying is how these emails about ITMS-90562: Invalid Bundle do NOT in fact tell us what's invalid in the bundle - if you (i.e. the processing server) are aware, why not just tell us in the same email? I've tried it with Xcode 13.2.1 as well and it still gets rejected. I have no idea what's going on as another one of our apps is submitting fine.
Topic:
App Store Distribution & Marketing
SubTopic:
App Store Connect
Tags:
I'm working on a multi-platform iOS and Mac app. When I try and Archive and Distribute to the App Store I run into this issue: ERROR ITMS-90259: Bad Bundle Executable. You must include a valid CFBundleExecutable key in your bundle's information property list file. I've verified that the Info.plist for the Mac target has a CFBundleExecutable So, far I've: Tried Xcode 12 & 13 Tried using App Transporter Used Xcode 13 RC and let that auto-generate the Info.plist Recreated the entire project in Xcode 13 I've tried everything I could find online - there's not much - and I can't get the upload to succeed. However, I was able to replicate the issue with an entirely empty project. No dependencies, no code, nothing. The project archives successfully, but the upload fails. Any help would be appreciated. I've spent two days on this already. An example project that fails: https://drive.google.com/file/d/1qUN5lHEWNyNHQV54fYPXMeRsuO-cpHqW/view?usp=sharing
Topic:
App Store Distribution & Marketing
SubTopic:
App Store Connect
Tags:
App Store Connect
Xcode
Beta
ITMS-90890: Missing recommended icon - The bundle does not contain an alternate app icon for iPhone / iPod Touch of exactly '120x120' pixels, in .png format for iOS versions I've provided icon_name@2x (in 120x120) and icon_name@3x (in 180x180) as alternate icons. These are located outside of the assets folder. I am able to switch the alternate icons without any issues and have been doing this since previous versions. Just recently, the warning is telling me that I'm missing something even if I already provided the icons. Is there something else that I'm missing?
Here's what you need as of 2022 if you're getting warnings like ITMS-90890, ITMS-90892: Filename Size (px) IconName@2x.png 120x120 IconName@3x.png 180x180 IconName@2x~ipad.png 152x152 IconName@3x~ipad.png 167x167 Note the lack of capitalization on ~ipad! Source: https://stackoverflow.com/a/70186649/702870
Topic:
App & System Services
SubTopic:
Hardware
Tags:
New apps uploaded to the App Store as of today (March 22, 2022) should no longer encounter the original error reported upon upload in relation to using Swift concurrency: ITMS-90562: Invalid Bundle - One or more dynamic libraries that are referenced by your app are not present in the dylib search path. If you were previously impacted, please upload a new version today. If you continue to receive this error message, please let us know through Feedback Assistant, and post the FB number here.
Topic:
App Store Distribution & Marketing
SubTopic:
App Store Connect
Tags:
I just started a gitlab project trying to cover the different use cases related to managing in-app purchases with iTMS Transporter. Maybe it's helpful: here's the link https://gitlab.com/ms152718212/manage-in-app-purchases-with-itmstransporter But as I said, it will take me a few more days and hours to finish it.
Topic:
App & System Services
SubTopic:
StoreKit
Tags:
You can use iTMS Transporter. There is a video from WWDC 2013 (session 306). I think there is also a video from 2012. https://help.apple.com/itc/transporteruserguide/en.lproj/static.html https://help.apple.com/asc/appsspec/en.lproj/static.html (note this has not yet been updated to remove the hosted content feature, which is going away at the end of this month). Note that a limit of 1000 IAPs applies in some situations; it is simpler to keep below that. If you must have more than 1000 you will need to do some operations in batches. Beware, this is not the easiest thing to use! Also beware, I think the number of people using it is probably quite small and I consider it at risk i.e. Apple might turn it off at any time. You're also likely to encounter bugs, e.g. the App Store Connect web interface probably isn't regularly tested with apps with >1000 IAPs. Good luck!
Topic:
App & System Services
SubTopic:
StoreKit
Tags:
Hello, My team is currently having an issue uploading our app to the AppStore because of the following issues: ITMS-90562: Invalid Bundle - Bitcode failed to compile for your watchOS binary because it includes assembly source code or inline assembly. To resolve this issue, rewrite the corresponding code in a higher-level language such as Objective-C or Swift and redeliver your app. ITMS-90562: Invalid Bundle - There's an issue with the app's bitcode compilation. Rebuild the app using the current public (GM) version of Xcode and upload it again. Firstly, we do not have a watchOS app at all. Our last release was successful when built on Xcode 11.6 and we're currently using Xcode 11.7. According to Apple, Xcode 12 isn't required until April of 2021, so I'm not sure what it's complaining about. Here's what we've tried. We created an AppStore build and ran it through the validator and that succeeded. It even uploads fine, but doesn't successfully process once uploaded. We created an Enterprise ve
Topic:
App Store Distribution & Marketing
SubTopic:
App Store Connect
Tags:
App Store Connect
iOS
App Binary
Exactly same issue here. Not only does it affect Ad Hoc distribution, but for normal App Store distribution, it also receives errors. ITMS-90562: Invalid Bundle - One or more dynamic libraries that are referenced by your app are not present in dylib search path. (this is incorrect error message). Unchecking Include Bitcode for iOS content can workaround the problem, but this cannot be applied to apps with Apple Watch applications. Detailed error log: ipatool failed with an exception: # /Applications/Xcode.app/Contents/Developer/usr/bin/ipatool:372:in `run' /Applications/Xcode.app/Contents/Developer/usr/bin/ipatool:2889:in `block in CompileOrStripBitcodeInBundle' /Applications/Xcode.app/Contents/Developer/usr/bin/ipatool:2828:in `each' /Applications/Xcode.app/Contents/Developer/usr/bin/ipatool:2828:in `CompileOrStripBitcodeInBundle' /Applications/Xcode.app/Contents/Developer/usr/bin/ipatool:2813:in `block in CompileOrStripBitcodeInBundle' /Applications/Xcode.app/Contents/Developer/usr/bin/ipatool:2812
Topic:
Programming Languages
SubTopic:
Swift
Tags: