Apple, Please Investigate: Two Apps Rejected for Information Already Provided in the Original Submissions Dear Apple Developer Community and App Review Team, I am writing to report a serious and extremely frustrating problem I have experienced with two different applications submitted to the App Store. Both applications were rejected under App Review Guideline 1.3, requesting answers to four questions that I had already answered completely in the App Review Notes during the ORIGINAL submissions. The information was not added after rejection. It was already provided before either application entered review. I fully support Apple’s strict requirements for children’s applications. However, these repeated incidents raise serious concerns about how App Review Notes and supporting documents are handled. **1. Kalimati - كلماتي Apple App ID: 6812125263** Kalimati is an educational application that helps children learn Arabic words and action verbs through interactive activities and animations. When submitting Kalimati for the first time, I explicitly answered all four required questions in the App Review Notes: Third-party analytics. Third-party advertising. Sharing user or device data with third parties. Other collection or processing of user or device information. Despite providing complete answers, Kalimati was rejected on October 11, 2026, requesting answers to those exact same questions. These answers were already included in the original submission! I responded again and resubmitted the application on October 11. As of October 22, Kalimati remains in “Waiting for Review” status, 11 days after resubmission. I contacted Apple Developer Support multiple times. Although I was informed that steps would be taken to expedite the review, the application remains in the queue. This delay followed a request for information that had already been provided. **2. HeroHop: Sky Adventure Apple App ID: 6823625184** After my experience with Kalimati, I took additional precautions before submitting HeroHop on October 20, 2026. I provided the answers in TWO separate places: First: Complete answers to all four questions in the App Review Notes. Second: A detailed two-page PDF attachment titled “HeroHop-App-Review-Notes-Build-8.pdf”, addressing each question individually and explaining privacy practices, data handling, parental controls, and in-app purchases. Nevertheless, HeroHop was rejected the following day with an automated message requesting answers to the exact same four questions! I had answered every question in the designated field AND attached detailed supporting documentation. Yet the application was rejected as though none of this information had been provided. I repeated the answers and resubmitted HeroHop on October 21. The Real Problem The issue is not Apple’s requirement to answer privacy-related questions. Those questions are reasonable and important. The issue is that Apple repeatedly requests information that developers have ALREADY provided in the designated submission fields. With Kalimati, the answers were included in App Review Notes. With HeroHop, the answers were included in App Review Notes AND a separate PDF. Both applications received requests for the same information again. This raises important questions: Are App Review Notes displayed correctly to reviewers? Are supporting documents properly accessible? Are automated requests generated without checking existing answers? Is there a procedural problem in reviewing Kids Category submissions? I cannot determine the cause from outside Apple’s systems. However, experiencing the same issue twice, despite taking additional precautions, strongly suggests that the submission or review workflow requires investigation. The Consequences for Developers Every unnecessary rejection can delay an application for days or weeks. Kalimati has remained in “Waiting for Review” since October 11. Developers spend considerable time preparing applications, testing them, documenting compliance, and answering Apple’s questions. It is extremely frustrating to complete these requirements correctly, only to receive a rejection requesting information that was already provided. This wastes developers’ time, disrupts release schedules, and undermines confidence in Apple’s review process. What Apple Should Investigate and Improve I respectfully urge Apple’s App Review management and App Store Connect teams to investigate and improve the following: 1. Verify App Review Notes: Ensure submitted information is correctly stored, displayed, and examined before requesting additional answers. 2. Verify attachments: Ensure supporting PDFs and documents are clearly visible and accessible to reviewers. 3. Prevent repeated requests: Before issuing a rejection, verify whether the requested information already exists in the original submission. 4. Provide specific explanations: If an answer is insufficient, explain precisely what is missing instead of repeating the same questionnaire. 5. Investigate the Kids Category workflow: Examine why the same four Guideline 1.3 questions are repeatedly requested despite documented answers. 6. Establish an escalation channel: Allow developers to report recurring procedural problems beyond individual rejection decisions. Concern About My Upcoming macOS Application I am currently developing another application for macOS. After these experiences, I am genuinely concerned that I may encounter another unnecessary rejection because information I carefully provide is overlooked. Developers should not have to worry whether their App Review Notes will actually be considered. A Direct Appeal to Apple I am not requesting special treatment, exceptions to Apple’s guidelines, or approval without proper review. I fully respect Apple’s responsibility to protect users, particularly children. I am simply asking Apple to ensure that information developers provide is actually read and considered before applications are rejected for supposedly missing information. Apple, please investigate this issue at both the management and technical levels. If there is a technical problem, fix it. If there is a procedural problem, improve the procedure. If answers are insufficient, explain exactly what is missing. This is a real and recurring problem that deserves serious attention. I also invite fellow developers to share their experiences: Have you received a Guideline 1.3 rejection requesting the four Kids Category answers even though you had already provided them in your original App Review Notes? I sincerely hope Apple takes this issue seriously and investigates its underlying cause. A Final Request to the Community Please help bring this issue to Apple’s attention. Salman Farhat

