App Review told me that my app can not be marked as a blood alcohol content calculator without the appropriate hardware. They refer to the expression "Promillewert", it is German and stands for "per mille value". They also referred to to the Guideline 1.4 (Physical Harm).
Is the way how I used the words the problem or the app itself? My idea is to use the expression "Geschätzter Promillewert"/"per mille value estimation", but I do not want to miss the App Review again.
App Review
RSS for tagApp review is the process of evaluating apps and app updates submitted to the App Store to ensure they are reliable, perform as expected, and follow Apple guidelines.
Posts under App Review tag
200 Posts
Selecting any option will automatically load the page
Post
Replies
Boosts
Views
Activity
Hi,
I work for UK company Lendable: https://www.lendable.co.uk/about
Lendable Ltd, company number 08828186 (previously Feather Media Ltd). Authorised and regulated by the Financial Conduct Authority (FCA). We are registered with the Information Commissioner’s Office in compliance with the Data Protection Regulations 2018 under registration ZA041704. Registered office at Lendable, Telephone House, 69-77 Paul St, London, EC2A 4NW.
At the moment our Zable app is being constantly rejected for Guideline 3.2.1 (viii) - which I quote below:
Business - Other Business Model Issues - Acceptable
We continue to notice that your app provides loan services but the domains listed on the app's Product Pages are not clearly under your control or ownership. Since users may use these domains to contact you to request support, the domains used on the Product Page for loan apps must be under your control or ownership.
Next Steps
Update the Product Page metadata in App Store Connect to only include domains that are associated with Apple Accounts registered to your developer account.
Please note that apps used for financial trading, investing, or money management should be submitted by the financial institution performing such services, as required by App Review Guideline 3.2.1(viii).
Zable is a fully owned Trading name of Lendable Operations Ltd. We fully own the name, domain, website and app associated with the name Zable (zable.co.uk and zable.com).
zable.co.uk universal links are verified within our developer account and the app responds correctly to opening them.
In the app review process we have provided legal documents showing our company structure and how Zable is a fully own trading name of Lendable Operations Ltd.
We have asked multiple times what further evidence we need to provide to ensure the trading name Zable is allowed to provide loan products for Lendable Operations Ltd on the app store. We are simply told the domain is not verified.
It has been an extremely frustrating process. How further can we verify the domain? What do we need to do?
Please help.
Hey everyone,
I’m really hoping someone here can share some advice because I’m feeling stuck. My game was recently rejected from the App Store for being classified as "spam," but I honestly have no idea why. I built everything from scratch—3D models, environments, UI, and all the code—nothing is copied or templated from any other game.
I first tried replying to the rejection email, but I kept getting the exact same automated response with no clarification. A week ago, I also submitted an appeal, but I haven’t heard anything back yet.
Since I wasn’t sure what else to do, I just submitted a new version of my game and appealed again. But now I’m wondering—does this even help? I don’t get any confirmation emails when I submit an appeal, so I don’t even know if anyone is actually reviewing it.
Has anyone else been through this? Any advice on how to get a real response from Apple or figure out what’s wrong? Would really appreciate any insights!
Thanks in advance!
Topic:
App Store Distribution & Marketing
SubTopic:
App Review
Tags:
App Store
App Review
App Store Connect
Dear Apple Review Team & Develpers! Could anyone clarify why Apple Reviewers, when rejecting the app under Guideline 4.3(a) - Design - Spam, do not provide any specific details? Each time my app is rejected, I receive a generic, automated response. In contrast, I provide detailed information and request clarification on the exact reasons for the rejection- specifically, what aspects of the app do not meet Apple's requirements. However, the responses I receive are always the same standard message without any useful details.
Am I correct in understanding that the review process is entirely automated, with no human evaluation, resulting in repetitive, unhelpful replies? I would appreciate a more detailed response that can genuinely help me address the issue and ensure my app complies with Apple's guidelines.
Here is their standard generic response to any my reply where I provide details and ask questions, but Apple Reviewer answer alsway with the same text:
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.
Specifically, this app appears to be identical to apps already on the App Store from other developers.
Apps that duplicate content or functionality create clutter, diminish the overall experience for the end user, and reduce the ability of developers to market their apps.
Next Steps
It would be appropriate to revise your app to provide a unique experience or submit a new app that does not duplicate the content and functionality of other apps on the App Store.
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 App Review Guideline 4.3(a).
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.
Provide feedback on this message and your review experience by completing a short survey.
Review Environment
Submission ID: c4a62f43-b02a-40f0-b763-e00fcc996512
Review date: March 04, 2025
Version reviewed: 11.4.1202
Hello,
My APP is under revision since december 5, is it normal?
What can I do to know what's happening? I don't have any notification since then.
Thanks
I normally get a response back within 1-4 hours. It's been over 36 hours and still nothing. anyone else?
Dear App Review team,
My app Goodie AI (Apple ID 6741483227) has been flagged as violating Guideline 4.3(a) - Design - Spam.
I thought I would reach out to the team to explain that Goodie AI is an entirely original concept, and would seek guidance on if we misunderstood what specifically the problem with the submission is.
DESCRIPTION
Please suggest next steps? We've already appealed, and have resubmitted the app. Thanks!
SCREENSHOTS ATTACHED
Topic:
App Store Distribution & Marketing
SubTopic:
App Review
Tags:
Design
App Store
iOS
App Review
Hello everyone,
We’re facing an ongoing issue with our app being rejected under the 4.3(a) Spam guideline, and we’re hoping the community can offer some advice on how to resolve it.
Our app is a free sports application that provides real-time score updates. It also features commentary from several top contributors and journalists. We offer exclusive features that are completely original—we don’t replicate or borrow any designs or functionalities from other apps on the App Store. Additionally, the app includes games that we have personally researched, designed, and developed from scratch without using any third-party libraries.
We were flagged under 4.3(a) Spam after a very minor update, which primarily focused on fixing some interface-related bugs. Despite these minimal changes, our app was rejected under the Spam guideline.
To address this, we have sent detailed information to Apple Review, including our development roadmap, screenshots of design versions, and even git logs to demonstrate the development process of our team. These materials clearly show that our app is not a repackage or spam app, as suggested. However, despite all these efforts, the responses we’ve received seem automated, and we have not been given clear explanations or a resolution.
We’ve spent a lot of time trying to troubleshoot, removing dead code, and restructuring the project (as Apple claimed we might be sharing binary files with a mysterious app...), but all efforts have been in vain.
I’m not sure how to resolve the issue of 'sharing similar binaries, metadata' with other apps if that’s the case. Could this be because I’m using Flutter and package on pub.dev like many other developers ? We’re at a point where we don’t know how to proceed. What steps should we take next to resolve this issue? Has anyone here faced a similar challenge and found a way to get a more detailed response from Apple Review? Any advice would be greatly appreciated!
Thank you for your time and help!
Kind regards,
Michael
Having a hard time understanding what to use to setup membership plans for a social app (think tinder) that has 3 and 5 years access for one-time use (or even if we allow multi-use but one at a time). The maximum subscription length I see is 1 year so that is out. For non-consumable it says that is lifelong which is problem as plan lengths are 3 and 5 years access only. We are not giving life long access with these plans. So consumable seems to allow the time duration IPA needed. Is this correct? An if it matters this is multi-platform app where users login with their email/pass to android / iOS / our website.
Topic:
App Store Distribution & Marketing
SubTopic:
App Store Connect
Tags:
App Review
In-App Purchase
Hello,
We have implemented support for our app to work with MDM. Basically the app needs to read the custom configuration with UserDefaults.standard.dictionary(forKey: ‘com.apple.configuration.managed’) in order to be functional when in an MDM. The issue is that in the app review process we are told that:
"Guideline 2.1.0 - Information Needed
We are still unable to access the app's Mobile Device Management (MDM) functionality.
Provide a demo MDM profile and corresponding login credentials that we can be used to access the MDM features and functionality."
How do we create a demo MDM profile? Our app only needs to be passed configuration information and we have used Apple Configurator to create a profile, we have added information but it still doesn't work.
Here is an example of the .mobileconfig file we have generated, but when we install it on our device, the app does not return any value using UserDefaults.standard.dictionary(forKey: ‘com.apple.configuration.managed’).
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>
<key>PayloadContent</key>
<array>
<dict>
<key>PayloadDisplayName</key>
<string>App Name</string>
<key>PayloadIdentifier</key>
<string>com.xxx.yyy.TESTUUID</string>
<key>PayloadType</key>
<string>com.apple.ManagedAppConfiguration</string>
<key>PayloadUUID</key>
<string>TESTUUID</string>
<key>PayloadVersion</key>
<integer>1</integer>
<key>ManagedAppConfiguration</key>
<dict>
<key>MyFirstKey</key>
<string>value1</string>
<key>MySecondKey</key>
<string>value2</string>
</dict>
</dict>
</array>
<key>PayloadDisplayName</key>
<string>Test Profile</string>
<key>PayloadIdentifier</key>
<string>payloadid.TESTUUID2</string>
<key>PayloadType</key>
<string>Configuration</string>
<key>PayloadUUID</key>
<string>TESTUUID2</string>
<key>PayloadVersion</key>
<integer>1</integer>
</dict>
</plist>
On the other hand, about 3 weeks ago we requested the MDM capability for the app (https://developer.apple.com/contact/request/mdm-capability) but we have not received any response.
We are at a bit of a loss.
Topic:
Business & Education
SubTopic:
Device Management
Tags:
Enterprise
App Review
Apple Business Manager
Device Management
Hello fellow developers,
My app has been in App Store review for more than three months, and I have received very limited communication from Apple.
App Review responded once, stating that they need more time, but no further updates have been provided.
Developer Support only gives the same generic response that the review is still in progress.
Two weeks ago, I resubmitted the app, but it remains in review with no response from either App Review or Developer Support.
I also requested an expedited review, but nothing has happened.
At this point, I’m unsure what else I can do to move the process forward. Has anyone else experienced such long review times? Any advice on how to escalate this situation?
Thanks in advance for any help!
Greetings, does anyone know if there is an extension for the iOS 18 SDK and Xcode 16 update? I understand that starting April 24, older versions will no longer be allowed to be uploaded?
Topic:
App Store Distribution & Marketing
SubTopic:
App Store Connect
Tags:
App Review
Developer Tools
My app is getting rejected due to Guideline 4.2 - Design - Minimum Functionality.
So, my app is for reading or chanting, it's a religious app for chanting set of paragraphs. I have it running on Google Play since several years. I have around 30 contents and each one is of 108 short lines. But as per Apple the content is not enough.
I can add more of them but they will not be much useful. They also require extra effort. I have given all the reasons to keep the app the way it is but they are not agreeing. Can someone please suggest me if there is any other way or how should I look at these things.
e've unfortunately been having this issue too ... apparently a grey screen appears immediately after launch ... we've tried everything to troubleshoot .... tried across multiple devices including multiple iPads (including same M-chip versions as the testing version).
Also a flutter iOS app.
None of us can replicate this and the feedback from the reviewers have been minimal and repeated unfortunately making it near possible to troubleshoot.
In the past we've also managed to plead that they allow the update since there were other known bugs that were in our fix and they approved it ... we got no bug reports re a grey screen.
This seems to be very much specific to Apple review team ... I'm not sure what it could be but would be really helpful to have some help!
Hi All,
Hoping someone can shed light on the correct way to proceed for App Review using an app built with Unity's IAP Service. I'm unsure if I have a problem with my build or there is a problem with my sequencing of the review process.
Unity’s IAP won’t recognize a product until it exists on App Store Connect (which you would expect), however App Store Connect won’t publish products until they are reviewed with a submitted binary.
I submitted a binary with my first product for review and the app was rejected for “completeness” because the product was unavailable.
I requested clarification and the review team sent a screenshot back showing the store page in the game with the IAP UI in the state I would expect for no products returned (the buttons say “unavailable” and are disabled) - which makes sense, because the IAP is not approved and therefore not available.
The review team sent the following:
"When validating receipts on your server, your server needs to be able to handle a production-signed app getting its receipts from Apple’s test environment. The recommended approach is for your production server to always validate receipts against the production App Store first. If validation fails with the error code “Sandbox receipt used in production,” you should validate against the test environment instead."
It seems we are not event to the point of receipt validation because the rejection is due to products not being approved and therefore not returned when the app queries them.
So the app can't be approved unless it can be tested before the product exist in App Store Connect, but Unity's IAP won’t recognize the product until it exists in App Score Connect?
Since I had submitted once I was able to resubmit just the IAP, but that was rejected for completeness because it didn't include a binary - which was rejected because the IAP was not present - and the IAP was not present because it was not approved.
The IAP is a very simple "100 Gems" in game currency pack so I don't believe it is being rejected on its own merits, but I suppose I could be mistaken there.
I can’t be the only one with this problem, or I must be missing something… or there is something else wrong with my build.
Suggestions much appreciated!
Hello,
My application was developed as a promotion and discovery platform for the city of Kars. Users can explore businesses, events, job postings, hotel and accommodation services in the city and communicate directly with businesses. They can get directions, are directed to event tickets and benefit from special student discounts.
However, I received a red from the App Store on the grounds of Guideline 4.2 - Minimum Functionality. I think that the application has not been reviewed enough and actually offers real value to users.
📌 Featured Features:
✅ push notifications for all current content or campaigns etc.
✅ Business and event discovery (Categories: Cafes, hairdressers, hotels, job ads, etc.)
✅ communicating directly with the business. To make a Decryption call with a button.
✅ Directions that lead directly to maps.
✅ Directions for purchasing tickets for events
✅ Adding to favorites and personal content management
✅ Special discounts and opportunities for students
✅ Special announcements with push notifications
✅ Floating banner contents...
and much more
In my opinion, my application does not work just like a website, but rather creates an interactive value by providing a region-specific exploration experience.
I want a real person from the Apple Review team to evaluate the app and the job. As a result of the agreements I have made, I have thousands of users waiting for my application to be released in the Appstore. Please have a human examine this application. Because I sent dozens of messages and didn't get any feedback. After reviewing this application, you will understand that it is unique and functional.
I'm just waiting for support and a realistic approach from you. I do not want my labor to be wasted in addition to applications that do not have any content and do not work in the Appstore.
Hi, Since last week, I’ve been trying to publish the new version of my Voxel game, which aims to fix many bugs and significantly optimize the game. This update is very important for improving the overall quality of the game.
Unfortunately, this version is not being accepted on the App Store due to a Design - Copycats issue related to guideline 4.1. I’ve tried everything to resolve the problem by changing the screenshots, app preview, description, game name, icons, and even all metadata that could cause issues in the build. But nothing seems to work.
I keep receiving the same rejection just a few minutes after submitting my build for review.
Here is the full warning message:
—————— “Guideline 4.1 - Design - Copycats
This app or its metadata appears to be misrepresenting itself as another popular app or game already available on the App Store, from a developer's website or distribution source, or from a third-party platform.
Apps should be unique and should not attempt to deceive users into thinking they are downloading something they are not.”
Next Steps
Learn more about requirements to prevent apps from impersonating other apps or services in guideline 4.1.
Revise the app to comply with these requirements.
Once the app is fully compliant, resubmit the app for review.
——————
Also I've already tried contaction the Apple Developer team but I got no answer. I don't know what to do.
Thanks
Topic:
App Store Distribution & Marketing
SubTopic:
App Review
Tags:
Design
App Review
App Store Connect
Hi everyone,
I recently received a rejection for my app submission on the App Store. The rejection reason was:
"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." (Guideline 4.3(a) - Design - Spam)
However, my game is quite different. It features a unique pixel art style and introduces fresh mechanics, such as cleaning tasks, accepting additional missions from NPCs, and even an idle clicker-style system where players can hire workers to gather in-game points. These elements differentiate it from other apps in the same category. My game's name is quite different as well: "My Pixel Market Sim - AppID: 6742187384"
Additionally, the code behind the game is completely my own, and I even sell a popular Unity Asset on the Unity Asset Store for this category. So, I can assure you the app isn’t a repackage of anything existing. (I am the owner and publisher: https://assetstore.unity.com/packages/templates/systems/market-shop-store-and-retail-game-creator-for-both-pc-and-mobile-291107)
Can anyone shed some light on why this might have been flagged as spam? I'd really appreciate any advice or guidance on how to proceed with re-submitting my app.
Thank you in advance!
We are now on Day 12, and my app remains stuck "In Review" with no progress. Despite my repeated attempts to get a real update—including daily support tickets, an expedited review request, a phone call with an Apple representative, and multiple forum posts—nothing has changed.
This is not a normal review delay. Based on backend logs, it is clear that no one has even opened the app for review. It is simply sitting in the queue, ignored, while my users are left without critical updates.
I demand a call back from an App Review manager today. Not a generic email, not another vague "it's still in review" response—I need a real explanation from someone who has actual insight into what is going on.
To reiterate:
My app is one of the most popular and highest-grossing indie apps on visionOS, with thousands of users and hundreds of subscribers.
The app follows a tight update schedule, which your inefficiency has completely disrupted.
This is actively harming my business and user experience.
Every proper channel I have followed has been ignored.
Apple preaches that it supports indie developers, but this level of disregard shows the opposite. If there is a legitimate reason for this delay, I expect clear communication, not silence. If there isn’t, I expect this review to be completed immediately.
Please schedule another call today. I will not accept another day of inaction.
App ID: 6737148404
Dear Apple Developer Support,
We are seeking clarification and assistance regarding the recent rejections of our app submissions, citing insufficient business ownership documentation.
We are a software company that builds white-labeled food ordering applications for restaurants. To comply with Apple's guidelines, we have provided signed authorisation documents from each restaurant owner, explicitly stating that we are permitted to submit and manage their branded apps on their behalf.
Despite submitting these signed agreements, the apps continue to face rejection. Given that the restaurant owners have formally authorised us to act as their representative, we would appreciate guidance on why these documents are considered insufficient and what additional documentation might be required.
We are submitting the apps under the accounts of the individual clients for whom they were designed. However, this approach presents significant operational difficulties for both us and our clients, including:
Inconsistent App Management: Requiring each of our 180+ restaurant clients to maintain their own Apple Developer accounts makes it nearly impossible for us to ensure that all apps receive timely updates. This includes critical security patches, feature enhancements, and bug fixes, which are essential for maintaining app reliability and user trust.
Compliance Issues: Many of our clients lack the technical expertise or resources to properly manage their developer accounts. This often results in expired memberships, incomplete account setups, or even suspensions, all of which prevent us from delivering necessary updates and jeopardise app performance.
Operational Overhead: The administrative burden of overseeing multiple developer accounts slows down our update process, creating inefficiencies that negatively impact our clients and their customers.
If possible, we kindly request that this matter be escalated to an Apple engineer or senior advisor who can help us find a path forward while ensuring compliance with Apple’s guidelines. Would be appreciated if someone can reach out to us.