4.3

Hello, Thank you for your efforts to follow our guidelines. There are still some issues that 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: 10286862-58d0-4abf-a767-24b885a8a25c Review date: June 17, 2024 Version reviewed: 1.0.0 Guideline 4.3(a) - Design - Spam 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. 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. 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 Creat

Greetings, We have been rejected in the review of our App for a code non-compliance with 4.3 Design guidelines. Our App appears to be similar to others, and indeed it is similar in functionality and appearance. The others that are similar have been developed by us as well, these being customisations that are specifically targeted at the companies or accounts we deal with. The truth is that we have gone through several reviews of the other Apps before when we submitted them for publication at the time. We know that there are other development companies that customise Apps for different brands and in these cases there has been no reason for rejection by the Apple Store. We are beginning to think that there may be certain factors that are directly influencing the rejection of this App: The mockups or screenshots we are using are similar to those of another App we have published with the same functionalities. The backgrounds of the App have a gem of colours similar to that of the other App. And now we wo

We have published an app to show biblical information from a book God's Word written in the stars for all constellations and sub-constellations. This is not a star gazing app and we are not duplicating any content whatsoever. We are building the sky image, the constellation images by ourselves and the content is from the above mentioned book. We have published the app 2-3 times but every time we get rejected owing to following design guidelines: 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. Guideline 5.2.1 - Legal - Intellectual Property Any help on this is much much appreciated.

Hello, I'm almost mad with the AppStore review. Our application was first published on AppStore(iOS) last month, version 2.2.5 is our first online version. After we noticed some bugs and fixed them, we submitted new version to AppStore, tried to fix the bugs of our application. But the reviewer always give us rejection, the reason is 4.3 - Design, said our application is spam. I can't understand, because our new version is the same with the online version 2.2.5. We just fixed some bugs. The rejection keeps 3 times, can you tell me what I can do to against this unreasonable condition? And another thing is the MacOS application. The reviewer said our application requires user to right-click the menu bar to quit our application. So we made change and made users can quit the application by clicking the red button on the application window like all other applications. We also uploaded a picture and noted this change in the submission. But the reviewer rejected it again, gave us the same reason. I can feel

Hello, I recently submitted my app to the Apple Store and received a rejection under Guideline 4.3(a) - Design - Spam, stating that my app is similar to others on the store. However, my app has a unique feature set, offers more functionality and content than competitors, and is completely free with ad monetization, unlike most similar apps that require subscriptions. I have spent five months developing this app from scratch, ensuring it provides an original and valuable experience for users. I did not use an app template or repackaged code, and my app is not a reskinned version of any existing app. I genuinely believe it brings meaningful differentiation to the market. I would appreciate any guidance on how I can better communicate my app’s uniqueness to the review team or what specific aspects I should adjust to comply with Apple's guidelines. Thank you for your time and support.

我们收到贵团队的审核反馈4.3(a) ，对此我们高度重视并认真核查。我们理解苹果对应用生态原创性的严格要求，但我们的 App 完全由团队独立开发，并未复制或模仿其他应用。 独立原创开发，非模板应用 • 本 App 100% 由我们团队自主开发，未使用任何第三方模板或克隆代码。 • 所有 UI 设计、交互逻辑、功能实现均为 原创，不存在与其他 App 的刻意相似。 核心功能差异显著 我们的 App 在以下方面具有独特创新：【交友】模块「通过（RTC）技术提供在线语音/视频聊天服务，以用户允许的个人信息匹配到对应用户进行音视频聊天，支持视频聊天场景下文本输入的交互」，以独特的用户操作界面和交互方式区别于市场同类交友App。 愿意配合调整，请求具体指导 如审核团队认为我们的 App与其他应用存在相似性，恳请提供关于本APP更具体的问题点，以便我们做针对性优化。我们非常愿意配合调整，确保符合苹果的审核标准。 感谢您的理解与支持，期待您的进一步反馈！ app #1561289219 We have received your feedback regarding Guideline 4.3(a), and we take it very seriously. We fully understand Apple’s commitment to maintaining originality and a high-quality app ecosystem. Therefore, we would like to clarify that our app is entirely independently developed and not copied or cloned from any other application. Independently Developed – Not a Template-Based App • This app is 100% developed in-house by our team. We have not used any third-party templates or cloned source code. • All UI designs, interaction logic, and functionality are original

