Search results for

ITMS-90158

1,686 results found

Post

Replies

Boosts

Views

Activity

APP was got rejected with ITMS-90165: Invalid Provisioning Profile Signature
Hi all, I was having an issue which my APP was got rejected and I received an email said the following ITMS-90165: Invalid Provisioning Profile Signature. The provisioning profile included in the bundle 'app' (ios.app) cannot be used to submit apps to the iOS App Store until it has a valid signature from Apple. (Expired profile signing certificate.) However, I can see my certificate and profile are still valid till 2022 May from the developer portal. Can someone let me know why I encounter this issue please? I was able to submit an iOS APP back in 2022 Mar. Could anyone please advise what I need to do to resolve the current situation and how I can prevent the same case in ongoing please? Also, it will be great if anyone can let me know any limitation or standard of using the APPLE related certificate to do distribution and development.
1
0
708
Apr ’22
Build upload to TestFlight has been unsuccessful due to some error 'ITMS-90338: Non-public API usage'.
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.
3
0
829
Apr ’22
ITMS-90427
Does anyone know where this is wrong?We identified one or more issues with a recent delivery for your app, Press Voice 1.4.5 (15). Please correct the following issues, then upload again.ITMS-90427: Invalid Swift Support - The expected dylibs are missing from the app’s Framework location, such as /Payload/Press Voice.app/Frameworks.
3
0
3.6k
Apr ’22
Application Loader ERROR: ERROR ITMS-90161
<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
6
0
7.7k
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.
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.
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
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?
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