I've added NFC support for my app. So, my UIRequiredDeviceCapabilities were extended from armv7 to armv7 nfc. This means I've prevented this application from running on devices supported by previous versions. Now I've received a message from Apple: ITMS-90109: This bundle is invalid - The key UIRequiredDeviceCapabilities in the Info.plist may not contain values that would prevent this application from running on devices that were supported by previous versions. What is the right way to add new functions?
Search results for
ITMS-90158
1,681 results found
Selecting any option will automatically load the page
Post
Replies
Boosts
Views
Activity
We got this message after publishing our app to test flight: ITMS-90725: SDK Version Issue - This app was built with the iOS 16.0 SDK. All iOS apps submitted to the App Store must be built with the iOS 15 SDK or later, included in Xcode 13 or later. I'm no math genius but am pretty sure that 16 is greater than 15. Why did I get this messages? Can I ignore it? will it prevent my app from being able to be submitted to the app store?
ITMS-90338: Non-public API usage - The app contains one or more corrupted binaries. Rebuild the app and resubmit.. 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/ They haven't mentioned Non-public APIs which we have used how can we resolve it? How can we resolve with this information?
Topic:
App Store Distribution & Marketing
SubTopic:
App Store Connect
Tags:
iOS
App Store Connect
App Submission
Do any Apple tools exist that currently enable Bulk IAP management? I have been trying to use the iTMSTransporter, and the following command does respond appropriately, but the metadata.xml that is returned is incredibly bare, and does not include any of the 50+ IAPs we have in our app. ./Transporter.app/Contents/itms/bin/iTMSTransporter -m lookupMetadata -u *** -p *** -destination ~/Desktop/IAP -apple_id *** -app_platform ios -subitemtype InAppPurchase
Topic:
App Store Distribution & Marketing
SubTopic:
App Store Connect
Tags:
In-App Purchase
App Store Connect
After using iOS16's new feature AppIntents, AppStore review is failed: ITMS-90426: Invalid Swift Support - The SwiftSupport folder is missing. Rebuild your app using the current public (GM) version of Xcode and resubmit it. I tried all methods in internet, but they all not work. Such as: I'm using the public version of Xcode I'm not using Ad hoc cert or .pp file I tried archive manually without using fastlane I tried change the Always Embed Swift Standard Libraries The only changes is iOS16's AppIntents. Before i use AppIntent, it works fine. After i use AppIntent, it failed. Only one commit between 2 .ipa. Can anyone help me? Many thanks.
I have 3 non universal apps and i get this:ERROR ITMS-90101: This bundle does not support one or more of the devices supported by the previous app version. Your app update must continue to support all devices previously supported. You declare supported devices in Xcode with the Targeted Device Family build setting.App app versions on the app store are NOT universal and iphone only. / except the latest released build.Someone NOT me has changed the device support from iphone only to universal and now im stuck.There is an faq: https://developer.apple.com/library/content/qa/qa1623/_index.htmlChoices 1 and 3 are not an option for me.Choice 2 is not working : i have changed min. iOS from 9.0 to 9.1 and i get the same error.Customer satisfaction should be the main goal!! Or not?I need help from a apple engineer to fix this.Thanks
We are trying to upload new build for our already existing app to appstore, with a build script to embed framework(Which is just copying from build directory to MyApp.app/Frameworks). Everything builds and works fine in my local machine. But getting this error while uploading to appstore. ITMS-90432: Invalid Swift Support - The file MyApp.app/Frameworks/Framework1.framework, MyApp.app/Frameworks/Framework2.framework doesn’t have the correct file type for this location. Ensure you’re using the correct file, rebuild your app using the current public (GM) version of Xcode, and resubmit it. We are copying to the correct directory, but still getting the above error while uploading. Are we missing the obvious here?
Topic:
App Store Distribution & Marketing
SubTopic:
App Store Connect
Tags:
iOS
App Store Connect
Xcode
Frameworks
I submitted a test package and got the following email: ITMS-90345: Metadata/Info.plist Mismatch - The value for bundle_identifier in the metadata.xml file does not match the value for CFBundleIdentifier in test [net.neolib.test.pkg/Payload/test.app]. I really don't have any idea what's wrong. It's a simple (almost blank) app with nearly no modification (except linked with a dylib). What is the metadata.xml? I cannot find it in my test project.
I got this when uploading to testFlight ITMS-90725: SDK Version Issue - This app was built with the iOS 15.5 SDK. Starting April 2023, all iOS apps submitted to the App Store must be built with the iOS 16.1 SDK or later, included in Xcode 14.1 or later. How can I solve this?
Topic:
App Store Distribution & Marketing
SubTopic:
App Store Connect
Tags:
Hi, I'm getting this error while pushing my app for testflight Dear Developer, We identified one or more issues with a recent delivery for your app, MyAppName 1.4.24 (1). Please correct the following issues, then upload again. ITMS-90129: The bundle uses a bundle name or display name that is already taken. Best regards, The App Store Team I've been abled to push version 1.4.16, 1.4.17, 1.4.19, 1.4.20 successfully before with no issues, and I'm sure I'm still holding the bundle identifier but yet this error is still appearing everytime I try to upload a new build. I'm wondering if anyone else having the same problem?
Topic:
App Store Distribution & Marketing
SubTopic:
App Store Connect
Tags:
App Store Connect
Bundle ID
TestFlight
We got the same message. and now planning to upgrade. app store message was as following, Dear Developer, We identified one or more issues with a recent delivery for your app, React Native App 1.0.0 (1). Your delivery was successful, but you may wish to correct the following issues in your next delivery: ITMS-90725: SDK Version Issue - This app was built with the iOS 16.0 SDK. Starting April 2023, all iOS apps submitted to the App Store must be built with the iOS 16.1 SDK or later, included in Xcode 14.1 or later. After you’ve corrected the issues, you can upload a new binary to App Store Connect. Best regards, The App Store Team
Topic:
App Store Distribution & Marketing
SubTopic:
TestFlight
Tags:
Resolved for me. Message now shows correct version numbers and makes logical sense ITMS-90725: SDK Version Issue - This app was built with the iOS 16.0 SDK. Starting April 2023, all iOS apps submitted to the App Store must be built with the iOS 16.1 SDK or later, included in Xcode 14.1 or later.
Topic:
App Store Distribution & Marketing
SubTopic:
TestFlight
Tags:
Hello, I'm trying to submit an app to apple connect that is build outside of xcode but I'm getting this email saying the files have an invalid signature. I'm doing a step wrong or maybe using the wrong signature but not sure what is supposed to be the way to do it. The app is written with python and pyside, and packaged with pyinstaller. In the pyinstaller .spec file I set the codesign_identity and entitlements_file and also fill some things to the info_plist (CFBundleVersion, LSApplicationCategoryType, etc). This results in a .app file, which then I run a command on it: productbuild --component path/to/file.app /Applications path/to/file.pkg --sign And then push with: xcrun altool --upload-app path/to/file.pkg --type macos -u -p I'm able to upload but then I get the email with the signature error (ITMS-90238: Invalid Signature). Are these steps ok, or something else is needed?
Topic:
App Store Distribution & Marketing
SubTopic:
App Store Connect
Tags:
App Store Connect
Mac App Store
App Submission
I received an email with the following message from Apple: ITMS-90725: SDK Version Issue - This app was built with the iOS 15.5 SDK. All iOS apps submitted to the App Store must be built with the iOS 15 SDK or later, included in Xcode 13 or later. Well, what's the problem Apple? I used 15.5. That's later than 15!
We got the same message. For context, our app was built on Xcode 14.0.1, which doesn't seem to know about iOS > 16.0. We're planning on upgrading our build machines to Xcode 14.2 in the next few days (before the April deadline), which lists iOS 16.1 and 16.2 as valid minimum iOS versions. I think KCO_S has the right idea; it's a legitimate warning with unfortunate typos, which should read: ITMS-90725: SDK Version Issue - This app was built with the iOS 16.0 SDK. All iOS apps submitted to the App Store must be built with the iOS 16.1 SDK or later, included in Xcode 14.1 or later.
Topic:
App Store Distribution & Marketing
SubTopic:
TestFlight
Tags: