ITMS-90338

1,572 results found

Post

Replies

Boosts

Views

Activity

ITMS-90426: Invalid Swift Support
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.
1
0
1.2k
Mar ’23
Major issue on upload new version
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
2
0
15k
Dec ’17
ITMS-90432: Issue while uploading app to appstore.
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?
1
0
615
Apr ’23
CFBundleIdentifier not match?
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.
2
0
712
Apr ’23
Getting The bundle uses a bundle name or display name that is already taken ERROR while pushing for Testflight
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?
1
0
2.5k
Sep ’22
Reply to SDK Version Issue message that defies basic math
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
Mar ’23
Invalid Signature Issue
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?
4
0
1.2k
Mar ’23
Reply to SDK Version Issue message that defies basic math
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.
Mar ’23
Reply to ITMS-90725: SDK Version Issue
It seems that the warning message is not up to date. I think It should be: 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 16.1 SDK or later, included in Xcode 14.1 or later. (cf https://developer.apple.com/ios/submit/) see also https://stackoverflow.com/questions/75772955/itms-90725-useless-error-message-since-it-contradicts-itself-apple-upload/75788891#75788891 You should be fine until April. This is just a warning for now.
Mar ’23
Sticker App converted to Standard App (ITMS-90639 ERROR)
HiSorry, my english is bad!A few weeks ago, I sent an app of stickers to AppStore. Now I'm trying to do an update making it a standard app with an extension of stickers.When I try to upload, App Loader displays the following message:ITMS-90639 ERROR: Invalid Binary The value of LSApplicationLaunchProhibited in Payload / PicMessage.app / Info.plist can not change after your app has been released..I have tried many things, such as recreating the Xcode project from scratch. Also I put LSApplicationLaunchProhibited true (and then receive other types of errors). Nothing solves my problem.How can I solve this problem?Regards,Angel
6
0
2.5k
Oct ’16
Apple App Store Submission rejected with code ITMS-90748 and no other information.
I built and submitted a react-native app and the app was sent to Apple for submission. I received an email back 5 minutes later that reads Dear Developer, We identified one or more issues with a recent delivery for your app, TYPSA REGISTRO DE JORNADA 1.0.2 (1.4). Please correct the following issues, then upload again. ITMS-90748: ${message} Best regards, The App Store Team The ${message} looks like a template placeholder that isn't populated and thus there is no information indicating what might be wrong. I google searched for the specific error code and could not find anything. What does this code mean and why is my app submission failing?
1
0
647
Jan ’23
Upload to the store Error
ERROR ITMS-90347: Bad bundle identifier. The bundle identifier 'com.legacylouisvillellc.legacylouisville' of the application extension Legacy Louisville.app/PlugIns/OneSignalNotificationServiceExtension.appex should start with the application's bundle identifier 'com.legacylouisvillellc.legacylouisville' and not contain more than one period “.” after the application's bundle ID. ERROR ITMS-90685: CFBundleIdentifier Collision. There is more than one bundle with the CFBundleIdentifier value 'com.legacylouisvillellc.legacylouisville' under the iOS application 'Legacy Louisville.app'. Hello, each time I am trying to upload this to the App Store for submission, I can't avoid these two error codes. Can anyone assist me? Thank you so much... Dave
3
0
2.7k
Aug ’21