As per the Apple review guidelines 4.3, multiple bundle Ids of the same app can be rejected by apple. Can you please confirm if there is any way to appeal Apple to allow more than one app with only change in theme and enabling / disabling few features based on permissions?

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

4.3 Spam allegation between early version FREE, Open Source API beta apps and latest version of the PAID app which has contractual PAID API incorporated along with In-App Purchase options. The Reviewers are not accounting for the difference between the free open source API and the paid licensed API. What to do to convince them?

Bear with me, this sounds like an FAQ but my specific situation is a little less frequent.I am working on an architecture in which I have the same front-end (entrypoint Storyboard, `AppDelegate`, top-level `ViewController`, Launch Storyboard, Info.plist, sound & image resources) for multiple apps. That is, I append the app-specific code to the common front-end.So the question is: how best to manage independent development of the front-end and the multiple back-ends. Including SCM. Some ideas:Libraries, static or dynamic - a non-starter because the common code-base includes Storyboards and assets.Completely separate projects, with the individualized apps including (by reference) the common code.Single project, separate targets.Separate sub-projects in a single Xcode Project.Separate projects inside a single Xcode Workspace.One criterion would be how well Xcode and Git[Hub] deal with the separation of code bases. I have had mixed results with Xcode getting out of sync with git. Advice welcome. I've been cut

I have stuck with 4.3 policy for around 1 month. I don't understand Apple reviewer kept hitting me with 4.2 policy without further explain the problem. I do refer to other app and copy some code from stack overflow, how do I know which part is causing the problem. My app provide better soothing sound quality and the UI is all different. Thanks, kindly advise .....

I have an Application in Flutter that receives data from an API on Laravel, and I tried to upload my Application to an App Store and Apple informed me that since I offer Login with Facebook and Google, I also need to offer Login with Apple. So, we tried to implement the login with Apple ID, but we couldn't because of the Laravel version. Our application needs the API on Laravel 5.8, PHP 7.1, Socialite 4.3+. And apple requires a newer version of Laravel and PHP, so we are unable to continue. Can someone help me how to proceed in this case?

Due to our app having different government clearances in each geographical region, we are required to have a different version in each region. While the apps are all fundamentally the same, is there any reason we can't have: OurApp US - available in US OurApp UK - available in UK only OurApp EU - available in EU only While I understand how to implement this, there is concern that the subsequent submissions might be flagged incorrectly by the 4.3 Spam rule. Users would never see more than one version of our app in their region's App Store. Does anyone have any knowledge or experience here? Is this kind of release strategy acceptable?

Hello Everybody,We develop a Math app, it snap a problem and get solution in PDF format.After waiting almost 40 days, reviewer reject app with below message. But it is our first Math app.Thank you for your response.In regards to the 4.3 issue, we continue to find that this app duplicates the content and functionality of other apps submitted by you or another developer to the App Store, which is considered a form of spam.Please note that deliberate disregard of the App Store Review Guidelines and attempts to deceive users or undermine the review process are unacceptable and is a direct violation Section 3.2(f) of the Apple Developer Program License Agreement. Continuing to violate the Terms & Conditions of the Apple Developer Program will result in the termination of your account, as well as any related or linked accounts, and the removal of all your associated apps from the App Store.Best regards,App Store ReviewOver 5 days we ask everday in resolution center same question which app is dublicate

So I've got a lot of apps that have been consolidated into a container app. Like many of you, I got the 4.3 messages. After some grimacing, I can see the silver lining - for devs, for users, for Apple. But I really wish iTunes Connect would add a forwarding option in our Removed from Sale apps that redirects to the container app. I added a bug-report (feature request) for this already, but I'm hoping more devs ask for this. Reasoning...1. There's gotta be millions of dead app store links already floating around the internet. Why have those links go to this message This app is no longer available in your country's store, when it can just jump to a live app? We can update our own websites, but some blogger that wrote about an app 3 years ago, isn't going to update their links. 2. Its also a dead end for actual App Store users going through their old Purchases. Doesn't need to be. Let us recapture those users. 3. Consolidation was / will be a big ask for many of us. And like I said, I can see the benefi