“4.3”

I'm hoping someone can help me get clarity on my app submission for LinkUp, an iMessage-native group scheduling app. Here's the timeline: • Initial rejection (~1 month ago): Rejected under 4.3(a) for duplicating functionality of other apps • I updated screenshots, app description, and submitted again • For the past 2 weeks the app has been stuck with no meaningful response from App Review • I have called Apple support, submitted messages through the Resolution Center, and filed an App Review Board appeal — but I have received no confirmation email for the appeal and it does not appear on my developer support request page What LinkUp actually does: it lets friend groups coordinate availability entirely inside iMessage. Users send a schedule card as a message bubble, and participants vote on availability directly in the conversation thread — no redirects, no external app required. The heatmap updates in the bubble as people respond. To my knowledge, nothing on the App Store does this.

App ID: 6767989183 was rejected for Guideline 4.3(a) Spam. I resubmitted, filed an appeal, and booked a call with App Review – got zero confirmation on any of it. Has anyone managed to escalate past this point and actually reach someone? What worked for you?

Hello, I'm hoping someone from the App Review team can look into this situation, which has specific context that I believe makes it worth a careful look. Thank you in advance for your time. I'm hoping someone from the App Review team can look into this situation, which I believe has specific context that makes it worth a careful look. My app YADA: You've Already Met (App ID: 6759586097) has been in Waiting for Review since Wednesday May 6 at 7:44 PM ET - now over 96 hours. I have an open support case (20000112508151) filed Friday with no response yet. I'm not writing simply to flag the wait - I want to explain why this submission deserves a thoughtful second look on the merits. When YADA was submitted for TestFlight beta review, it was flagged under Guideline 4.3(b) for the same reason as the App Store rejection. I appealed, explained the differentiating mechanic, and an Apple reviewer evaluated the argument and approved the app for external testing. That approval is on record. I'm asking for consist

Hello everyone, I’m looking for advice from developers who successfully resolved a Guideline 4.3(a) “Spam” rejection in a legitimate account migration scenario. Situation: I originally developed and submitted my app under my personal Apple Developer account. Later, after creating a business/company, I opened a business Apple Developer account because I wanted the app published under the company instead. The original app on the personal account was removed before submitting on the business account. I changed the Bundle ID and created a new app entry under the business account. However, the business-account submission was rejected under: “Guideline 4.3(a) - Design - Spam” with the message about “similar binary, metadata, and/or concept.” I appealed and explained that this is the same legitimate app/business transitioning from an individual account to a company account, not a spam network or template cloning situation. The appeal was denied. What makes this more confusing is that the app on the

Issue Description We noticed the app shares a similar binary, metadata, and/or concept as apps submitted to the App Store by other developers, with only minor differences. Next Steps Since we do not accept spam apps on the App Store, we encourage you to review the app concept and submit a unique app with distinct content and functionality. 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 guideline 4.3.

My app has been rejected three times under Guideline 4.3(b). I'm seeking guidance from anyone who has navigated a similar situation. The app generates real-time personalized content by combining data from five iOS frameworks — WeatherKit, EventKit, HealthKit, Contacts, and CoreLocation — with an AI API. The generated output directly references the user's actual current weather, actual calendar events, and actual health patterns. No content library exists. Every output is unique. My competitors in this space do not use this method and mine is seriously impressive and can be very beneficial to the user. No other app on the App Store integrates these five frameworks together at content generation time. A 2-minute test confirms this: grant permissions, generate content, and observe your real weather and calendar data in the output. My concern is a process inconsistency. The app was initially reviewed and rejected for four technical issues. Guideline 4.3(b) was not cited. All four issues were res

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

Hello Apple Developer commuinty! We have been developing a VPN client app with unique protocol for quite a while, and now it have come to publishing it in App Store/Google play. I know that publishing a VPN service requires organization(which i cant register because of my life situation), that why i have choosen to make a client. User is NOT necessarily required to use official hosting, theres an option of importing external key. App itself, doesnt contain any hardcoded server credentials and such, but it does have option to get free config from website by click. For some reason, my app review have not gone well. Apple have claimed my app have violated Guidelines 4.3(a) and 5.4. In all of my respect for App Review Team, but claim on Guideline 4.3(a) - Spam is completely ridiculous! App was completely written from the ground, not only including protocol, but the design itself. The MONOGON style, is unique application style which no other app on app store have seen(featuring dotted ASCII style

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: f14dec0a-1269-438e-b483-6d806b3d17bf Review date: April 13, 2026 Review Device: iPhone 17 Pro Max Version reviewed: 1.0 Guideline 4.3(a) - Design - Spam Issue Description We noticed the app shares a similar binary, metadata, and/or concept as other apps you already submitted to the App Store, 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 the app concept and submit a unique app with distinct content and functionality. 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 Cre

Hello App Review Team, I am writing to request further assistance regarding the rejection under Guideline 4.3(a) (Design – Spam). The issue appears to be related to another app that I previously submitted from a different developer account. Unfortunately, I no longer have access to that previous account. I lost my phone, and the SIM card associated with that Apple ID has been permanently blocked. As a result, I am unable to receive verification codes or recover access to the account. I understand the concern about duplicate apps on the App Store and fully respect Apple’s guidelines. To resolve this issue, I would like to request one of the following: Guidance on how I can verify ownership of the previous account so I can take appropriate action (such as removing the older app or restricting storefronts), or Assistance from Apple in removing or disabling the duplicate app associated with my inaccessible account, or Any alternative solution you recommend to comply with Guideline 4.3(a) and pro

After months of hard work developing an app with unique mechanics and a distinct user experience, we recently faced a rejection under Guideline 4.3(b) (Spam/Saturated Category). The feedback we received stated that there are already enough of these apps on the App Store. While we completely understand Apple's need to filter out low-quality clones, it feels like this guideline sometimes overlooks genuine originality. The most frustrating part for independent developers is that the category you fall into seems to matter more than the actual value your app provides. Whether the app is positioned in lifestyle, entertainment, or productivity, a rigid category quota can prevent reviewers from truly seeing the unique features we built. This creates a significant hurdle for new entrants and makes it incredibly difficult for fresh ideas to break into established categories. It feels less about the quality of the application and more about timing—as if early arrivers have a permanent advantage over newcomers,