Search results for

ITMS-90158

1,681 results found

Post

Replies

Boosts

Views

Activity

ITMS-90896 Error when uploading binary with Transporter
Hi I have an app with an Intents extension and a Widget extension that is failing to upload to App Store connect. I am receiving the following error and I have no idea how to fix it ERROR ITMS-90896: Invalid Mach-O header. The __swift5_entry section is missing for extension bundle Payload/[AppName].app/PlugIns/WidgetsExtension.appex, which prevents the extension from running. You can run the otool command against your binary to ensure there is a __swift5_entry section. This worked fine a couple of months ago on last submission. Thanks Alan
5
0
2.3k
Nov ’23
Your app has been changed to invalid binary and rejected
I am trying to submit my app for review on appstoreconnect, but after every attempt it immediately says your app has been changed to invalid binary and rejected. The error related to this rejections is: ITMS-91064: Invalid tracking information - A PrivacyInfo.xcprivacy file contains invalid tracking information at the following path: “Frameworks/MapboxCoreSearch.framework/PrivacyInfo.xcprivacy”. NSPrivacyTracking must be true if NSPrivacyTrackingDomains isn’t empty. Keys and values in your app’s privacy manifests must be valid. Despite the fact that my app's PrivacyInfo.xcprivacy states no that there are no tracking domains, privacy tracking is not enabled and that the Privacy Nutrition Label Types clearly state that there are no particular tracking happening across the selected the labels, which are course location, precise location and search history. The information in the IPrivacyInfo.xcprivacy in the app privacy settings and reflect that there is no tracking happening. I have attempted changing
1
0
784
Feb ’25
Enterprise IPA install from web fails with "incompatible platform: com.apple.platform.xros"
I am trying to set up a workflow where Apple Vision Pro users in my organization can install a signed enterprise .ipa file from an internal web page. The relevant link looks something like this: <a role=button href=itms-services://?action=download-manifest&url=https://my.example.com/path/manifest.plist>Click here to download</a> After verifying that all the mime types were correct on the server and the certificate was valid, I finally attached my AVP headset to my Mac's console app and saw that the errors look like this: [com.example.myapp] Skipping due to incompatible platform: com.apple.platform.xros Could not load download manifest with underlying error: Error Domain=ASDErrorDomain Code=752 Not compatible with this platform: com.apple.platform.xros UserInfo={NSDebugDescription=Not compatible with this platform: com.apple.platform.xros} This manifest.plist was made by the Distribute App workflow in Xcode 16.0. Multipart question: Is installing VisionOS apps via m
2
0
741
Oct ’24
ITMS-90683: NSMotionUsageDescription
I've received this email when attempting to upload my app to test flight, but I have a long description like This app collects motion data to track user activity and provide accurate workout insights. Motion tracking helps improve fitness and health-related features. specified in the project.pbxproj file, which is where all of these parameters are (and where I've specified them in the past).
1
0
326
Feb ’25
App alternative icon not working when archieve.
I add the following info in the build settings of my app. Then I also add the icon to my asset. I build the app, it works normally, but I notice that when I changed the icon to 'AppIcon-Defaults', The icon change alert didn't appear. but it succeeds . I uploaded the archive to App Store I got: ITMS-90895: Missing Icon - The Info.plist key CFBundleIcons.CFBundleAlternateIcons contains an entry “AppIcon-Defaults” that references asset “AppIcon-Defaults.” No such asset is present in the asset catalog. Then I use xcrun --sdk iphoneos assetutil --info Assets.car to check the assets inside the archieved app, It have the asset.
2
0
527
Feb ’25
Reply to Unable to upload to store using altool after account transfer
This is the altool command -> FAILURE xcrun altool --verbose --list-providers -u USERNAME --password APPLICATION_PASS 2025-01-28 11:54:56.589 Verbose logging enabled. 2025-01-28 11:54:56.591 Will look for transporter at executable bundle relative path: /Applications/Xcode.app/Contents/SharedFrameworks/ContentDeliveryServices.framework/itms/bin/iTMSTransporter 2025-01-28 11:54:56.591 Looking for Transporter at path: /Applications/Xcode.app/Contents/SharedFrameworks/ContentDeliveryServices.framework/itms/bin/iTMSTransporter 2025-01-28 11:54:56.591 Looking for Transporter at path: /Applications/Xcode.app/Contents/Developer/usr/bin/../SharedFrameworks/ContentDeliveryServices.framework/itms/bin/iTMSTransporter 2025-01-28 11:54:56.591 Looking for Transporter at path: /Applications/Xcode.app/Contents/Developer/usr/bin/../itms/bin/iTMSTransporter 2025-01-28 11:54:56.591 Looking for Transporter at path: /Applications/Transporter.app/Contents/itms/bin/iTMSTransporter 2025
Jan ’25
App Store Connect invalidating binary during App Review - built with Xcode Cloud / Xcode 16 RC
I archived and uploaded a build with Xcode 16 RC earlier today since it wasn't available in Xcode Cloud at that moment. The upload was successful. Since then, Xcode Cloud was updated with Xcode 16 RC and I can build and deploy to TestFlight and App Store Connect that way too. Now, upon submitting my app to App Review, the binary is being rejected as invalid due to unsupported version of Xcode. Rejections Sept 9th at 11:28 PM Central and Sept 10th 12:37 AM. Here is the error message I received via email: ITMS-90111: Unsupported SDK or Xcode version - App submissions must use the latest Xcode and SDK Release Candidates (RC). For details on currently supported versions, visit: https://developer.apple.com/news/releases. Upon visiting the site, you can see a developer news article stating that App Review is now accepting builds created from Xcode 16 RC. I assume this is just the system going through upgrades and the whole system isn't updated yet. Is anyone else having issues submitting Xcode 16 RC builds
10
0
2.0k
Sep ’24
Issue uploading release builds using ITMS Transporter: ITMS-90529 Invalid package
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!
5
0
1.3k
Jan ’24
Entitlements/signature problem with app submission
I really need help. Can anyone decrypt the following message for me: Dear Developer, We identified one or more issues with a recent delivery for your app, MYAPP 2.0 (1200). Please correct the following issues, then upload again. ITMS-90288: Invalid Code Signing Entitlements - The entitlements in your app bundle signature do not match the ones that are contained in the provisioning profile. According to the provisioning profile, the bundle contains a key value that is not allowed: '' for the key 'com.apple.application-identifier' in 'MYAPP.app/Contents/Frameworks/libsqlite3s.dylib' ITMS-90286: Invalid Code Signing Entitlements - Your application bundle's signature contains code signing entitlements that are not supported on macOS. Specifically, value '' for key 'com.apple.application-identifier' in 'MYAPP.app/Contents/Frameworks/libsqlite3s.dylib' is not supported. This value should be a string starting with your TEAMID, followed by a dot '.', followed by the bundle identifier . The 2 dylibs
1
0
1k
Apr ’23
Assistance Needed: App Submission Issue (ITMS-90426)
Hello, We submitted our app on TestFlight, but received an automated response with the following error: ITMS-90426: Invalid Swift Support - The SwiftSupport folder is missing. Rebuild your app using the current public (GM) version of Xcode and resubmit it. Our app is developed entirely in Objective-C, and we’re unsure why it’s looking for SwiftSupport. Despite attempting several potential solutions, the error persists. Could someone please assist us with understanding why this is happening and advise on how to proceed with the submission? Any guidance would be greatly appreciated. Thank you for your help.
1
0
492
Jan ’25
ITMS-90429: Invalid Swift Support
Build the archive, validating and uploading it to App Store Connect - TestFlight is successful from Xcode (16.0, macOS 15.1.1). Although after that the build is rejected stating : ITMS-90429: Invalid Swift Support - The files libswiftCoreFoundation.dylib, libswiftCoreData.dylib, libswiftCore.dylib, libswiftFoundation.dylib, libswift_Concurrency.dylib, libswiftObjectiveC.dylib aren’t at the expected location /Payload/Runner.app/Frameworks. Move the file to the expected location, rebuild your app using the current public (GM) version of Xcode, and resubmit it. Cross checked the Archive and .ipa file, where we found that the mentioned .dylib files are actually present inside the /Payload/Runner.app/Frameworks folder, and all the .dylib files are also present in the SwiftSupport/iphoneos folder. Scenario : using tdLib compilation libtdjson.xcframework (embedded & signed) for ios arm64 placed under Framworks, in my Flutter application, calling methods via Method Channels, interacting with AppDelegate.
3
0
1.1k
Feb ’25
Reply to ITMS-91109 for logo as PNG file of about dialog
After upload got a mail from AppStoreConnect 'ITMS-91109: Invalid package contents - The package contains one or more files with the com.apple.quarantine extended file attribute'. Indeed in the past xcode complained about such files, like images saved from Photoshop that have extended attributes. Easily removed with 'xattr -c'. But, if this is an issue to send us emails about AFTER upload, then please have xcode check this BEFORE upload.. I had 3000+ such images.
Jan ’25