App Submission

RSS for tag

Submit your apps to the App Store using App Store Connect.

Posts under App Submission tag

164 Posts
Sort by:

Post

Replies

Boosts

Views

Activity

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 "<path/to/SDK>", 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 privacy-impacting SDK that doesn't include a privacy manifest file. If you are the developer of the rejected app, gather the name of the SDK from the email you received from Apple, then contact the SDK's provider for an updated version that includes a valid privacy manifest. After receiving an updated version of the SDK, verify the SDK includes a valid privacy manifest file at the expected location. For more information, see Adding a privacy manifest to your app or third-party SDK. If your app includes a privacy manifest file, make sure the file only describes the privacy practices of your app. Do not add the privacy practices of the SDK to your app's privacy manifest. If the email lists multiple SDKs, repeat the above process for all of them. If you are the developer of an SDK listed in the email, publish an updated version of your SDK that includes a privacy manifest file with valid keys and values. Every privacy-impacting SDK must contain a privacy manifest file that only describes its privacy practices. To learn how to add a valid privacy manifest to your SDK, see the Additional resources section below. Additional resources Privacy manifest files Describing data use in privacy manifests Describing use of required reason API Adding a privacy manifest to your app or third-party SDK TN3182: Adding privacy tracking keys to your privacy manifest TN3183: Adding required reason API entries to your privacy manifest TN3184: Adding data collection details to your privacy manifest TN3181: Debugging an invalid privacy manifest
0
0
3.5k
2w
Missing the Required "In-App Purchases and Subscriptions" Section in App Store Connect
CONTEXT: iOS: 18.2.1 || macOS: 15.4 || Xcode: 16.2 || App status: Not yet released || In-app purchase type: Subscription || App version: 1.0, Build 3 ISSUE:
 App Store Connect has rejected our latest app submission with the instructions “…submit your in-app purchases and upload a new binary in App Store Connect…”. Unfortunately, the required "In-App Purchases and Subscriptions" section is missing from the ‘version page’ of our submission. This is further complicated by the fact that we had already tested the subscription in App Store Connect’s sandbox, where it successfully returned the non-domestic storefront pricing for Hungary (HUF1,490.00/year). After reviewing nearly four dozen Apple pages of documentation and a dozen Apple forum posts, we found only one relevant link: https://developer.apple.com/help/app-store-connect/manage-submissions-to-app-review/submit-for-review Unfortunately, the instructions under the disclosure triangle: "Submit an in-app purchase for the first time" confirm that the "In-App Purchases and Subscriptions" section is missing from our version page. Additionally, review of the blue warning box on the Subscription page includes the following instructions: "…Create your subscription, then select it from the app’s In-App Purchases and Subscriptions section on the version page…" Unfortunately, this section does not exist on our version page, confirming that there is no specific section labeled "In-App Purchases and Subscriptions" available. Similar issues have been reported by other developers. See this Stack Overflow thread for additional context: https://stackoverflow.com/questions/73098652/app-store-connect-in-app-purchase-and-subscriptions-section-missing HISTORY: Successfully created and sandbox tested the subscription in App Store Connect. Reviewed over five dozen pages of Apple documentation and forum posts as well as Stack Overflow. Have repeatedly loaded and checked the 'version page' for the "In-App Purchases and Subscriptions" section, which is unfortunately missing from our submission. QUESTIONS: Where is the "In-App Purchases and Subscriptions" section located, if not on the 'version page' of our submission? Is there an alternative method to submit in-app purchases and upload a new binary in App Store Connect? Do we need to remove any part of the submission to access the "In-App Purchases and Subscriptions" section? What is the risk of losing our app name 'Concensus' in the Apple App Store if we delete any portion of the submission? We would appreciate guidance on how to proceed with submitting our in-app purchase subscription along with our new app version. Grateful Indeed.
