App Review

RSS for tag

Understand the technical and content review process for submitting apps to the App Store.

App Review Documentation

Post

Replies

Boosts

Views

Activity

4.3 A Spam Design
Hi there, I need your help with a specific issue we're facing. We recently submitted our app, but it was rejected for violating Apple's Guideline 4.3 (Spam Design). Our situation is unique: our principal company ceased operations in 2020 due to the COVID-19 outbreak, and the previous app is no longer functional. The Apple Developer account and web services associated with it are also inactive. We're trying to rebuild using the legacy source code from the previous company. We don't have access to the old app or the Apple Developer Account, but we do have the source code, which is built using Xamarin. Our Android app, which uses the same codebase, is already live, and we're attempting to upload the iOS version. The support team has asked us to change the app concept, but this isn't feasible due to the app's purpose: it's designed for monitoring and reporting within our hotel management system and isn't open to the public. Changing the app would require significant alterations to our business flow, re-educating our customers, and impacting our Android app, which shares the same codebase. Could someone experienced with Guideline 4.3(a) assist us with this issue? Your help would be greatly appreciated. Thank you.
2
0
81
20h
Rejected Review - Mac App Sandbox entitlements required for Bluetooth
I submitted a Mac Catalyst app for TestFlight and before it can be tested by external testers it requires an App Review. The iOS app passed review, but the Mac Catalyst app failed review. The rejection reason given was that App Sandbox needed the entitlement: "com.apple.security.network.client" to be YES / true (not false). I do have "com.apple.security.device.bluetooth" set to YES / true. The Developer docs for entitlement "com.apple.security.network.client" say "Use this key to allow your sandboxed app to connect to a server process running on another machine, or on the same machine." for entitlement "com.apple.security.network.client", then go on to discuss TCP and UDP. https://developer.apple.com/documentation/security/app_sandbox While technically a Bluetooth app connecting to another Bluetooth device puts the app in "client mode" and the device in "server mode", I think this network entitlement was intended for TCP / UDP, not Bluetooth. The entitlement "com.apple.security.device.bluetooth" says "A Boolean value indicating whether your app may interact with Bluetooth devices." - this seems to cover all the necessary needs for Bluetooth "your app may interact with Bluetooth devices"..... Would someone at Apple familiar with the docs please clarify what entitlements are required for an app that only uses Bluetooth? If the "com.apple.security.network.client" is required, then I believe the docs for that property should also specify Bluetooth.
1
0
96
1d
Guideline 3.2.1(viii) - Business - Other Business Model Issues - Acceptable Your app provides loan services without meeting all the requirements for apps providing these services.
I am Pakaytip,Here is the detail infomation about my issue: The first time I registered a developer account for my organization, I used my gmail email address. When I submitted the app for review for the first time, the review team replied to me that because our app provides loan services, the developer account must use an email address in the same domain as the company. So I followed the guidance of the developer rules and transferred the holder of our developer account from my previous gmail to the current email address with the same domain as the company in Membership: ******@thiensuratleasing.com Now the name of our organization is: THIENSURAT LEASING COMPANY LIMITED Account Holder: ******@thiensuratleasing.com But when I resubmitted for review, I still received a rejection for issue 3.2.1, as follows: __****Hello, Thank you for your response. However, in terms of 3.2.1, we continued to find that the verified email domains for the "Contract Admin" only end with gmail.com and do not match domains for the submitting company or partnered financial institution. Should you require additional assistance, you can use the contact us page to request help with setting up or distributing your app through App Store Connect. We look forward to reviewing your resubmission. Best regards, App Review** **__ So, I want to know how to update the email address here in "Contract Admin"?
1
0
66
2d
Guideline 4.3(a) - Design - Spam
Hi, Thank you for your feedback regarding our app submission. We understand that the latest version was rejected under Guideline 4.3(a) - Design - Spam. We would like to confirm that our app is unique, combining casual gaming and video chat to deliver an engaging and distinct user experience. This update is critical for ensuring optimal performance on iOS 18 and providing a seamless experience for users who have already upgraded. We hope to resolve this matter fully and avoid encountering similar issues with this guideline in future submissions. We kindly request that the review team re-evaluate our app’s uniqueness and design. Additionally, we would greatly appreciate your assistance in expediting the review process so we can release this important update to our users. If further clarification or additional information is needed, please don’t hesitate to reach out. Thank you for your understanding and support. Best regards, The Fachat Team
2
0
124
4d
Reader App & external Button
Could I implement a button in my application that would open an external link where people could register their account? Just like the Netflix or Disney Plus app has. I think my application falls under the category of "reader" app, just like Netflix and Disney Plus. While I was developing the app, the apple review team rejected my app because of the button to the external registration page. But I see that all other applications that belong to the Reader app have a button, so I'm interested if someone can help me, what do I need to do to enable the button to the external user registration page? best regard Nemanja Nedelkov
1
0
44
4d
4.3 Design Spam - Roadblock
Hi, I am stuck at "Design Spam", I have done numerous revisions but still i am getting "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." from app review team. The app which I am trying to submit is a simple social media app, and its been almost a month it could not pass the review. I have updated meta data, updated assets but still app is getting rejected. Has anyone faced similar case, if yes then how did they solved it? Any help would be appreciated. Thanks
1
0
143
5d
In-App Purchase goes missing when submitting app for review
I'm currently in the process of submitting a new app with a single non-consumable In-App Purchase. After creating the IAP in AppStore Connect, I created a synced StoreKit config in Xcode which correctly loaded the purchase. After making sure that the transaction works as expected within the app, I submitted the app in AppStore connect, including the In-App Purchase. Since then, the In-App Purchase can not be found in the StoreKit configuration and isn't displayed in the app, which lead to the submission being rejected. As requested by the review team, I have resubmitted the In-App Purchase, so it's currently "Waiting for Review" but still not showing up in the StoreKit configuration in Xcode. I'm not quite sure what I'm doing wrong here. I have other apps live in the AppStore with IAPs and no outstanding agreements to sign.
2
0
75
5d
Notice of Termination. I ask for advice on what to do.
App ID: 6470781599 After receiving the mail below, my developer account was canceled and my app was taken down. I contacted Apple and they said they are reviewing it and haven't gotten back to me in 3 weeks. I was wondering if anyone has experienced the same situation and if anyone knows how much longer I should wait? Since it's a company app, I'm getting a lot of resentment from existing app users. Should I upload a new app? As previously advised, App Store Review Guidelines 5.6.4 (App Quality) states, "[Customers expect the best quality in the App Store, and maintaining high-quality content, service, and experience increases customer confidence. Signs that this expectation is not being met include excessive customer reporting and excessive refund requests for concerns about apps such as negative customer reviews. The inability to maintain high quality can be a factor in determining whether developers comply with the developer code of conduct," it states. You have not done enough to tailor your Apple Developer Program account to the Developer Code of Product. Therefore, Apple is exercising its right to terminate your status as an Apple developer under the DPLA. As an Apple developer, I would like to remind you of your obligations under DPLA regarding all software and other confidential information obtained from Apple. You must immediately cease and desist from any use of these materials and comply with all other termination obligations set forth in Section 11.3 of DPLA and Section 10 of ADA. If applicable, no additional payment will be made in accordance with Section 7.1 of the Paid Application Agreement (DPLA Schedule 2 and 3). This letter is not a complete description of the facts in this matter, and nothing in this letter should be construed as waiving any rights or remedies Apple may have. All such rights or remedies are hereby protected.
0
0
130
5d
In App Purchase
I have an objective C in app purchase listener... I have a swift form and it begins the in app purchase when they click on the button the purchase screen comes up if i am signed in as a tester the only test email we have on our account eveyrthing goes through and the server creates the proper records because the purchase listener SKPaymentTransactionObserver on the APp Delegate gets in formed ... and calls the static swfit methods to complete the process which takes the static USER ID of last logged in user and puts the original transaction id with it and sends both to our server so it can link the transaction id to the user id . Once the app loads it queries our site which uses the API for Apple payments to query the status of the original transaction id for that user. if it is valid it lets them login. Now for some reason the server never receives any information if i login on my icloud ... phone account as anyone but the testing email holder. If i use my own account to test the transaction my own personal email and apple id i get no feedback what soever from the SKPaymentTransactionObserver so i never get the original transaction id to send it to the server. BUt if i sign in as a tester in sandbox mode then everything works as expected. I send it to the test team and they too say they never get the subscription to be recognized this is a single reoccurring subscription they purchase recurrs every 3 minutes. Now why when i login as the test email account everything works every time butwhen the app store test team tries it nothing gets to the server any more Are they supposed to login on their phones to the Same Test account as i did meaning erase all their info and put the test email account in their phone just to get this to work and why do no other emails work for the purchase when in sandbox mode am i supposed to take it out of sandbox mode in the submission ???? why is in app purchasing working every time in my sand box mode test account when it is installed on the phone but no where else ?
0
0
86
6d
App rejection for including one-time offer at the end of onboarding?
We have an app that’s been in the store for a year, and the latest version was rejected for Guideline 5.6 - Developer Code of Conduct. The app attempts to manipulate customers into making unwanted in-app purchases. Specifically, the app shows a one time offer for subscription when the user closes the initial subscription page launched upon opening the app. Essentially we have a soft paywall at the end of onboarding, and if the user closes that paywall we pop a second paywall with a one-time offer with an introductory offer (2 months for $1, “Once you close your one-time offer, it’s gone!”). We’ve had this in the last few versions of the app, but not been flagged for it. The strategy of having a one time offer after end of the onboarding paywall is not uncommon, and we are copying the approach used by many other apps in the app store. Limited time offers are a staple of marketing across all types of B2C stores. Does anyone have any experience with this type of rejection? Should we stick to our approach and escalate to a phone call? Change the one-time offer to a “limited time offer” (e.g. reduced price for 12 hours) so there is less pressure to decide right then? It’s a strange rejection because it doesn’t seem like we are doing anythign unusual. An onboarding soft-paywall followed by a one time offer is less of a push than a hard paywall (which is approvable), and offers some people an appealing way to test the app before committing to pay for a subscription (which doesn’t offer free trials). However, we don’t want to get flagged as a bad actor by the App Store reviewers.
1
0
140
6d
In-app payment via bottom-up swipe gesture
This question came up, a customer wants to add payment, with gesture, to their app. This gesture is a swipe, from bottom to top (like when minimizing applications). The question immediately arose, will the application pass the review with such UI/UX ? Will there be any problems ? I'm not talking about problems when the user can minimize the application when paying, or pay (accidentally) when minimizing. I want to know if there will be any problems from Apple's rules when releasing the app ? I haven't found the exact information yet
1
0
121
1w
App Store Rejection - "Information needed"
these are the questions that apple asks repeatedly. This is the Home Screen of the app. What are the ways to publish my app publicly. what changes should I make if they keep on asking these questions? I have an organisational signup and with the organization ID users can be registered. the transfers are loaded from DB, if the registered user has a transfer assigned, it will be shown in the Home Screen.they can accept or reject the transfer as required!
2
0
84
1w
Rejected for 4.3.0 Design Spam
Thank you for your feedback on our app submission. We noticed that our latest version (1.1.7) was rejected for 4.3.0 Design: Spam. However, the previous version (1.1.6), with similar features and design, was successfully approved. We can confirm that our app is unique, offering distinct functionality and user experience. It is developed using the React Native framework, with a carefully crafted interface and interactions to provide a high-quality user experience. Due to issues with in-app purchases and several bugs in version 1.1.6 affecting user experience, we urgently need to release this update (1.1.7) to resolve these issues and ensure a stable, secure app for our users. We hope to fully resolve this matter to avoid inadvertently encountering this guideline in future releases. We kindly request that the review team re-evaluate the uniqueness and design of our app and assist us in expediting the review process so that we can push this update to our users. If you need further clarification or additional information, please don’t hesitate to reach out. Thank you for your support and understanding. Best regards, 365 Internet Inc
1
0
85
1w
App Rejected for 4.3.0 Design: Spam
Thank you for your feedback on our app submission. We noticed that our latest version (1.1.7) was rejected for 4.3.0 Design: Spam. However, the previous version (1.1.6), with similar features and design, was successfully approved. We can confirm that our app is unique, offering distinct functionality and user experience. It is developed using the React Native framework, with a carefully crafted interface and interactions to provide a high-quality user experience. Due to issues with in-app purchases and several bugs in version 1.1.6 affecting user experience, we urgently need to release this update (1.1.7) to resolve these issues and ensure a stable, secure app for our users. We hope to fully resolve this matter to avoid inadvertently encountering this guideline in future releases. We kindly request that the review team re-evaluate the uniqueness and design of our app and assist us in expediting the review process so that we can push this update to our users. If you need further clarification or additional information, please don’t hesitate to reach out. Thank you for your support and understanding. Best regards, [Your Name or Team Name]
0
0
91
1w
Safari Extension rejected for using "for [Platform]" in name - despite many precedents
Hi devs community, I've run into an interesting situation with App Review that I'd like to get the community's perspective on. My Safari extension "Protego for Reddit" (a content filter for Reddit) was rejected under Guidelines 2.3.7 for using "Reddit" in the name/subtitle, citing potential customer confusion. What's puzzling is there are many established apps using the same naming pattern for the app name and subtitle, all currently on the App Store: Narwhal 2 for Reddit - "Highly customizable Reddit app" Sink It for Reddit - "Upgrade Your Reddit Experience" Reno for Reddit - "instagram styled Reddit app" Dystopia for Reddit - "A Better Way to Reddit" MultiTab for Reddit - "Best viewer for image/video" Nano for Reddit - "The wrist-based Reddit client" Focus for Reddit - "A unofficial app for Reddit" Monocle for Reddit - "A comprehensive Reddit client" Redirect for Reddit - "Redirects to old.Reddit.com!" Alerts for Reddit - "News" rex for Reddit - "Lurk with ease!" Comet for Reddit - "Fast, Robust, and Beautiful" Redista client for Reddit - "Entertainment" Readder for Reddit - "Entertainment" lurkur for Reddit - "a new way to browse" Pics HD for Reddit - "Entertainment" Apollo for Reddit - "Closed. Goodbye and thank you!" and more I submitted a reply to the app review rejection and they told me that if I disagree with the outcome of their review that I need to file appeal to the App Review Board. I've already submitted an appeal pointing out these precedents and explaining that the name accurately describes the app's functionality without implying any official association. While I wait for the response, I'm curious about a few things: For those who maintain apps with "for [Platform]" in the name: Do you face this rejection with every update? Did you only have to appeal once, after which subsequent updates were approved? Was there any special process to get your app "whitelisted" for this naming convention? Has anyone noticed if this is a recent change in enforcement? The number of existing apps with similar names suggests this wasn't always strictly enforced. For those who successfully appealed similar rejections: How long did the appeal process take? Did you need to escalate beyond the initial appeal? My concern is whether I'll need to go through this rejection/appeal cycle with every update, which would significantly impact our ability to push out timely fixes and improvements. I've had to delay two updates due to this issue. Context: App description: Safari extension for filtering Reddit content on Mac Current name: "Protego for Reddit" Subtitle: "Filter your Reddit Feed" Version: 1.3 Status: Awaiting appeal response Many of these established apps even use "Reddit" in their subtitles, which makes the rejection of my subtitle "Filter your Reddit Feed" particularly confusing. Thanks in advance for any guidance or shared experiences!
2
0
115
1w