I have a question regarding app publishing.
I am a developer creating applications for my clients. I want to publish an application I developed for a client using my own Apple Developer account. The content of the application consists of data provided by my client.
Can I do this?
Are there any examples of applications that have been published under similar circumstances?
App Review
RSS for tagUnderstand the technical and content review process for submitting apps to the App Store.
Post
Replies
Boosts
Views
Activity
Hi everyone, can someone tell me what kind of documents mentioned below do I need to provide? I submitted everything I could: design documents, our workspace on bitbucket, trello but still got rejected.
Hello, Apple community and support team.
We would like to get your input on a recent rejection we got in our latest app submission.
The app uses public APIs in an unapproved manner, which does not comply with guideline 2.5.1.
Specifically, your app utilizes the NEVPNManager APIs for non-approved uses.
Since there is no accurate way of predicting how an API may be modified and what effects those modifications may have, unapproved uses of public APIs in apps is not allowed.
We are currently uncertain about the specific ways in which the NEVPNManager APIs are being misused in our app, as we have diligently followed the instructions documented on Apple’s website.
Our app uses a Packet Tunnel Provider and configures it to use a local proxy server for reducing network traffic, especially for video streaming services. We initially don't send any of the received traffic to a VPN server and instead, traffic is only handled by the Proxy Server.
We are committed to ensuring our app complies with all guidelines and appreciate your assistance in resolving this matter. Your guidance will be invaluable in helping us make the necessary adjustments.
Thank you for your support.
Recently, our app was rejected by App Store, reason is :
"The app still uses public APIs in an unapproved manner, which does not comply with guideline 2.5.1.
Specifically, your app is using NEVPNManager APIs without using VPN APIs.
Since there is no accurate way of predicting how an API may be modified and what effects those modifications may have, unapproved uses of public APIs in apps is not allowed."
Our app uses VPN to connect our company-internal network only.
so what should we do next?
i need update some options with Xcode or apply for some kinds of permission
In our application, we have a 'sign up' link that directs users to a URL (which is shared by our website) where they can create an account on our platform. Users can create an account either through traditional sign-up methods (providing their name, email, phone number, and password) or by using social sign-up options such as LinkedIn or Google.
Our application was rejected after we introduced the Google and LinkedIn social sign-up options. As a temporary measure, we have removed the link to the sign-up page from the application. Currently, users can only sign in to the app if they already have an existing account using email and password.
From guideline 4.8 we have:
4.8 Login Services Apps that use a third-party or social login service … must also offer as
an equivalent option another login service with the following features:
the login service limits data collection to the user’s name and email address;
the login service allows users to keep their email address private as part of setting up their account; and
the login service does not collect interactions with your app for advertising purposes without consent.
This guideline clearly specifies that the three listed features are only applicable to the equivalent (non social sign-up) option, they are not relevant to the third party login options.
Furthermore, the two third party login options which we have added to the page in question (Google and Facebook) are listed as third-party or social login service options in guideline 4.8, so these are not options which are unfamiliar to Apple and are clearly separated from what the guideline defines as an equivalent option, thereby clarifying that they are not needed to be reviewed for adherence to the three features listed.
I have communicated with the review team multiple times, seeking more details or a resolution to the issue, but the responses have been vague, pointing us to guideline 4.8 without providing detail on what aspect we are not adhering to.
What would be the best approach to resolve this issue and reinstate the sign-up functionality in the app? Based on my research, it seems that adding Apple Sign In as a third social sign-in option might be a solution, but this sign-up method would be out of place on the website and it does not feel like Apple will strong-arm developers in such a way.
Hi,
I would like to know the guidelines or rules regarding the implementation of Local Authentication. My client requirements are:
After the user login in with username and password, reset password, it will then authorize face id or passcode to be able to access/navigate the app.
Subsequent access will also require face id or passcode to access the app.
Clicking app notifications when app is closed will require face id or passcode to access app.
Is this a proccess allowed by Apple?
Thanks
Hello everyone!
By the guidelines we have to use IAP because actual service happens in the application itself: it is an app for scheduling actions. The business problem is that IAP does not allow the refund functionality which is important in-app in case the actual scheduled action will not happen.
Is there a way to use Stripe still exactly cos we need to implement refunds in the app?
Hello I have a question about my web app release. I have built a web app including Apple Music MusicKitJS. Now I would like to release it. Do I need to confirm this with Apple? If yes, what can I do next?
Guideline 2.1 - Performance - App Completeness
Your app did not load its contents and the activity indicator spun indefinitely when we tapped "Don't Allow" when prompted for permission to use current location. If location information is required, it is necessary to display a notification or alert indicating this requirement.
Next Steps
To resolve this issue, please revise your app to either enable functionality when a user opts out of providing location information or include an alert that this information is required.
Resources
For more information on Location Services, please review the section, "Determining Whether Location Services are Available" in the Location and Maps Programming Guide.
For a networking overview, review About Networking.
Guideline 2.1 - Information Needed
We’re looking forward to reviewing your app, but we were unable to sign in with the following demo account credentials you provided in App Store Connect:
User name: 8015965494
Password: 8015965494
To avoid delays in App Review, it is essential to provide the App Review team with access to your app's full features and functionality with every submission.
Next Steps
Please provide the username and password for a valid demo account on the App Review page of App Store Connect that provides full access to your app's features and functionality or include a demonstration mode that shows all of the features and functionality available in your app. Note that we cannot use a demo video showing your app in use to continue the review.
Resources
Watch a video from App Review with tips for preventing common rejections.
Learn how to share information with App Review when submitting your app for review.
Guideline 5.1.1 - Legal - Privacy - Data Collection and Storage
The app encourages or directs users to allow the app to access the location. Specifically, the app directs the user to grant permission in the following way(s):
A custom message appears before the permission request, and to proceed users press a "Configure Location Access" button. Use words like "Continue" or "Next" on the button instead.
Permission requests give users control of their personal information. It is important to respect their decision about how their data is used.
Next Steps
To resolve this issue, please revise the permission request process in the app to not display messages before the permission request with inappropriate words on buttons.
If necessary, you may provide more information about why you are requesting permission before the request appears. If the user is trying to use a feature in the app that won't function without access to the location, you may include a notification to inform the user and provide a link to the Settings app.
app在审核人员那里登录不成功,但我测试是成功的,请问应该如何去做
Good Afternoon Apple .... I am developing a takeway app, which allows business owners to register their takeway, then allow customers and staff, and allow their staff access to the account they have created. I would use IAP subscription to allow tiered monthly access, ie $10 for 1 user, $20 for 2, etc.
I have a server back-end which would be used to record the IAP subscription to allow the extra staff to log in via web or android.
The complication comes in with the case of a 'serial entrepreneur'. I use the model of '1 company, 1 email'. so, my entrepreneur registers 2 accounts, for 2 separate take-aways. Company A has 1 user, company B has 2 users.
In this scenario, I would want the entrepreneur to log into company A, purchase a 1-user mobthly subscription, switch to company B, and then purchase a 2-user supscription. the subscriptions would therefore be separate.
The registration would use my own login mechanism, so the entrepreneur would be using the same apple Id on the same iPhone.
i wish to avoid the scenario 'entrepreneur registers company B, purchases a 2-user monthly subscription, then registers company A, and automatically gets another 2 users.
Whilst I could likely code this to work, my questino is whether the app store would accept it ? the guidelines don't really seem to elaborate on this scenario.
if necessary i could make the entrepreneur purchas a 3-user monthly subscription that is shared across his 2 logins, but I would like to avoid this if possible.
regards,
Phil
A regular update to our game have been in review for almost two weeks. These updates normally take a day or less.
Is this a general problem or just our game?
We have iOS users complaining about the lack of new content. They are comparing to their friends on other platforms. Other platforms now have almost 3 weeks worth of updates that iOS have not gotten. iOS users are slowly losing faith and there is nothing we can do.
When can we expect for review times to return to normal?
We use CoreNFC feature for few clients. For clients who don't use NFC or add NFC related permission, the app is rejected on App Store.
is there a way to make CoreNFC optional in the library and not lead to app store rejection for parent app who do not use this feature?
I am using an older Adobe product (Director) with extensions that my programmer created to allow us to continue creating IPA's, successfully! Well, for the most part ;-)
We added a new app Product (and ID), got many successful Transporter uploads of builds, had all requirement ready.
But when we click on Add for Review, we are told that we need a 1024x1024 PNG icon image for marketing.
We have tried many different ways now to include such an image. However, we still get that error!
BUT...Transporter tells us they were successful uploads and TestFlight is showing the build as Ready to Submit!
Anyone else stuck at this juncture?
I got the feedback from app review that I need to clarify a few things about my add distribution. Here is the what apple told me to do. Where do I put the answers for these questions at? Also, let's say I pick unlisted app as the category, where do I put this information?
Here is what Apple asking me to do
We’re looking forward to continuing our review, but we need more information about your business model and your users to help you find the best distribution option for your app.
Next Steps
Please review the following questions and provide as much detailed information as you can for each question.
Is your app restricted to users who are part of a single company? This may include users of the company's partners, employees, and contractors.
Is your app designed for use by a limited or specific group of companies?
If yes, which companies use this app?
If not, can any company become a client and utilize this app?
What features in the app, if any, are intended for use by the general public?
How do users obtain an account?
Is there any paid content in the app and if so who pays for it? For example, do users pay for opening an account or using certain features in the app?
Resources
Learn more about app distribution options on Apple Developer.
I have an app which is in the app store since 2022.
It is an app with combined features of note taking, todo list and calendar.
My most recent app update is rejected with the following message.
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
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.
Help improve the review process or identify a need for clarity in our policies by suggesting guideline changes.
I reply the reviewer with the following message.
Hi,
I am writing to appeal the rejection of my app, ***. I would like to emphasize the unique aspects of *** that distinguish it from other apps in the market:
Integrated Functionality: Unlike most apps that are standalone note-taking, to-do, or calendar apps, *** uniquely combines all three functions into a single app.
Extensive Calendar Features: *** includes a comprehensive calendar feature covering holidays in 250 countries and 3,680 states and provinces, a rare and valuable feature.
Chinese Lunar Calendar: Our app includes a Chinese Lunar Calendar, which is highly appreciated in the Taiwanese market, adding a culturally specific feature not commonly found in other apps.
Organizational Tools: *** allows unlimited tabs and colors for organizing notes, surpassing many competitors who offer limited color options.
Flexible Viewing and Sorting Modes: Users can choose from four viewing modes (Grid, Compact Grid, List, Compact List) and five sorting modes (Modified Time, Created Time, Alphabet, Color, Check, Reminder), enhancing the user experience by providing flexibility and customization.
No Character Limit: Our design supports notes of any length without character limitations, unlike many apps that impose restrictions.
Organized To-Do Lists: Completed to-do items are automatically moved to the bottom, keeping the list clean and organized, a feature that sets us apart from other apps.
Rich Attachments: *** supports unlimited picture attachments, drawing attachments, and voice recordings for notes, offering more versatility than many other apps.
Advanced Security: *** offers 3 different kinds of password lock mechanisms to protect note privacy, ensuring users have multiple options for securing their information.
Powerful Reminders: Our app includes highly customizable reminders that can repeat daily, weekly, monthly, or yearly, making it easy for users to stay on top of their tasks and appointments.
Due to the character limits of this form, I cannot list all the unique features of ***. Please refer to our product description for a comprehensive overview.
We are proud of our 5k user reviews with an average rating of 4.8, reflecting user satisfaction with ***'s unique features.
Here's are some of the recent reviews. (United states only. Please kindly contact me to obtain full list of the reviews)
by ??? – Jun 14, 2024
omg i cannot explain how much i love *** like unlike the boring notes app this one is actually fun to use and rlly easy and i rlly like the fonts, color, to do list, calandar that can remind you like every day, week, month, and year like omg?!?!? i love *** and this app is going in like my "I 💖U" folder like tysm for making *** idk what i would do without it like omg tysm i cant explain in words how much i love it💖💖💖💖💖💖💖💖💖💖💖💖💖💖
by ??? – May 12, 2024
I love it sooo much I give it a 5 because there is a password so no one can look
by ??? – Apr 30, 2024
Perfect app. All in one
by ??? – Mar 26, 2024
I just downloaded this app a few days ago and I love it!! 😃 Up til recently I ALWAYS used paper sticky notes that I would have on my desk - and the reason why is because I could see everything all at once at all times; it’s very convenient - but it also produces clutter and anxiety because every subject is all in one place. *** fixed that!! 😀 With tabs and the list or grid view mode, I can have more organization of subjects and still see almost everything all at once! I love it! 🤩 suggestion I would really love to have more format options for the text! 🙂 Like a button to indent, and be able to have sub notes with points, dashes, or numbers. It makes everything look more tidy and neat. Thank you for this wonderful app! 😆
I am available at 123-456-789 to discuss further and provide additional detail. Thank you.
Till to date, I haven't received reply from the reviewer.
May I know, what are some other actionable items I can do, so that I can get through "Guideline 4.3(a) - Design - Spam" app update rejection?
Thank you so much!
Hi all,
Our app has been rejected several times without any clear explanation of what we need to do. The latest rejection reason is as follows:
Guidelines 3.1.1 - In-App Purchase and 3.1.3(c) - Enterprise Services
We noticed in our review that your app offers enterprise services that are sold directly to organizations or groups of employees or students. However, these same services are also available to be sold to single users, consumers, or for family use without using in-app purchase.
When an organization or group buys access to your app's enterprise services, you don't need to use in-app purchase. But when providing access to an individual user, consumer, or for family use, you should use in-app purchase.
To which we responded with:
We would also like to clarify our app and business model:
1) Our app is a free app intended for companies, organizations, and business owners. Individual users can sign up for our app, but with some restrictions. We designed it this way so that users can try our app before registering their company or business.
2) In the previous app version, we enabled users to subscribe and unlock more features within our app using our own mechanism. Hence, the review referred to Guidelines 3.1.1. In this version, we have removed the feature so that users cannot purchase any subscriptions.
Since users cannot purchase anything from our app, we believe Guidelines 3.1.1 should no longer apply for the app review.
But our app is still not approved. Instead, they replied with:
We are not able to provide feedback on app concepts or features, but we recommend evaluating your suggestions against the App Review Guidelines, as well as the Apple Developer Program License Agreement, and the Human Interface Guidelines.
Can anyone enlighten us why does the reviewer still referring to Guidelines 3.1.1 when there isn't anything that user can purchase from our app? And what do they actually want us to do?
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
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.
Help improve the review process or identify a need for clarity in our policies by suggesting guideline changes.
Hello,
I have built a mobile application specifically designed for managing employees within an open-source ERP system.
I have enabled an in-app purchase option so users can upgrade their version and access additional features.
We are now receiving interest from many clients who want to white-label this app and customize it with features tailored to their business needs.
Since we cannot incorporate all features into a standard app due to the unique requirements of each business, what is the best way to upload a white-labeled app to the App Store and customize it according to client specifications?
I attempted to upload a white-labeled app but it was rejected with the error "4.3.0 design spam." I am unsure how to address this issue.
Thank you.
Does anyone have recent experience of what App Review consider acceptable for location purpose strings these days?
My map apps simply display a blue spot on the map showing your current location when you turn on the app's location button. That data doesn't leave the app; I'm not selling it to anyone, or doing anything nefarious. For years, I've had concise location purpose strings such as "Your location will be shown on the map".
Now, App Review seem to find that inadequate. They say: "One or more purpose strings in the app do not sufficiently explain the use of protected resources. Purpose strings must clearly and completely describe the app's use of data and, in most cases, provide an example of how the data will be used. Next steps: Update the ... location purpose string to explain how the app will use the requested information and provide an example of how the data will be used. "
I've just look at what Apple Maps uses as its purpose string, and it's just "Your location is used to show your position on the map, get directions, estimate travel times, and improve search results." I'm only doing the first of those things, so surely "Your location is used to show your position on the map" would get approved, right? Wrong!
I have similar issues with the photos purpose string.