1
0
31
10h
App Store Connect Upload bug
I am trying to submit my app for review but when I click on the 'add to review' button, I am getting the message: Unable to Add for Review The items below are required to start the review process: There are still screenshot uploads in progress. However, there is nothing I am uploading... I tried removing all screenshots, nothing works. It has been 4 days, I cant update my app on the app store... impossible to get any response from Apple... Any inputs will be greatly appreciated.
1
1
83
1w
App Transparency can't publish for review?
Hi recent app update review was rejected because we were informed we had to implement the App Transparency Tracking UI to let users choose. (we had just successfully published two days prior to this, and we need to get some bug fixes out with a new submission) Nothing about the app with respect to data collection had changed between the successful submission and the rejection and still wondering why we were rejected for that reason. We do not track data. We do collect user info and info about app usage for user account login and app performance analytics, and also for our development cycle. So I updated the app to present the Tracking Transparency UI at startup and that is all good. Now I add the app to the submission form, and I go update our privacy policy to define what data we collect and how we are using it. I publish the updated privacy information. but now I am stuck. The submission page returns a message that I have to set up the privacy data to be able to submit for review Your app contains NSUserTrackingUsageDescription, indicating that it may request permission to track users. To submit for review, update your App Privacy response to indicate that data collected from this app will be used for tracking purposes, or update your app binary and upload a new build. Learn More But I have already defined and published that privacy data. It seems it is not finding the Privacy data or what? What could be going wrong here? Thanks for any ideas!
2
0
227
1w
Confusion Over In‑App Purchase Setup for Auto‑Renewable Subscription – Need Guidance
Hello everyone, I’m having trouble with our app’s subscription setup during App Store review, and I’m hoping to get some guidance. Our app, offers an auto‑renewable subscription. In App Store Connect, we created the subscription as an “Auto‑Renewable Subscription” with a product identifier. We do not offer consumable or non‑consumable in‑app purchases—only this subscription. However, Apple recently rejected our submission with the following message: “We have started the review of your app, but we are not able to continue because we cannot locate the in‑app purchases within your app at this time. Next Steps To help us proceed with the review of your app, please reply to this message providing the steps for locating the in‑app purchases in your app. Note that in‑app purchases are reviewed in an Apple‑provided sandbox environment. Make sure they have been appropriately configured for review in the Apple‑provided sandbox environment. If you are restricting access to in‑app purchases based on factors such as storefront or device configurations, please include this information in your reply along with steps to enable the in‑app purchases for our review.” I’m confused for a couple of reasons: 1. We only offer subscriptions—there are no consumable or non‑consumable products. Yet, Apple’s message refers to “in‑app purchases.” 2. It seems our subscription product is not being found in the sandbox environment. Our subscription is currently in “Waiting for Review” status in App Store Connect, so when using StoreKit 2 (via Product.products([…])) the array returns empty. 3. I’m not sure if we need to enable something else in App Store Connect for subscriptions to be testable in the sandbox, or if our configuration is insufficient for review. Has anyone encountered a similar situation? What are the steps you took to ensure your auto‑renewable subscription were testable for App Store review? Any tips on dealing with this loop—where the subscription must be approved for reviewers to find it, yet Apple won’t approve the app until they can test it? Thanks in advance for any insights or suggestions!
1
0
270
1w
Subscriptions not selectable during binary submission - stuck in "Developer Action Needed"
I am experiencing difficulties including subscriptions for the first time in a new binary version. The subscriptions are currently in “Developer Action Needed” status, and I am unable to reset them to “Ready to Submit”. I assume this is why the “Select In-App Purchases and Subscriptions” option is missing from the binary version page. Since subscriptions are a vital part of the app, their absence has led to the app being rejected in the review process. Any advice on how to proceed?
2
0
187
1w
No Appeal Response
Hello, I've submitted my game to app store review and got rejected, I sent an appeal on Mar 2, but I didn't receive any confirmation email that the appeal has been sent, which was weird thing since Apple always send confirmation emails! and I didn't receive any response yet! My game is still in rejected state I didn't upload any new version as I wait for the appeal response. M questions are, do Apple usually sends a confirmation emails after submitting an appeal? and should I wait more for the response? (it has been 10 days). Thanks in advance for anyone who could share any insights.
1
0
221
2w
App "In Review" for over 4 days now
I've built and released quite a few apps, and it always goes something like this App is "waiting for review" for 12-24 hours App is "in review" for 4-8 hours App is approved or rejected However, this time is different. I submitted a brand new app to the store. Within 12 hours, it moved from "waiting for review" to "in review". Pretty normal. Over 48 hours later, it's still "In review". I rejected it and resubmitted because I wanted to remove a distribution country. And again, same thing. Moved to "In Review". It's been over 4 days now. I don't understand whats taking so long here. This is incredibly frustrating as the app launched just fine on the Google Play store, and I'd like to start marketing them together. What can I do?
2
1
236
2w
Account Flagged 3.2(f) and no reply at all
We are a team of developers, and our company is involved in creating mobile applications. Recently, our developer account was terminated, and all active apps were removed from the App Store. The email mentioned that our app violates section 3.2(f) of the Apple Developer Program License Agreement. We've been trying to identify the issue since then, but we're not involved in any fraudulent activities. Our company is facing a critical situation as it is essential for us to have the apps back on the App Store as soon as possible. We are unsure of how to proceed and would greatly appreciate any assistance or guidance. Thanks. Our app ID com.seriktes.kz App name Seriktes
1
0
216
2w
Guideline 4.3(a) - Design - Spam
Dear Apple Review Team & Develpers! Could anyone clarify why Apple Reviewers, when rejecting the app under Guideline 4.3(a) - Design - Spam, do not provide any specific details? Each time my app is rejected, I receive a generic, automated response. In contrast, I provide detailed information and request clarification on the exact reasons for the rejection- specifically, what aspects of the app do not meet Apple's requirements. However, the responses I receive are always the same standard message without any useful details. Am I correct in understanding that the review process is entirely automated, with no human evaluation, resulting in repetitive, unhelpful replies? I would appreciate a more detailed response that can genuinely help me address the issue and ensure my app complies with Apple's guidelines. Here is their standard generic response to any my reply where I provide details and ask questions, but Apple Reviewer answer alsway with the same text: Guideline 4.3(a) - Design - Spam This app duplicates the content and functionality of other apps on the App Store, which is considered a form of spam. Specifically, this app appears to be identical to apps already on the App Store from other developers. Apps that duplicate content or functionality create clutter, diminish the overall experience for the end user, and reduce the ability of developers to market their apps. Next Steps It would be appropriate to revise your app to provide a unique experience or submit a new app that does not duplicate the content and functionality of other apps on the App Store. Resources Some factors that contribute to a spam rejection may include: Submitting an app with the same source code or assets as other apps already submitted to the App Store Creating and submitting multiple similar apps using a repackaged app template Purchasing an app template with problematic code from a third party Submitting several similar apps across multiple accounts Learn more about our requirements to prevent spam in App Review Guideline 4.3(a). Support Reply to this message in your preferred language if you need assistance. If you need additional support, use the Contact Us module. Consult with fellow developers and Apple engineers on the Apple Developer Forums. Provide feedback on this message and your review experience by completing a short survey. Review Environment Submission ID: c4a62f43-b02a-40f0-b763-e00fcc996512 Review date: March 04, 2025 Version reviewed: 11.4.1202
1
0
326
3w
App Review rejected due to Guideline 4.3(a) - Design - Spam
Hello everyone, We’re facing an ongoing issue with our app being rejected under the 4.3(a) Spam guideline, and we’re hoping the community can offer some advice on how to resolve it. Our app is a free sports application that provides real-time score updates. It also features commentary from several top contributors and journalists. We offer exclusive features that are completely original—we don’t replicate or borrow any designs or functionalities from other apps on the App Store. Additionally, the app includes games that we have personally researched, designed, and developed from scratch without using any third-party libraries. We were flagged under 4.3(a) Spam after a very minor update, which primarily focused on fixing some interface-related bugs. Despite these minimal changes, our app was rejected under the Spam guideline. To address this, we have sent detailed information to Apple Review, including our development roadmap, screenshots of design versions, and even git logs to demonstrate the development process of our team. These materials clearly show that our app is not a repackage or spam app, as suggested. However, despite all these efforts, the responses we’ve received seem automated, and we have not been given clear explanations or a resolution. We’ve spent a lot of time trying to troubleshoot, removing dead code, and restructuring the project (as Apple claimed we might be sharing binary files with a mysterious app...), but all efforts have been in vain. I’m not sure how to resolve the issue of 'sharing similar binaries, metadata' with other apps if that’s the case. Could this be because I’m using Flutter and package on pub.dev like many other developers ? We’re at a point where we don’t know how to proceed. What steps should we take next to resolve this issue? Has anyone here faced a similar challenge and found a way to get a more detailed response from Apple Review? Any advice would be greatly appreciated! Thank you for your time and help! Kind regards, Michael
2
0
287
3w
How do I determine whether a framework contains bitcode?
Hi there I've recently had my upload rejected in Xcode Organizer as a result of one of the frameworks we use containing bitcode. Error: [ContentDelivery.Uploader.XXXXXXXXXX] Validation failed (409) Invalid Executable. The executable 'Sam.app/Frameworks/Foo.framework/Foo' contains bitcode. Is there an accurate way to determine whether an .xcframework contains bitcode ahead of time without using Xcode Organiser? My current methodology is below, please can I get some confirmation that this is accurate, or suggest a more efficient approach? I have concerns about my approach and whether it throws false positives for empty bitcode markers. 1. get original framework size 2. run xcrun bitcode_strip -r framework_path -o temp 3. get new framework size 4. if new size is smaller than original, then it contains bitcode Thanks for the help, Sam
1
0
369
4w
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 allowed here; expected the element end-tag or element "game_center", "in_app_purchases", "products", "read_only_info" or "versions" at XPath /package/software_metadata/software" ERROR ITMS-3000: "Line 16 column 28: element "bundle_id" not allowed anywhere; expected element "read_only_value" at XPath /package/software_metadata/software/read_only_info/bundle_id" ERROR ITMS-3000: "Line 17 column 30: element "app_version" not allowed anywhere; expected element "read_only_value" at XPath /package/software_metadata/software/read_only_info/app_version" ERROR ITMS-3000: "Line 18 column 33: element "product_family" not allowed anywhere; expected element "read_only_value" at XPath /package/software_metadata/software/read_only_info/product_family" ERROR ITMS-3000: "Line 19 column 30: element "read_only_info" incomplete; missing required element "read_only_value"" ERROR ITMS-3000: "Line 20 column 20: element "software" incomplete; expected element "software_assets" or "software_metadata"" ERROR ITMS-3000: "Package "null" failed schema validation." [2025-02-19 15:45:07 EST] <main> DBG-X: Returning 1 Essentially just a bunch of warnings about my metadata file which I edited manually to read the following <?xml version="1.0" encoding="UTF-8"?> <package version="software5.10" xmlns="http://apple.com/itunes/importer"> <provider>GL5BCCW69X</provider> <team_id>GL5BCCW69X</team_id> <software_assets> <asset type="bundle"> <data_file> <file_name>ALGORA_Performance.pkg</file_name> <checksum type="sha1">7acb9fcb19eb203bdc6038f88d06a67386900b28</checksum> <size>75619323</size> </data_file> </asset> <software_metadata> <software> <vendor_id>93274081</vendor_id> <read_only_info> <read_only_value key="bundle_id">com.algora.ALGORA-Performance</read_only_value> <read_only_value key="app_version">0.0.0</read_only_value> <read_only_value key="product_family">macOS</read_only_value> </read_only_info> </software> </software_metadata> </software_assets> </package> Last note is that I manually created the metadata.xml file and moved it via local terminal for fear of having to use XCode which I am not familiar with. ANY HELP IS APPRECIATED
1
0
332
Feb ’25
iTMSTransporter errors with "Bad Status received from server: 400"
I could use an extra set of eyes on this - I'm totally stuck. Any ideas or thoughts on things to check would be much appreciated. This problem started on 2025-02-06. It's a Unity project under active development, but I don't see where that can create a problem when using Transporter. We have been uploading fine for months. Now we are seeing errors like this: &lt;RLT-005&gt; INFO: Upload Failed: (id: 650d9057-eb69-4d32-a765-e53894c332e3 file: myapp.ipa part: 24) ([1/3] will retry): org.apache.http.NoHttpResponseException: The target server failed to respond &lt;RLT-005&gt; INFO: Starting upload for reservation: (650d9057-eb69-4d32-a765-e53894c332e3) file: (myapp.ipa/24) attempt: 2 size: 5242880 &lt;main&gt; ERROR: myapp.ipa (8) - Bad Status received from server: 400 &lt;main&gt; ERROR: Could not upload 1 file(s): &lt;main&gt; ERROR: Could not upload file: myapp.ipa 28 parts failed: [10, 24, 5, 14, 7, 2, 16, 19, 25, 1, 21, 9, 3, 6, 8, 15, 12, 27, 18, 26, 11, 20, 17, 4, 23, 28, 13, 22] &lt;main&gt; ERROR: Please retry your upload later. That "400" server error has me thinking it could be something on Apple's side. But I've also seen this error: INFO: Verifying checksums against the previous upload attempt. &lt;main&gt; ERROR: A file(s) has been modified between the initial upload and restart of the upload. Please retry your upload. So I don't know what to make of it. Nothing had changed in how we use Transporter. Things I've tried: I have tried the Transporter command using all three "-t" options: Aspera, Signiant, HTTP. Same errors. I have tried using a new app password. I have tried upgrading the OS version to Sequoia 15.3. Xcode 16.0 with iOS 18 stuff I have tried upgrading Transporter to 3.4.1. I am running a Mac mini - M1, 2020. I am working on trying with a different host on a different internet connection. Maybe some network security device is interfering somehow. I am able to manually use Xcode to archive the project and upload it to TestFlight, so the problem appears to be isolated to Transporter or the servers it talks to. The only unexpected warning I see when manually archiving and uploading is something about a HelpShiftX.framework dSYM not being included. Could that be a cause of the Transporter issue?
1
0
306
Feb ’25
Flutter macOS app getting warnings related to privacy manifest
We are developing a Flutter application targeted for MacOS and Windows . We are using the FlutterMacOS and connectivity_plus packages in our app But whenever we are releasing a version to App Store we are getting the privacy manifest file missing for above 2 packages We tried to add xcPrivacy file inside the Runner Xcode project. But that doesn't solve the issue Adding the relevant lines from the warning email getting from App Store below "ITMS-91061: Missing privacy manifest - Your app includes “Contents/Frameworks/FlutterMacOS.framework/Versions/A/FlutterMacOS”, which includes Flutter, an SDK that was identified in the documentation as a commonly used third-party SDK. Starting February 12, 2025, if a new app includes a commonly used third-party SDK, or an app update adds a new commonly used third-party SDK, the SDK must include a privacy manifest file or you won’t be able to submit the app for review in App Store Connect. 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. ITMS-91061: Missing privacy manifest - Your app includes “Contents/Frameworks/connectivity_plus.framework/Versions/A/connectivity_plus”, which includes connectivity_plus, an SDK that was identified in the documentation as a commonly used third-party SDK. Starting February 12, 2025, if a new app includes a commonly used third-party SDK, or an app update adds a new commonly used third-party SDK, the SDK must include a privacy manifest file or you won’t be able to submit the app for review in App Store Connect. 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." Please suggest a solution to solve this issue as early as possible , because February 12th onwards we will get blocked to release new versions
5
0
995
Feb ’25
Japanese Katakana and Sign up With Apple
We have an app that has failed during the app review for the Japanese market but has been accepted in several other markets successfully. We need the user's name in native Katakana format as we need it to be displayed in our restaurant Point of Sale systems for workers to be able to read and understand. We use 'Sign up with Apple', but when doing so, if this returns an anglicised given and family name, we have to request the customer supply their Katakana format name so that our in-store systems and staff can process and fulfil their orders. When the App Review process automatically tests the app, it uses "Apple John" as a customer's name. Since this is not a Japanese name, we ask for it again in the correct format, or we cannot allow the user to register. This contravenes Apple's rules, and thus, our app is rejected. If the Apple identity used belonged to a user more typical of the target market, it would work as required. Does anyone else have this issue, and how did you work around it? Tim
2
0
332
Feb ’25