Search results for

ITMS-90158

1,681 results found

Post

Replies

Boosts

Views

Activity

Which field does 'ITMS-90814: Missing SDK Version' relate to? (I have DTSDK* fields set already)
Hi, uploading the latest build of my app, I got the error 'ITMS-90814: Missing SDK Version' for my watch extension Now I do have the fields DTSDKBuild & DTSDKName so im confused as to what field this pertains to I submitted with XCode 11.6 last week and it worked fine and today a 11.6 submit fails :) Thanks
1
0
817
Sep ’20
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
iOS ITMS-90013: Corrupt Image File image file 'AppIcon60x60@2x.png
After uploading a new iOS build, we received an error message via email from Apple stating: ITMS-90013: Corrupt Image File - The image file AppIcon60x60 2x.png appears to be corrupt. Strangely, we don't have any image file with that name in our project. It seems to be a build processing error on Apple's side. While I've seen similar issues reported for Apple TV in the past, this is happening with our iOS build. Has anyone discovered a workaround? I've uploaded another app build and haven't encountered any errors.
4
0
2.2k
May ’24
Pkg installation package uploaded to macstore email prompt ITMS-90296
Hello! I encountered an issue while packaging and uploading the project to the Mac store. I received an email stating: ITMS-90296: App Sandbox not enabled - The following executors must include the 'com. apple. security. app sandbox' entitlement with a Boolean value of true in the entitlement property list: [[com. electron. iflyrecclient. pkg/Payload/iFlytek Listen. app/Contents/MacOS/iFlytek Listen]] Refer to App Sandbox page at https://developer.apple.com/documentation/security/app_sandbox for more information on sandboxing your app. Though you are not required to fix the following issues, we wanted to make you aware of them: ITMS-90886: 'Cannot be used with TestFlight because the signature for the bundle at' iFlytek hears. app 'is missing an application identifier but has an application identifier in the provisioning profile for the bundle.' Bundles with application identifiers in the provisioning profile are expected to have the same identifier signed into the bundle in order to be eligi
18
0
1.7k
Nov ’24
ITMS-90111 uploading to App Store with Xcode 10.1 (no betas!)
Hello!I'm getting the ITMS-90111 rejection when I submit to the app store. This particular app requires that I use Xcode 10.1, so that's what I'm using.I submitted Monday without issue, but today it's an issue.There are no beta Xcodes installed on the machine. Here's the full text of the rejection email, but wiht name and versions removed:Dear Developer,We identified one or more issues with a recent submission for App Store review for your app, XXXXXXXX V.V.V (B.B.B.B). Please correct the following issues, then upload again.ITMS-90111: Invalid Toolchain - Your app was built with a beta version of Xcode or SDK. Apps submitted to the App Store must be built with the GM version of Xcode 9 and the SDK for iOS 11, tvOS 11, watchOS 4, or macOS 10.13 or later.Best regards,The App Store Team
1
0
1.3k
Jun ’19
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
ITMS - 90455 Cannot see minimumOSversion in info.plist
Good Day,Please observe the above images, I got an error after the upload and from the previos forums I saw in the feed that I have to change the minimum watchkit OS into 2.0; however, I cannot see it from the watchkit info.plist.Please advise, all the help will be deeply appreciated because the deadline for this project is long overdue because of WatchOS version upgrade.Respectfully,johncban
0
0
143
Jan ’16
Xcode - ITMS errors (90022, 90023, 90704)
Iam trying to upload my app but I get the error codes 90022, 90023 and 90704. App icons are on the assets and all necessary keys are referenced on the info.plist file. You can check them here : Info.plist Assests Errors Maybe I'm missing a key value on the info.plist file or I need to erase like a cache or derived data folder. Thanks a lot.
0
0
371
Jul ’21
Reply to Two errors -- binary not optimized for iphone 5 (error 90096) and invalid code signing (error 90163) when submitting to iTunes
The ERROR ITMS- 90096: “Your binary is not optimized for iPhone 5 ……” is SOLVED! I had my splash images in a folder. Once I took them out of the folder and put them in the same directory as the project I was didn't receive the error anymore. The problem for the ERROR ITMS- 90163: “Invalid Code Signing Entitlements error was that a development AND production provisioning profile was using the same App ID. Once I created and paired a separate app ID for the development and production provisioning profile the problem was solved. PROBLEM SOLVED.
Feb ’16
ERROR ITMS-90564 Unsupported UIRequiredDeviceCapabilities value.
Get this error when attempting to submit to iTunesConnect: The Info.plist value for UIRequiredDeviceCapabilities contains an unsupported value 'watch-companion.'I have an iPhone app targeting iOS 8.2 with a watchOS 1 target (not targeting watch0S 2). I recently updated to XCode 7, and in doing so it asked me whether I wanted to upgrade the build phase of my project to watchOS 2 (can't remember exact wording). I'd read on the watchOS 2 transition guide that watchOS 1 apps will continue to run on watchOS 2 as usual (extension on phone, app on watch) so thought this would be ok.The 'watch-companion' value was in my plist before the 'build phase upgrade'. Any ideas as to what might be going wrong?
0
0
231
Sep ’15
ERROR ITMS-90085: No architectures in the binary.
The app runs fine on the device and simulator and we are able to build an archive without any issues. The issue is when we want to upload the build to the app store using Xcode 12.5.1, we get the following error: App Store Connect Operation Error No architectures in the binary. Lipo failed to detect any architectures in the bundle executable. Stackoverflow Link
1
0
2k
Jul ’21
Can't upload new update(ITMS-90109)
Hello. I developed an Unity app for iPhone and iPad, but uploaded only iPhone version. After a while of uploading new updates I can't upload new version of my App with iPad comparability. I have tried to add to graphics API Metal and OpenGLES3, but since start of development I used OpenGLES2 only. Both variants (using OpenGLES2 only or three of kind) return same issue as above.
0
0
492
Oct ’20
ITMS-90338 over LLVM container Usage
We use some of LLVM's containers in our code...llvm/ADT/SmallVector.h for example. When trying to submit our app to the App Store, it gets rejected with:ITMS-90338: Non-public API usage - The app references non-public symbols in X-Plane: __ZN4llvm24DisableABIBreakingChecksE. 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. If so, they must be removed. For further information, visit the Technical Support Information at http://developer.apple.com/support/technical/What gives, Apple? Are we not allowed to use open source code in our app? 😕Is there a way around this without having to search/replace every symbol that Apple's validator finds?
2
0
1.3k
Aug ’19