“4.3”

Hello everyone, I’m developing a work management app using React Native/Expo for multiple companies. The apps share a common codebase and similar core functionality, but each company has its own app name, logo, bundle ID, and company-specific data. Each company wants a separate app publicly available on the App Store so users can search for and download it. Private distribution through Custom Apps or a single shared app with a company selector would not meet their requirements. I’d like to understand how App Review Guidelines 4.3(a) and 4.2.6 apply to these two scenarios: 1. All apps published under one organization’s developer account Our company would develop and publish all client apps under our own Apple Developer Program organization account. Is there a compliant way to support this model? What requirements would each app need to meet? 2. Each app published under the client company’s own developer account Each client company would enroll in the Apple Developer Program and publish its app under i

Hello, I’m looking for advice from developers who may have encountered similar App Review situations. I have an iOS game (“Next Run Game”), a fantasy roguelike RPG. App version 1.0.13 was reviewed and approved by App Review, but it was not released publicly on the App Store. Later, I submitted version 1.0.14. This update contained only minor changes: small balance tweaks bug fixes localization text fixes No changes were made to metadata or presentation: app name icon screenshots description branding overall concept After submitting version 1.0.14, the app began to be rejected under: Guideline 4.3 (Spam) later also Guideline 4.1 (Copycats) The review messages are generic and state that the app or its metadata “appears to be misrepresenting itself as another popular app,” but no specific example, reference app, or concrete issue has been provided. What is confusing to me: The same app (version 1.0.13) was previously approved by App Review. Metadata did not change between the approved and rejected submi

Hello App Review team and fellow developers, We’re seeking assistance with Communicator Pro, version 2.0.2 (App Store ID: 6514321736). Here is the timeline: September 29: Build 102 was rejected under Guideline 4.3(a). App Review identified overlapping storefront availability with another app we submitted. Apple also requested a physical-device video demonstrating NFC functionality. The response included an “Extended Review” warning. October 1: We replied that we had removed the other app, Communicator Cloud, from the App Store and attached a video demonstrating NFC tag scanning and assignment on a physical iPhone. After receiving no further response, we withdrew the previous submission and resubmitted the same build. The current submission remains “Waiting for Review.” We contacted Apple Developer Support on October 9 and October 14 but have not received a response so far. We can provide case numbers privately through an appropriate Apple support channel. We understand that additional verification ca

I’m attempting to download this update. I’m using an iPhone X to the Series 3 watch and it’s been longer than 120 minutes since the download completed. It’s been sitting at “verifying” for the last 90 minutes and it seems to be stuck there. I’m running all Apple networking and it’s very quick.What‘s a “normal” download and install timeframe?Thank you for any and all help / suggestions

Wanted to check if there's really a issue for a genuine company going to release a white label solution( with different branding, logo, look and feel) for their product using same apple store account, app template but with different bundle id?

Hi all Our App was rejected for being suspected Spam, copied from another entiy's App witht he following narrative: We noticed your app shares a similar binary, metadata, and/or concept as apps submitted to the App Store by other developers, with only minor differences. We explained this on the form, but the case is not being progressed, jsut ignored. Is there a good way forward to resolve this that is good for Apple as well. Here is our response in the Form: Dear App Review, Thank you for flagging this point and we fully understand and appreciate your concern for protection of our App from being put to unauthorised use. This App and has been developed solely for us and on our instruction and under our direction. As you have noticed, our developer submitted our App to your App Store years ago and it was available for several years from this account. Then some months ago we decided with the developer to move it to our own account. And as you also noticed, some small changes to simplify the flow were made inte

Hi everyone, I’m currently working on a project based on the Telegram iOS open-source code. My goal is to build an unofficial Telegram client with Telegram’s permission (they have publicly allowed third-party clients under their open-source license). My app includes unique new features and UI improvements that are not present in the official Telegram app. Essentially, it’s Telegram plus additional features — built from the official source, but extended significantly. However, when I try to submit my app to the App Store, Apple rejects the build under Guideline 4.3(a) - Design - Spam with this message: “We still noticed your app 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.” I completely understand Apple’s intent to prevent low-effort clones or spam apps. However, in my case, this is

Hello Apple Team, We are seeking assistance regarding our app 健康行動go (App ID: 1437488996, Case ID: 20000146721382). Timeline: August 14: We received feedback regarding Guideline 4.3(a). August 21: We resolved the issues by providing detailed business differentiation, UI comparison documentation, and submitting an updated build. Status: The submission has remained in Waiting for Review since August 21. Today, August 27, 2026, is our scheduled public release date with external commitments. Could an Apple representative please check if our submission is held in a specialized queue and assist in escalating it to the App Review team for review? Thank you very much for your time and support.

Hello, My app Tall - App de rencontre (App ID: 6761081326) has been rejected 4 times under Guideline 4.3(b) Design Spam. The App Review Board also upheld the rejection (Appeal Ticket APL411770). I fully understand the dating category is saturated. However, my app has unique mechanical features that do not exist on any other dating app on the App Store: MANDATORY HEIGHT GATE: During registration, women below 1.75m and men below 1.80m are blocked and CANNOT complete registration. This is hard-coded into the onboarding. It is not an optional filter. Users who do not meet the height criteria simply cannot use the app. DOOR-FRAME HEIGHT VERIFICATION: Users must submit a full-body photo standing barefoot under a standard door frame to verify their height. Unverified users see all other profiles blurred. This trust-and-safety mechanism is entirely unique. THE BAKERY: A curated, time-limited daily drop of compatible profiles replacing infinite swipe. This is an anti-swipe paradigm designed to prioritize qual