Search results for

ITMS-90158

1,681 results found

Post

Replies

Boosts

Views

Activity

XCode 11.3 (11C29) unable to submit an iOS 12.1 app (itms-90725)
Since Saturday Dec 28th 2019 (about 10am PST) I am no longer able to submit a build for testing in TestFlight, the error I receive is:ERROR ITMS-90725: SDK Version Issue. This app was built with the iOS SDK. All iOS apps submitted to the App Store must be built with the iOS 11 SDK or later, included in Xcode 9 or later. Further, starting March 2019, all iOS apps submitted to the App Store must be built with the iOS 12.1 SDK or later, included in Xcode 10.1 or later.The steps I take are, Open Xcode, Product -> Archive and then just click through the process to auto-sign etc. and upload. I am running Xcode 11.3 and tried building for iOS 12.0 / 12.1 & 13.2 all result in the same error since Saturday 12/28 10am PST.I've gone back in our git history and synced to the code last submitted on 12/26 and bumped the build number and get the same error, I deleted the entire project folder and cloned the repository again to no avail, rebooted my system still no dice.So I did another test, ran 'Validate Ap
5
0
1.2k
Dec ’19
ERROR ITMS-90189: "Redundant Binary Upload.", but the binary is not showing up in TestFlight.
Hi all, I am encountering a problem where I am attempting to upload an IPA to TestFlight using fastlane. In my first attempt, I received no errors. However, even after hours of waiting, there is still no binary on TestFlight for that version and build number. In my second and following attempts, I get this error: ERROR ITMS-90189: Redundant Binary Upload. You've already uploaded a build with build number '18445' for version number '3.66.0'. Make sure you increment the build string before you upload your app to App Store Connect. Learn more in Xcode Help (http://help.apple.com/xcode/mac/current/#/devba7f53ad4). To clarify again, if I go into TestFlight, there is no version 3.66.0. The build number is supposed to automatically increment, as it does previously. So there are multiple problems here for me. Binary not showing up in TestFlight TestFlight thinks the binary is there, so I'm not able to automatically increment build number.
1
0
1.7k
Jun ’22
iOS 16.0 (20A5339d) itms-service cant work
download succeeded, but installation failed: Aug 12 17:28:48 taketekiiPhone installd(MobileSystemServices)[344] : 0x16f213000 -[MIInstaller _bundleInDirectory:withBundleID:error:]_block_invoke: Ignoring non-target app bundle Dungeon.app with bundle ID com.rscube.dungeon.dev while exploring /var/installd/Library/Caches/com.apple.mobile.installd.staging/temp.sHH8DP/extracted/Payload Aug 12 17:28:48 taketekiiPhone installd(MobileSystemServices)[344] : 0x16f213000 -[MIInstaller _bundleInDirectory:withBundleID:error:]: 450: The item being installed did not contain an app with bundle ID com.rscube.dungon.dev, but it did contain app(s) with bundle ID(s): {( com.rscube.dungeon.dev )}
1
0
957
Aug ’22
ITMS-90809: Deprecated API Usage , but there is no UIWebView...
I am lost now with apple's warningITMS-90809: Deprecated API Usagesaying that the submitted app contains UIWebView.I have removed all UIWebView in the source code, going as far as even removing it in comments. Search function in Xcode and in Finder show no result.All pods have been brought to the latest version.Running nm myapp | grep UIWeb for framework in Frameworks/*.framework; do fname=$(basename $framework .framework) echo $fname nm $framework/$fname | grep UIWeb donenicely lists all frameworks as being clean.So where else could a UIWebView be hiding?
2
0
1.4k
Apr ’20
Testflight Validate ERROR ITMS-90778 NDEF is disallowed
I am trying to upload my app to TestFlight, which using CoreNFCUnfortunately, I got the error message on Testflight Validate part in (SDK version 13 and 13.1).I already tried [this]: Xcode 11 beta can't upload app to TestFlightbut it will Lose NDEF function [this]: https://stackoverflow.com/a/58128365/5588637Error messages: Invalid entitlement for core nfc framework The sdk version 13.0 and min OS version 13.0 are not compatible for the entitlement 'com. Apple developer nfc. Readersession formats because NDEF is disallowedI already choose target iOS 13.1 in XCode, but also have this error.image 1: https://user-images.githubusercontent.com/19588517/65782718-dceb9180-e180-11e9-88d9-d21c2dcb5701.pngimage 2: https://user-images.githubusercontent.com/19588517/65782843-263be100-e181-11e9-8639-48fb64c5e08d.png
16
0
14k
Sep ’19
xCode - ITMS-90111: Unsupported SDK or Xcode version
When I try to upload an app to the AppStore, I receive following feedback: I had Xcode 16 with visionOS installed. Because of the feedback, I switched back to Xcode 15.3 with visionOs 1.0. I archived it again and tried to upload the app again. But I still receive the same feedback. I also tried https://stackoverflow.com/questions/56518791/app-store-refuses-my-update-after-installing-xcode-11-beta-with-keeping-xcode-10/56623421#56623421, but it seems that there is no such property for visionOS in the info.plist I do not have any further ideas...
2
0
1.1k
Jun ’24
ITMS-90682: can't contain 16-bit or P3 assets if the app supports iOS 8 or earlier
Hi, I just started seeing this error (without change in assets) in a testflight submission (we have iOS10-only code) - this is the full message (from XCode8)ERROR ITMS-906832: Invalid Bundle. The aseet catalog at 'Paylod/XXXX/Assets.car' can't contain 16-but or P3 assets if the app supports iOS 8 or earlierI can submit by disabling iOS8 but need to know if this is a temporary error, or something wrong in our assets.Thank you
117
0
44k
Aug ’16
WidgetKit Extension Causing "ITMS-90078: Missing Push Notification Entitlement"
Hello! We have a pretty robust codebase that has APNs enabled for the base app. We recently added a WidgetKit extension to replace our old widget from pre-iOS 14. Our working provisioning profiles (before this addition) were generally as such: Our main target has APNs enabled and configured (and has for ~6 years), testing push notifications on our previous release works as intended Our old widget does not have APNs enabled, since it doesn't support push notifications What we added was: 3. A new iOS14+ widget extension without APNs enabled Ever since we added the third provisioning profile, we've received the warning: ITMS-90078: Missing Push Notification Entitlement - Your app appears to register with the Apple Push Notification service, but the app signature's entitlements do not include the 'aps-environment' entitlement. If your app uses the Apple Push Notification service, make sure your App ID is enabled for Push Notification in the Provisioning Portal, and resubmit after signing your app with a
0
0
2.1k
Sep ’22