Hello Apple App Review Team, I am writing to express my serious concern and frustration regarding the prolonged review delay of our application, Kalimati – كلماتي. App Name: Kalimati – كلماتي Apple App ID: 6812125263 Version: 1.0 Resubmission Date: October 11, 2026 Current Status: Waiting for Review Developer Support Case: 102996639249 The Original Rejection Was Based on Information We Had Already Provided Our application was initially reviewed and rejected on October 11, 2026, under Guideline 2.1, with a request to answer four questions concerning Guideline 1.3 (Kids Category). What makes this situation particularly frustrating is that we had already provided complete, detailed answers to ALL FOUR QUESTIONS in the designated App Review Notes field BEFORE submitting the application for its initial review. To be absolutely clear: We did not merely provide general privacy statements or brief explanations. We specifically prepared a dedicated section addressing Guideline 1.3 (Kids Category), containing: The exact question regarding third-party analytics, followed by a clear and detailed answer. The exact question regarding third-party advertising, followed by a clear and detailed answer. The exact question regarding data sharing with third parties, followed by a clear and detailed answer. The exact question regarding additional user or device data collection, followed by a clear and detailed answer. These were the EXACT SAME FOUR QUESTIONS that Apple subsequently asked us to answer after rejecting the application, presented in EXACTLY THE SAME ORDER. Furthermore, our original App Review Notes included additional explanations regarding: Our parental gate implementation. Children’s privacy and safety. The absence of third-party advertising and analytics. Our one-time, non-consumable in-app purchase. Apple’s StoreKit payment processing. The Restore Purchases functionality. In other words, every piece of information requested in the rejection message had already been explicitly provided in the original submission. Nothing was missing. This raises a serious concern about whether the App Review Notes were actually reviewed before the rejection was issued. Had the information we carefully prepared been read and considered, this rejection and the resulting delay could likely have been avoided. Immediate Response and Resubmission Despite having already provided all the requested information, we responded immediately to the App Review Team on October 11. We repeated all four answers in full, once again emphasizing that they had already been included in our original App Review Notes. We then resubmitted the application on October 11 at 10:17 AM, just 24 minutes after the rejection. Since that moment, our application has remained in “Waiting for Review” without any further progress. No Substantive Response from Developer Support On October 14, we contacted Apple Developer Support to report the delay. We received the following support case number: Case ID: 102996639249 However, we received only an automated acknowledgment. We subsequently followed up through the same support case, explaining the circumstances and requesting assistance. Unfortunately, we have still not received a substantive response or any indication that the issue is being investigated. The Impact of This Unnecessary Delay As an independent developer, I invest significant time, effort, and financial resources into creating educational applications for children. We carefully followed Apple’s submission requirements and proactively provided comprehensive compliance information specifically to prevent unnecessary questions and delays. Yet our application was rejected for information that was already present, and we have now spent more than a week waiting for the review process to resume. This has disrupted our release schedule and delayed our plans for other applications. We fully understand that review times may vary and that Apple must carefully evaluate applications, particularly those intended for children. However, it is difficult to understand why developers should experience such prolonged delays after providing all the requested information correctly from the very beginning. Request for Investigation and Assistance I respectfully request that someone from the Apple App Review Team investigate this situation and clarify the following: Why was our application rejected for information that had already been explicitly provided in the original App Review Notes? Is our resubmitted application correctly queued for review, or could there be a processing issue? Why has the application remained in “Waiting for Review” for more than seven days after resubmission? Can this matter be escalated to the appropriate App Review team to prevent further unnecessary delays? We are not requesting special treatment. We are asking for a fair and timely review of an application for which all requested information was provided from the very beginning. We would sincerely appreciate assistance from an Apple App Review representative in investigating this matter. Thank you for your time and attention. Kind regards, Kalimati Development Team