on Apple Store Connect, i have set language to Australia English, app availability in Aus and NZ only, but the age rating shows Brazil. This gives more errors like requesting me to submit documents related to Brazil.

Message from Apple review team- Guideline 2.1 - Performance - App Completeness Issue Description The app exhibited one or more bugs that would negatively impact users. Bug description: Unable to launch app on iPhone. Review device details: Device type: iPhone 13 mini OS version: iOS 18.5 Next Steps Test the app on supported devices to identify and resolve bugs and stability issues before submitting for review. If the bug cannot be reproduced, try the following: For new apps, uninstall all previous versions of the app from a device, then install and follow the steps to reproduce. For app updates, install the new version as an update to the previous version, then follow the steps to reproduce.

Message from Apple review team- Guideline 2.1 - Performance - App Completeness Issue Description The app exhibited one or more bugs that would negatively impact users. Bug description: Unable to launch app on iPhone. Review device details: Device type: iPhone 13 mini OS version: iOS 18.5 Next Steps Test the app on supported devices to identify and resolve bugs and stability issues before submitting for review. If the bug cannot be reproduced, try the following: For new apps, uninstall all previous versions of the app from a device, then install and follow the steps to reproduce. For app updates, install the new version as an update to the previous version, then follow the steps to reproduce. My rely on top of this message- Hello, The same build I’m able to launch and run through TestFlight in our iPhones. If it is working on my iPhone 11, iPhone 16 and iPhone 15 then it should work in every iPhone. And there is nothing got changed in launch screens, only intro screen I’ve changed as you mentioned that it is not perfect in iPad, since its first release. And this is not the first there’s. This is the third release of the app. Why this much problem is coming in review?

Section 1: Our game was developed using Cocos Creator 3.8.5, written in TypeScript. The team spent nearly two years completing it. Initially, our submission wasn't classified under Guideline 4.3(a). The first four reviews provided normal feedback, which we addressed. However, after a subsequent rejection citing 4.3(a), we considered whether similarities in gameplay concepts, narrative, or art assets might exist. In response, our team introduced unique features not found in other App Store applications. We completely redesigned our original art assets to ensure originality and extensively modified aspects potentially resembling other developers’ work. This included removing all third-party SDK modules except Apple Pay and Sign in with Apple. Despite these significant efforts, we still received a 4.3(a) rejection. We have now iterated over 20 versions but continue to face this issue.  Section 2: Our game’s business logic code (excluding the Cocos engine code) is entirely original and should not duplicate others' work. Could the rejection stem from similarities in compiled JSC files or binaries generated from JavaScript? Would it be possible for the review team to examine our source code for verification? We are deeply committed to launching on the App Store and can provide comprehensive proof of originality, including but not limited to: Full GIT commit history and source code from inception to present  Documentation proving original art creation  Evidence demonstrating unique gameplay mechanics distinct from other developers  Cocos Creator Engine: https://www.cocos.com/creator-download Games developed with Cocos have successfully launched on platforms like WeChat Mini Games and Android app stores in China, where they are well-received by users. Honorable Review Team, could you please conduct a manual inspection of our source code and evaluate the gameplay? We believe Apple—the world’s most innovative technology company—employs highly professional and insightful experts dedicated to delivering unique, high-quality experiences for players. However, the persistent 4.3(a) rejections are concerning, especially since numerous Cocos-based games are approved globally. We’ve revised the game over six months across 20+ versions, yet each rejection cites identical reasoning:  Apple's Rejection Message Translation: Hello, The issues we previously identified still require your attention. If you have any questions, we’re here to help. Please reply to this message in App Store Connect. Review Details Submission ID: 68 bd1e 18-6 EAA-4a 19-976 e-c 7 B2 E1 ff 0 e 44 Date Reviewed: June 28, 2025 Version Reviewed: 2.3.0 Guideline 4.3(a) - Design - Spam We continue to find that your app shares a similar binary, metadata, and/or concept as other apps submitted to the App Store with only minor differences. Submitting similar or repackaged apps constitutes spam, creates clutter, and diminishes user discovery of genuinely new applications. Next Steps Since we do not accept spam apps on the App Store, we encourage you to review your app concept and submit a truly original application with distinct content and functionality. Support Reply in your preferred language if you need assistance. For further support, use the Contact Us module.  Seek advice from fellow developers and Apple engineers on the Apple Developer Forums.  Request an App Review consultation via Meet with Apple (availability varies based on local hours, Tuesdays and Thursdays).  Provide feedback on this process and your review experience by completing a brief survey.

