When I submitted to the MacOS Apple Store, it was rejected, and the following error was prompted, what should I do (I used a third-party build and signature, and did not use XCode) Dear Developer,We identified one or more issues with a recent delivery for your app, CollDesk 1.0.0 (1.0.0). Please correct the following issues, then upload again.ITMS-90332: Invalid Symbolic Link - The symbolic link 'com.colltech.desk.pkg/Payload/CollDesk.app/Contents/Frameworks/QtPrintSupport.framework/Headers' resolves to an invalid location. Make sure that the symbolic link does not resolve to itself, and that the location exists and is contained within the app bundle.ITMS-90332: Invalid Symbolic Link - The symbolic link 'com.colltech.desk.pkg/Payload/CollDesk.app/Contents/Frameworks/QtGui.framework/Headers' resolves to an invalid location. Make sure that the symbolic link does not resolve to itself, and that the location exists and is contained within the app bundle.ITMS-90332: Invalid Symbolic Link - The symbolic link 'com.c
ITMS-90338
1,572 results found
Post
Replies
Boosts
Views
Activity
I am trying to upload a new build of my app from the new Xcode 15.0.1 but it keeps failing with the below error: ITMS-90428: Invalid Swift Support - The files libswiftMetal.dylib, libswiftCoreGraphics.dylib, libswiftCoreLocation.dylib, libswiftObjectiveC.dylib, libswiftCoreAudio.dylib, libswiftos.dylib, libswiftDarwin.dylib, libswiftsimd.dylib, libswiftFoundation.dylib, libswiftCoreImage.dylib, libswiftQuartzCore.dylib, libswiftNetwork.dylib, libswiftUIKit.dylib, libswiftCoreFoundation.dylib, libswiftCoreMedia.dylib, libswiftCore.dylib, libswiftDispatch.dylib, libswiftAVFoundation.dylib don’t match /Payload/goodville.app/Frameworks/libswiftMetal.dylib, /Payload/goodville.app/Frameworks/libswiftCoreGraphics.dylib, /Payload/goodville.app/Frameworks/libswiftCoreLocation.dylib, /Payload/goodville.app/Frameworks/libswiftObjectiveC.dylib, /Payload/goodville.app/Frameworks/libswiftCoreAudio.dylib, /Payload/goodville.app/Frameworks/libswiftos.dylib, /Payload/goodville.app/Frameworks/libswiftDarwin.dylib, /Pa
I have the similar situation on my mac-mini now (Feb, 2024, Sonoma 14.3.1). I have several records for testflight in my keychain. And old records work well. But a new record (I created it today) doesn't work. I have these messages: dmitriy@Mini-Dmitriy IPA % xcrun altool --upload-app --type ios --file app.ipa --username dmitriy@.com --password @keychain:TESTFLIGHT_PROD --verbose 2024-02-24 17:16:24.810 Starting altool... 2024-02-24 17:16:24.813 Initializing bundle from: /Applications/Xcode.app/Contents/SharedFrameworks/ContentDeliveryServices.framework/Versions/A/Frameworks/AppStoreService.framework 2024-02-24 17:16:24.819 Will look for transporter at executable bundle relative path: /Applications/Xcode.app/Contents/SharedFrameworks/ContentDeliveryServices.framework/itms/bin/iTMSTransporter 2024-02-24 17:16:24.819 Looking for Transporter at path: /Applications/Xcode.app/Contents/SharedFrameworks/ContentDeliveryServices.framework/itms/bin/iTMSTransporter 2024-02-24 17:16:24.819 Looking for Tr
I'm testing the tvOS version of the development app (swiftUI), and I need to add the Intents Extension to the target to support Siri intents (INPlayMediaIntent) to play music, this is already working fine in the iOS version of the project and submitted for testing, when I compile and submit Go to App Store Connect, and then there is the following error in the feedback email: ITMS-90898: Invalid Mach-O entry point - Please make sure the build system passes “-e _NSExtensionMain” to the linker for the “MusicPlayer tvOS.app/PlugIns/TVSiriControlAudioExtension.appex” extension bundle, or the extension will not function. My project has Siri enabled, but I don't know what to do now. I tried to delete and re-create the Intents Extension without making any changes to the file, and submitted it directly to App Store Connect, but still prompted this error. Headache
Hello, Im currently having signing issues submitting my Swift macOS app to App Store Connect. After submitting it using Xcode I receive an e-mail with these issues: ITMS-90238: Invalid Signature - The main app bundle CodeMenu at path CodeMenu.app has following signing error(s): nested code is modified or invalid . Refer to the Code Signing and Application Sandboxing Guide at http://developer.apple.com/library/mac/#documentation/Security/Conceptual/CodeSigningGuide/AboutCS/AboutCS.html and Technical Note 2206 at https://developer.apple.com/library/mac/technotes/tn2206/_index.html for more information. ITMS-90238: Invalid Signature - The nested app bundle CodeMirror-SwiftUI at path CodeMenu.app/Contents/Frameworks/CodeMirror-SwiftUI.framework has following signing error(s): valid on disk /Volumes/workspace/app_data/SWValidationService/mz_15562079435119469448dir/mz_7860448159412669971dir/id.thedev.marcin.CodeMenu.pkg/Payload/CodeMenu.app/Contents/Frameworks/CodeMirror-SwiftUI.framework/Versions
In our latest two pushes to AppStore Connect, we've been getting the following message, where we hadn't previously: Dear Developer, We identified one or more issues with a recent delivery for your app, XYZ 1.2.3 (123). Your delivery was successful, but you may wish to correct the following issues in your next delivery: ITMS-90683: Missing purpose string in Info.plist - Your app’s code references one or more APIs that access sensitive user data, or the app has one or more entitlements that permit such access. The Info.plist file for the “xyz.app” bundle should contain a NSLocationAlwaysAndWhenInUseUsageDescription key with a user-facing purpose string explaining clearly and completely why your app needs the data. If you’re using external libraries or SDKs, they may reference APIs that require a purpose string. While your app might not use these APIs, a purpose string is still required. Oddly though, we've not really made any changes to our codebase that should trigger this. Just wondering if others ar
We received this message after uploading IPA to App Store Connect: Dear Developer, We identified one or more issues with a recent delivery for your app, **** 2.4.1 (4). Please correct the following issues, then upload again. ITMS-90338: Non-public API usage - The app references non-public selectors in Onay: _setWidth:. 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/ Best regards, The App Store Team We tried to rename all methods or delete them and republish, but always receive this message. Can we get more detailed error description?
When I try to submit the app, I get the following error. Is there a way to solve this? Asset validation failed (90045) Invalid Code Signing Entitlements. Your application bundle's signature contains code signing entitlements that are not supported on iOS. Specifically, key 'UIRequiresFullScreen' in 'Payload/MyApp.iOS.app/MyApp.iOS' is not supported. Asset validation failed (90045) Invalid Code Signing Entitlements. Your application bundle's signature contains code signing entitlements that are not supported on iOS. Specifically, key 'CFBundleDisplayName' in 'Payload/MyApp.iOS.app/MyApp.iOS' is not supported. Asset validation failed (90045) Invalid Code Signing Entitlements. Your application bundle's signature contains code signing entitlements that are not supported on iOS. Specifically, key 'UIMainStoryboardFile' in 'Payload/MyApp.iOS.app/MyApp.iOS' is not supported. Asset validation failed (90045) Invalid Code Signing Entitlements. Your application bundle's signature contains code signing entitlements that
When I try to submit the app, I get the following error. Is there a way to solve this? Asset validation failed (90045) Invalid Code Signing Entitlements. Your application bundle's signature contains code signing entitlements that are not supported on iOS. Specifically, key 'UIRequiresFullScreen' in 'Payload/MyApp.iOS.app/MyApp.iOS' is not supported. Asset validation failed (90045) Invalid Code Signing Entitlements. Your application bundle's signature contains code signing entitlements that are not supported on iOS. Specifically, key 'CFBundleDisplayName' in 'Payload/MyApp.iOS.app/MyApp.iOS' is not supported. Asset validation failed (90045) Invalid Code Signing Entitlements. Your application bundle's signature contains code signing entitlements that are not supported on iOS. Specifically, key 'UIMainStoryboardFile' in 'Payload/MyApp.iOS.app/MyApp.iOS' is not supported. Asset validation failed (90045) Invalid Code Signing Entitlements. Your application bundle's signature contains code signing entitlements that
I'm trying to submit my app and ran into this error:Missing Marketing Icon - iOS Apps must include a 1024x1024px Marketing Icon in PNG format. Apps that do not include the Marketing Icon cannot be submitted for App Review or Beta App Review.So, I updated my asset catalog to include one, but now I keep getting this error:ERROR ITMS-90717: Invalid App Store Icon. The App Store Icon in the asset catalog in 'Some.app' can't be transparent nor contain an alpha channel.I have removed alpha and transparency with multiple Apps (Photoshop, pngcrush, imagemagick) but keep running into the validation error above. I'm pretty sure my PNG file does not contain any alpha channels or transparency at this point. The only way I found to pass validation is to supply the marketing icon in JPG format, contrary to the first error message.Anybody with similar issues or ideas how to pass validation with a PNG App Store icon?
I'm dealing with a problem uploading our release binaries that is completely perplexing. If I use the ITMS Transporter desktop app to upload my IPA, everything works fine. If I use the ITMS Transporter command line interface (which i'm calling from inside the desktop app's directory /Applications/Transporter.app/Contents/itms/bin/iTMSTransporter -m upload...) to upload my IPA, I get the following error ERROR ITMS-90529: Invalid package. Applications built with sdk 9.0 or later must be packaged as proper IPA files. No idea why this error is coming up. I can also use altool to upload my binaries successfully. The issue is altool is being deprecated and I need to be able to use the ITMS command line interface as part of some deployment scripts we have. Please help!
i'm starstruck haha This is with the exact same IPA file. I know you're asking the guy who was trying on Linux, but I want to also highlight that the same IPA file uploaded via the GUI of the MacOS Transporter app works, while passing that IPA into the command line interface for Transporter doesn't work. I suspect the MacOS Transporter GUI is using a slightly different version of the ITMS Transporter binary than the CLI or Linux Transporter app are.
Hi,I have been trying to resolve another warning.WARNING ITMS-90704: Missing App Store Icon. iOS Apps must include a 1024x1024px App Store Icon in PNG format. Without providing the icon in the Asset Catalog or via iTunes Connect, apps cannot be submitted for App Review or Beta App Review. Refer to https://developer.apple.com/ios/human-interface-guidelines/icons-and-images/app-icon/ for more information.Any help would be greatful.iOS11 / Xcode 9.0.1 / Mac High Sierra 10.13
Im also having the same issue trying to upload using the Transporter app for Linux. Using the macOS one works perfectly, but on linux i get the same error: ERROR ITMS-90529: Invalid package. Applications built with sdk 9.0 or later must be packaged as proper IPA files
Hi, I am facing a problem with Xcode 12.3, swift 5, and cocoapods-1.10.1 version when I want to publish my archive on Appstore Connect, everything goes well, but once the application sent I receive an e-mail from App Store Connect with the following error : ITMS-90429: Invalid Swift Support - The files libswiftDarwin.dylib, libswiftMetal.dylib, libswiftCoreAudio.dylib, libswiftsimd.dylib, libswiftQuartzCore.dylib, libswiftos.dylib, libswiftObjectiveC.dylib, libswiftDispatch.dylib, libswiftCoreLocation.dylib, libswiftAccelerate.dylib, libswiftCoreGraphics.dylib, libswiftCoreData.dylib, libswiftCoreFoundation.dylib, libswiftUIKit.dylib, libswiftCoreMedia.dylib, libswiftAVFoundation.dylib, libswiftContacts.dylib, libswiftCore.dylib, libswiftFoundation.dylib, libswiftMediaPlayer.dylib, libswiftCloudKit.dylib, libswiftCoreImage.dylib aren’t at the expected location /Payload/WoWonder.app/Frameworks. Move the file to the expected location, rebuild your app using the current public (GM) version of Xcode, and