Search results for

“ITMS-90338”

1,703 results found

Post

Replies

Boosts

Views

Activity

ERROR ITMS-90087, ERROR ITMS-90209, ERROR ITMS-90125, WARNING ITMS-90080
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.
Topic: App Store Distribution & Marketing SubTopic: App Review Tags:
5
0
9.2k
Apr ’22
Reply to ITMS-90562: Invalid Bundle with Xcode 13.3 RC
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:
Mar ’22
Xcode 13 Beta: CFBundleExecutable Error on Upload
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:
2
0
1.4k
Mar ’22
Bundle does not contain an alternate app icon for iPhone / iPod Touch of exactly '120x120' pixels. I've provided the icons but still missing what seems to be the issue?
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?
Topic: App & System Services SubTopic: Hardware Tags:
7
0
11k
Apr ’22
Reply to Bundle does not contain an alternate app icon for iPhone / iPod Touch of exactly '120x120' pixels. I've provided the icons but still missing what seems to be the issue?
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:
Mar ’22
Reply to ITMS-90562: Invalid Bundle with Xcode 13.3 RC
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:
Mar ’22
Reply to App Store Connect API for in-app purchases
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:
Mar ’22
Reply to App Store Connect API for in-app purchases
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:
Mar ’22
ITMS-90562: Invalid Bundle - Bitcode failed to compile for your watchOS binary
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:
17
0
10k
Mar ’22
Reply to Unable to export for Ad Hoc or Development distribution with Xcode 13.3 RC
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:
Mar ’22
upload app to App Store failed and get error in signing code for my application vb from vbulletin
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
Topic: Code Signing SubTopic: General Tags:
1
0
1.1k
Mar ’22
error itms-90168 null when trying to archive a build (trying to upload build to testflight)
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.
Topic: App Store Distribution & Marketing SubTopic: App Store Connect Tags:
2
0
2k
Mar ’22
Reply to Can't upload to AppStore - Invalid Provisioning Signature
Same here! No hope. Xcode Version 13.3.1 (13E500a) #ITM-90165 / ITM-90165
Topic: App Store Distribution & Marketing SubTopic: App Store Connect Tags:
Replies
Boosts
Views
Activity
Apr ’22
Reply to Can't upload to AppStore - Invalid Provisioning Signature
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:
Replies
Boosts
Views
Activity
Apr ’22
ERROR ITMS-90087, ERROR ITMS-90209, ERROR ITMS-90125, WARNING ITMS-90080
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.
Topic: App Store Distribution & Marketing SubTopic: App Review Tags:
Replies
5
Boosts
0
Views
9.2k
Activity
Apr ’22
Reply to ITMS-90562: Invalid Bundle with Xcode 13.3 RC
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:
Replies
Boosts
Views
Activity
Mar ’22
Xcode 13 Beta: CFBundleExecutable Error on Upload
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:
Replies
2
Boosts
0
Views
1.4k
Activity
Mar ’22
Bundle does not contain an alternate app icon for iPhone / iPod Touch of exactly '120x120' pixels. I've provided the icons but still missing what seems to be the issue?
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?
Topic: App & System Services SubTopic: Hardware Tags:
Replies
7
Boosts
0
Views
11k
Activity
Apr ’22
Reply to Bundle does not contain an alternate app icon for iPhone / iPod Touch of exactly '120x120' pixels. I've provided the icons but still missing what seems to be the issue?
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:
Replies
Boosts
Views
Activity
Mar ’22
Reply to ITMS-90562: Invalid Bundle with Xcode 13.3 RC
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:
Replies
Boosts
Views
Activity
Mar ’22
Reply to App Store Connect API for in-app purchases
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:
Replies
Boosts
Views
Activity
Mar ’22
Reply to App Store Connect API for in-app purchases
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:
Replies
Boosts
Views
Activity
Mar ’22
ITMS-90562: Invalid Bundle - Bitcode failed to compile for your watchOS binary
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:
Replies
17
Boosts
0
Views
10k
Activity
Mar ’22
Reply to Unable to export for Ad Hoc or Development distribution with Xcode 13.3 RC
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:
Replies
Boosts
Views
Activity
Mar ’22
upload app to App Store failed and get error in signing code for my application vb from vbulletin
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
Topic: Code Signing SubTopic: General Tags:
Replies
1
Boosts
0
Views
1.1k
Activity
Mar ’22
error itms-90168 null when trying to archive a build (trying to upload build to testflight)
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.
Topic: App Store Distribution & Marketing SubTopic: App Store Connect Tags:
Replies
2
Boosts
0
Views
2k
Activity
Mar ’22
open App Store app from watchOS app
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) }
Topic: App Store Distribution & Marketing SubTopic: General Tags:
Replies
1
Boosts
0
Views
574
Activity
Mar ’22