Here is the English translation of your content:  Section 1: Our game was developed using Cocos Creator 3.8.5, written in TypeScript. The team spent nearly two years completing it. Initially, our submission wasn't classified under Guideline 4.3(a). The first four reviews provided normal feedback, which we addressed. However, after a subsequent rejection citing 4.3(a), we considered whether similarities in gameplay concepts, narrative, or art assets might exist. In response, our team introduced unique features not found in other App Store applications. We completely redesigned our original art assets to ensure originality and extensively modified aspects potentially resembling other developers’ work. This included removing all third-party SDK modules except Apple Pay and Sign in with Apple. Despite these significant efforts, we still received a 4.3(a) rejection. We have now iterated over 20 versions but continue to face this issue.  Section 2: Our game’s business logic code (excluding the Cocos engine code) is entirely original and should not duplicate others' work. Could the rejection stem from similarities in compiled JSC files or binaries generated from JavaScript? Would it be possible for the review team to examine our source code for verification? We are deeply committed to launching on the App Store and can provide comprehensive proof of originality, including but not limited to: Full GIT commit history and source code from inception to present  Documentation proving original art creation  Evidence demonstrating unique gameplay mechanics distinct from other developers  Cocos Creator Engine: https://www.cocos.com/creator-download Games developed with Cocos have successfully launched on platforms like WeChat Mini Games and Android app stores in China, where they are well-received by users. Honorable Review Team, could you please conduct a manual inspection of our source code and evaluate the gameplay? We believe Apple—the world’s most innovative technology company—employs highly professional and insightful experts dedicated to delivering unique, high-quality experiences for players. However, the persistent 4.3(a) rejections are concerning, especially since numerous Cocos-based games are approved globally. We’ve revised the game over six months across 20+ versions, yet each rejection cites identical reasoning:  Apple's Rejection Message Translation: Hello, The issues we previously identified still require your attention. If you have any questions, we’re here to help. Please reply to this message in App Store Connect. Review Details Submission ID: 68 bd1e 18-6 EAA-4a 19-976 e-c 7 B2 E1 ff 0 e 44 Date Reviewed: June 28, 2025 Version Reviewed: 2.3.0 Guideline 4.3(a) - Design - Spam We continue to find that your app shares a similar binary, metadata, and/or concept as other apps submitted to the App Store with only minor differences. Submitting similar or repackaged apps constitutes spam, creates clutter, and diminishes user discovery of genuinely new applications. Next Steps Since we do not accept spam apps on the App Store, we encourage you to review your app concept and submit a truly original application with distinct content and functionality. Support Reply in your preferred language if you need assistance. For further support, use the Contact Us module.  Seek advice from fellow developers and Apple engineers on the Apple Developer Forums.  Request an App Review consultation via Meet with Apple (availability varies based on local hours, Tuesdays and Thursdays).  Provide feedback on this process and your review experience by completing a brief survey.

