Search results for

ITMS-90158

1,681 results found

Post

Replies

Boosts

Views

Activity

Reply to AppStore submission for Ruby/Glimmer app on MacOS without Xcode
Thanks for detailed commands! That really helped. I found the matching profile, copied it over to embedded.provisionprofile, resigned the executable & bundle, and uploaded using Transporter. Received missing an application identifier error and fixed it from https://developer.apple.com/forums/thread/748589?login=true and TestFlight, Provisioning Profiles, and the Mac App Store Uploaded & Validated w/ Transporter, but received an email about: ITMS-91109: Invalid package contents - The package contains one or more files with the com.apple.quarantine extended file attribute, such as “com.chipcastle.pathmanager.pkg/Payload/PATHmanager.app/Contents/embedded.provisionprofile”. This attribute isn’t permitted in macOS apps distributed on TestFlight or the App Store. Please remove the attribute from all files within your app and upload again. Attempted to remove extended attributes as follows (sudo had no effect): ~/Desktop/distribution/PATHmanager.app/Contents λ xattr embedded.provisionprofile com.app
Topic: Code Signing SubTopic: General
Mar ’25
New iOS-style App Groups Prevent App Submission
We have a macOS app that has a Photos Extension, which shares documents with the app via an app group container. Historically we used to have an iOS-style group identifier (group.${TeamIdentifier}${groupName}), because we were lead by the web interface in the developer portal to believe this to be the right way to name groups. Later with the first macOS 15 betas last year there was a bug with the operating system warning users, our app would access data from different apps, but it was our own app group container directory. Therefore we added a macOS-style group identifier (${TeamIdentifier}${groupName}) and wrote a migration of documents to the new group container directory. So basically we need to have access to these two app group containers for the foreseeable future. Now with the introduction of iOS-style group identifiers for macOS, Xcode Cloud no longer archives our app for TestFlight or AppStore, because it complains: ITMS-90286: Invalid code signing entitlements - Your application bundle’s si
1
0
343
Mar ’25
SDK version issue
Hi, our team received this message ITMS-90725: SDK version issue - This app was built with the iOS 17.0 SDK. Starting April 24, 2025, all iOS and iPadOS apps must be built with the iOS 18 SDK or later, included in Xcode 16 or later, in order to be uploaded to App Store Connect or submitted for distribution. We still have a requirement to support iOS 12.5.7 for our users. If I change to build SDK iOS18 using Xcode 16 or later, will my app submission be rejected during review process? (since I specified my minimum iOS version to be 12)
1
0
6.6k
Mar ’25
ITMS-90426: Invalid Swift Support - The SwiftSupport folder is missing.
Flutter iOS App. Previous version submitted passed. Only change the version and some text, submit has 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. the release steps: flutter clean; flutter pub get; flutter build ios --release; xcode - clean build folder; archive; distribute app Searched online and tried many suggestions, none works.
2
0
331
Feb ’25
Reply to Invalid code signing entitlements with app group on macOS
I also have been blocked by a sudden failure to upload macOS archives to App Store Connect the past few days, but finally managed to fix it by forcing XCode 16.3 beta to regenerate the provisioning profile(s) of the offending app extensions that uses the App Groups capability. I deliberately include all the steps I took to provide as much detail as possible for anyone else facing the same issue. The exact error I got is as follows (redacted for privacy reasons): ITMS-90286: Invalid code signing entitlements - Your application bundle’s signature contains code signing entitlements that aren’t supported on macOS. Specifically, the “[group.com.xxx]” value for the com.apple.security.application-groups key in “com.xxx.appname.pkg/Payload/appname.app/Contents/PlugIns/AppNameExtension.appex/Contents/MacOS/AppNameExtension” isn’t supported. This value should be a string or an array of strings, where each string is the “group” value or your Team ID, followed by a dot (“.”), followed by the group name. If you'r
Topic: Code Signing SubTopic: Entitlements Tags:
Feb ’25
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'm trying to use Transporter to upload my .ipa file to the Apple Store and make it available on TestFlight. I'm generating the .ipa with the command eas build -p ios --profile production. However, I'm receiving the ITMS-90426 error in my email. I've seen many suggested solutions for this issue, but most of them involve using Xcode. The problem is, I don't use Xcode. I only use Transporter on my Mac to upload the app, and I develop on a Windows environment. Could you please guide me on how to generate the required files using Expo/EAS to avoid this issue?
1
0
540
Feb ’25
Reply to ShazamKit supported for iOS apps that can run on Mac silicon?
I’m having the same problem, only with another Lib: This is what the E-Mail from Apple sais about my App: Although delivery was successful, you may want to correct the following issues in your next delivery. Once you've corrected the issues, upload a new binary to App Store Connect. ITMS-90863: Macs with Apple silicon support issue - The app links with libraries that aren’t present in macOS: /usr/lib/swift/libswiftWebKit.dylib And I notice that the App can’t be installed on my Mac via Testflight. The latest AppStore version of the App can be installed on the Mac (from with the AppStore). I’m not sure when exactly the issue has started, but there are other threads in the Apple developer forum where developers have the very same problem: https://developer.apple.com/forums/thread/766061 https://developer.apple.com/forums/thread/756325 https://developer.apple.com/forums/thread/771068
Topic: Media Technologies SubTopic: Audio Tags:
Feb ’25
Reply to Provisioning profile failed qualification. Profile doesn't support App Groups.
even with the already uploaded binary, cannot get it to be reviewed... The status of your app has changed to Invalid Binary. Please correct the following issues and upload a new binary to App Store Connect. ITMS-90286: Invalid code signing entitlements - Your application bundle’s signature contains code signing entitlements that aren’t supported on macOS. Specifically, the “[group.com.
Feb ’25
Handling ITMS-91061: Missing privacy manifest
An ITMS-91061: Missing privacy manifest rejection email looks as follows: ITMS-91061: Missing privacy manifest- Your app includes , which includes , an SDK that was identified in the documentation as a privacy-impacting third-party SDK. Starting February 12, 2025, if a new app includes a privacy-impacting SDK, or an app update adds a new privacy-impacting SDK, the SDK must include a privacy manifest file. Please contact the provider of the SDK that includes this file to get an updated SDK version with a privacy manifest. For more details about this policy, including a list of SDKs that are required to include signatures and manifests, visit: https://developer.apple.com/support/third-party-SDK-requirements. Glossary ITMS-91061: Missing privacy manifest: An email that includes the name and path of privacy-impacting SDK(s) with no privacy manifest files in your app bundle. For more information, see https://developer.apple.com/support/third-party-SDK-requirements. : The specified privac
0
0
5.9k
Feb ’25
Reply to metadata file in .itmsp file (Transporter)
UPDATE : I was able to narrow down my metadata errors vaslty. The only error that sustains is as follows. Package Summary: 1 package(s) were not uploaded because they had problems: /Users/isseyyohannes/Desktop/ALGORA_Performance.itmsp - Error Messages: ERROR ITMS-3000: Line 16 column 15: element versions not allowed here; expected the element end-tag or element metadata_token at XPath /package/versions ERROR ITMS-3000: Package null failed schema validation. [2025-02-20 12:23:44 EST] DBG-X: Returning 1 This is the structure of my metadata file. GL5BCCW69X GL5BCCW69X ALGORA_Performance.pkg ALGORA Performance Trading made easy. This app is optimized for macOS trading. Any insight on to what I may be doing wrong in my metadata.xml file would be appreciated. Thank you. Note : md5 was hidden on purpose.
Feb ’25
Regarding Firebase Privacy Manifest in PrivacyInfo.xcprivacy
I am reaching out regarding the ITMS-91061 rejection issue we encountered while submitting our app to the App Store. The rejection is related to missing privacy manifests for Firebase and related SDKs. Currently, our PrivacyInfo.xcprivacy file is structured as follows: Could you please confirm whether we can modify this file to include Firebase-related privacy information to resolve the rejection? If so, could you provide guidance on the correct format and the necessary entries we should add? We appreciate your support and look forward to your response.
1
0
553
Feb ’25
metadata file in .itmsp file (Transporter)
I am attempting to upload an application to the app store. The selected method was using Transporter through terminal commands. In this sense, I keep receiving a metadata error which is as follows : Command (Assume values are filled in) /usr/local/itms/bin/iTMSTransporter -m upload -u MY_EMAIL -p YOUR_APP_SPECIFIC_PASSWORD -f /Users/isseyyohannes/Desktop/ALGORA_Performance.itmsp --asc-provider GL5BCCW69X -v detailed I receive the following error Package Summary: 1 package(s) were not uploaded because they had problems: /Users/isseyyohannes/Desktop/ALGORA_Performance.itmsp - Error Messages: ERROR ITMS-3000: Line 9 column 25: element data_file incomplete; missing required elements checksum and size at XPath /package/software_assets/asset/data_file ERROR ITMS-3000: Line 12 column 24: element software_metadata not allowed here; expected the element end-tag or element metadata_token at XPath /package/software_metadata ERROR ITMS-3000: Line 13 column 19: element software not
1
0
468
Feb ’25