Our game was written by Cocos Creator version 3.8.5 ‌TypeScript, which took the team nearly 2 years to complete. At the beginning, my application was not defined as 4.3a. The first four reviews were all normal feedback questions. We revised the questions. After the last review rejected 4.3A, we also suspected that the reasons such as game creativity, game copywriting and game art might be close to other applications. Then our team added functional innovations that other applications in the Apple Store didn't have, and the original art was original. We created new art again because of 4.3a, and also revised many places that may be similar to other developers, including that we removed all SDK modules except Apple Pay and Apple Login, and it also showed that 4.3a refused, and we have revised no less than 20 versions or failed. Our business code except the game engine code is newly developed by us and should not be duplicated with other developers' code. Is it because the JSC file and binary file output by JavaScript code are similar to those of other developers? Can we check our original code? We really want to put it on the Apple Store. We guarantee that the game was originally written. We can provide any proof, including but not limited to (GIT code submission records and codes from the beginning to today, art original proof, proof that the game mode innovation ability is not consistent with other developers' concepts, etc.) Cocos creator Engine Address: https://www.cocos.com/creator-download We have been put on the shelves in app stores such as WeChat applet and Android, and we are deeply loved by users in other channels. Dear audit, can you manually check our game code and look at the game to experience it? I believe that as the greatest technology company in the world, Apple's official staff are very professional, knowledgeable and innovative, so that Apple players can get a unique and high-quality experience. However, this repeated 4.3a refusal makes me very suspicious. So many games that use cocos game engine in the world are on the Apple store, why do we independently write the rest of the code except the game engine? Every time the reason for refusing is this passage, we have revised it for half a year, and no less than 20 game versions have been changed in half a year. Hello, The issues we previously identified still need your attention. If you have any questions, we are here to help. Reply to this message in App Store Connect and let us know. Review Environment Submission ID: 68bd1e18-6eaa-4a19-976e-c7b2e1ff0e44 Review date: June 28, 2025 Version reviewed: 2.3.0 Guideline 4.3(a) - Design - Spam We noticed your app still shares a similar binary, metadata, and/or concept as apps submitted to the App Store by other developers, with only minor differences. Submitting similar or repackaged apps is a form of spam that creates clutter and makes it difficult for users to discover new apps. Next Steps Since we do not accept spam apps on the App Store, we encourage you to review your app concept and submit a unique app with distinct content and functionality. 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. Request an App Review Appointment at Meet with Apple to discuss your app's review. Appointments subject to availability during your local business hours on Tuesdays and Thursdays. Provide feedback on this message and your review experience by completing a short survey.

Hello everyone, my app is designed to help people sleep. It has been rejected multiple times due to issues with version 1.4.1 during the submission process. However, the app simply evaluates users’ insomnia and anxiety status based on their responses to questions and provides some relaxation methods. It does not involve any medical-related content. The reviewer provided screenshots of the assessment results page and some relaxation techniques. How should I handle this issue?

Hello everyone, my app is designed to help people sleep. It has been rejected multiple times due to issues with version 1.4.1 during the submission process. However, the app simply evaluates users’ insomnia and anxiety status based on their responses to questions and provides some relaxation methods. It does not involve any medical-related content. The reviewer provided screenshots of the assessment results page and some relaxation techniques. How should I handle this issue?

Hello everyone, my app has been repeatedly rejected due to issue 1.4.1. However, the app merely assessed the state of insomnia and anxiety based on the user's responses, and then provided some relaxation methods. It did not involve any medical-related content. How can I solve this problem?

Hello Apple Team, Our app uses essential custom payment flows such as: One-time full payments Monthly recurring payments (up to 12 months) Custom 6 month recurring subscriptions Deposit + fixed date balance payments Deposit + monthly recurring payments Deposit + 6 month recurring payments These billing structures are currently not supported by In-App Purchase (IAP) due to technical limitations (e.g., split payments, custom intervals). We’d like to understand what approved alternatives are available for supporting such payment models within App Store guidelines. Could you please advise on any compliant options or architectures that would allow us to implement these flows? Thank you, Vidya

Went through several rounds of rejections this week and finally the app was approved. Unfortunately I just discovered that my Subscriptions and Localization are still "In Review" and "Waiting for Review". It's baffling to me that either the reviewer could overlook this or the system allows for this scenario. All issues flagged in the review process were addressed as requested too. I've already emailed and called about this but they have no eta on when it will be resolved. This seems entirely preventable and it's very frustrating as this has delayed my release. Is there anything else I can do to get this resolved?

Hi, One of my application doesn't get rating updates on AppStore. On https://appstoreconnect.apple.com/ Ratings and Reviews page I see that app got 19 Ratings with average 3.8 out of 5. But on AppStore it just have 5 ratings with average 3.4 out of 5. See attached screenshots: AppStore: AppStore Connect: . Please help me to figure out with this issue and hope we can fix rating on AppStore page accordingly to AppStore Connect. Thanks, Alex

So from the documentation of apple for implementing the in app review feature we can't test it without releasing our app to App Store since in test flight it doesn't approve the api call is there a way to test it where we can check if the rating or review entered is visible on a console so that we can test the end to end work flow? this happens in android in internal test track? is there any provision for this in iOS?

Hello Experts, I am in need of your help with this feedback from the App Reviewer. Issue Description: One or more purpose strings in the app do not sufficiently explain the use of protected resources. Purpose strings must clearly and completely describe the app's use of data and, in most cases, provide an example of how the data will be used. Next Steps: Update the location purpose string to explain how the app will use the requested information and provide a specific example of how the data will be used. See the attached screenshot. Resources: Purpose strings must clearly describe how an app uses the ability, data, or resource. The following are hypothetical examples of unclear purpose strings that would not pass review: "App would like to access your Contacts" "App needs microphone access" Feedback #2 "Regarding 5.1.1, we understand why your app needs access to location. However, the permission request alert does not sufficiently explain this to your users before accessing the location. To resolve this issue, it would be appropriate to revise the location permission request, specify why your app needs access, and provide an example of how your app will use the user's data. To learn more about purpose string requirements, watch a video from App Review with tips for writing clear purpose strings. We look forward to reviewing your app once the appropriate changes have been made." May I know how can I update my purpose string? I appealed on the first feedback by explaining what is the purpose of it but got the Feedback #2. TYIA!!

Hello, I submitted an appeal after my app was rejected under Guideline 4.3(a). It has now been over 5 days and I have not received any reply from the App Review Team. Has anyone experienced similar delays recently? Does Apple respond eventually or is there something else I should do? Thank you in advance.

An update to my app has been rejected under Guideline 2.1 - Performance - App Completeness, citing that only a blank screen appeared on launch. I cannot recreate this bug. I have, on this exact device and iOS version that the reviewer used (iPhone 13 mini, iOS 18.5): Downloaded the app from TestFlight and successfully launched Launched in release mode Launched as a new install AND as an upgrade Launched with no internet, good internet and slow internet I have asked the reviewer for any crash logs and more detail about the testing setup that led to this blank screen on launch, and no extra information was provided at all, just another screenshot of the launch screen. Where do I go from here? Any advice would be hugely appreciated.

Its been over a month for 3 of my Apps still waiting for review (2 of them are already listed on App Store and the other 1 is new). I wrote to the support the situation and asked for the reason, but still no response. What could be the reason and what should I do ?

Dear Apple Review Team, Greetings! We are a growing development team, and our recently submitted app “VIVA LIVE” (App ID: 6450330971) has been in “Waiting for Review” status for more than 13 days. As a small business, this application is crucial to our current operational goals and represents the collective effort and expectations of our entire team. We fully understand and respect the rigorous and complex nature of Apple’s review process, and we are ready to cooperate with any required changes or improvements. However, the extended review time has begun to impact our launch schedule and has put significant pressure on our developers. We therefore kindly ask whether there might be any questions or issues with our submission that we could address or clarify to help move the review forward. We sincerely hope you can give our request some attention so that we may bring our product to users as soon as possible and showcase the hard work we have invested. We greatly appreciate your time and look forward to your feedback. Thank you very much. Best regards, Entity Name: NEXTORN PTE. LTD Team ID: QJGHYXFBCL App Name: VIVA LIVE App ID: 6450330971

Dear Apple Review： I submitted my app on May 15th, and two weeks later, the app was still in the pending review status. So on May 28th, I deleted the app and resubmitted it. I resubmitted my app on May 29th, and as of today, June 21st, the app is still in the pending review status. I submitted another app in June, which has already been reviewed and is now live on the store, but this particular app remains in the pending review status.During the review period, I also emailed multiple times for inquiries, but I have not received any feedback yet. I would greatly appreciate it if you could look into the status of my submision and provide any updates or guidance regarding the next steps. Thank you for your time and supportl Best regards.

Hello, I’m an individual developer who received a termination notice for my Apple Developer account almost 30 days ago. I have submitted multiple appeals through the official App Review Board form and follow-ups through Developer Support, but I haven’t received any response. I’ve done everything possible to comply, including acknowledging any concerns raised and confirming that I will not repeat any mistakes. I’ve also stopped distribution of the app in question and committed to focus only on compliant development moving forward. With the 30-day deadline approaching and no answer, I’m extremely concerned and frustrated. I’m asking here because I have no other channel left to get a human response or confirmation that my appeals are being reviewed. I understand the importance of Apple’s rules, and I fully support fair enforcement. But complete silence in such a critical matter is very hard to handle for a small developer. If anyone from Apple sees this, please help escalate the case or provide guidance. I just want a fair chance to continue working within the platform. Thank you.