I'm submitting my first iOS app through iTunes Connect. What should I add under App Review Information ->Notes for the app reviewer?
Is it recommended to add some kind of tutorial/walkthrough to let the reviewer know what to do?
When deploying our applications, we usually leave this field blank. You should definitely avoid entering tutorials and walkthroughs in the review notes.
The application is getting approved for App Store. The question you have to ask yourself is: "If someone working for Apple, clearly with technical expertise, needs a specific tutorial, how can someone without any knowledge of development use my application?"
Those review notes are meant only for Apple Review Team, as previously mentioned, you should only add notes that are relevant for them, if some special registration is required for sandboxing the user (or you can provide login credentials in separate fields).
Just make sure you are conforming to Apple's App Store rules and leave the field blank, unless it is absolutely necessary to tell something to reviewer. Do not use it to tell them, something is unfinished or beta, or such.
Related
I need to update URL for App Store server notifications, which I entered when started development the app.
So IT was available.
But now, there is no such input
Also I have valid role for edit this info, have several Auto-Renewable Subscriptions, used different browsers. and my teammates do not see this input too
as describe in doc https://help.apple.com/app-store-connect/#/dev0067a330b
You have to add a subscription item in your In App Purchases Section.
Once added the field will show up.
I've written to apple support and got the answer with "To better assist you, I need more information. Please provide the following:...."
So I started recording the video about this issue and guess what? Right! The input field was in the place where it should be.
I did nothing additional after write this post and ask the support. Dark magic as it is.
Apple should improve developer experience in App Store Connect. This is not the first such problem. The most often, apple even does not the error text and you should go to dev tools and look out what the real problem
I don't know where to answer these questions. I uploaded the answers in app review information note section but didn't work. What should I do?
The review message is attached below.
Guideline 2.1 - Information Needed
We’re looking forward to continuing our review, but we need a bit more information about your business model and your users to help find the best distribution option for your app. Our preliminary review of your app suggests that your app may be a good fit for our Apple Business Manager program, which is designed specifically for business apps.
Next Steps
Please review the following questions and provide as much detailed information as you can for each question.
Please describe which kinds of users you expect will use your app. Some common kinds of users are:
Users who are part of a single company (including its partners, employees and contractors)
A limited number of companies which are clients of the developer
The general public
Identify the specific countries or regions where you plan to distribute your app.
What features in the app are intended for use by general App Store users?
How do users obtain an account?
If there are any paid aspects of the app, such as for opening an account or using certain features in the app, please explain how users access the paid content.
Who pays for the paid content?
Since your App Store Connect status is Metadata Rejected, we do NOT require a new binary. To revise the metadata, visit App Store Connect to select your app and revise the desired metadata values. Once you’ve completed all changes, reply to this message in Resolution Center and we will continue the review.
You need to navigate to the app in Appstore Connect, click on "Version History" and then click on "Resolution Center". On that screen is a form where you can reply to the inquiry from Apple. It took me longer than expected to find it.
I've been working on a simplified, web-based ad-hoc build management service for a while now, and I'm going over the possibilities to my make clients life easier.
While one possibility is to simply create a web app optimized for iOS, I'd rather have a native app instead.
Now, I haven't found any clear advice on whether or not Apple is okay with apps using itms-services links, which would then install 3rd party non-App Store apps, as long as they were signed ad-hoc/Enterprise builds.
In my case, the apps in question would be tied to a specific user/group, and would be behind a login/signup.
Currently all I'm doing is:
[[UIApplication sharedApplication] openURL:_appInstallUrl];
Also, if Apple would be okay with an app like this on the App Store, how would they feel about forcefully suspending apps?
I'm currently doing this right after installing the app:
[[UIApplication sharedApplication] performSelector:#selector(suspend)];
This could be a violation to the App Store Review Guidelines:
2.8 Apps that install or launch other executable code will be rejected
2.25 Apps that display Apps other than your own for purchase or promotion in a manner similar to or confusing with the App Store will be rejected
But you'll only know if you directly ask Apple, or simply submit it and it goes through.
Posting this as an answer, since it's the official response from Apple.
I first contacted Apple's technical support regarding this, but they couldn't help and instead wanted me to contact the App Store Review Team, remembering to mention that a technician had told me to contact them.
They finally responded with the following:
Thank you for contacting the App Store Review Team.
Please know we are not able to pre-approve proposed application ideas or concepts for developers without reviewing the app itself.
Each application is unique and we would need to look at all its features, and complexity to be able to give you an answer.
Therefore, we recommend that you submit your application for review. We will then contact you if we have any questions.
However, for your questions we do recommend that you review the Functionality and Privacy sections within our iOS guidelines:
2.22: Apps that arbitrarily restrict which users may use the App, such as by location or carrier, may be rejected
17.2: Apps that require users to share personal information, such as email address and date of birth, in order to function will be rejected
While this technically doesn't answer my question (at all), it would seem like the idea/app could still go through, depending on the reviewer. At least they don't seem to be against the idea.
I am working on a mobile iOS app that is customized to each client, with their own app icon, startup screen, and a few other changes. Each is then submitted to the app store as an individual app.
This is working just fine so far, but what will happen if there's 1000 clients instead of around a dozen? Does Apple have any rules on quantity, submission rate or uniqueness? Any reviewer would clearly see that the apps are basically the same outside of the branding.
Don't do it. You will get kicked out of the appstore.
Read 2.20 of Apple iOS Guidelines which says that developers that spam appstore with similar apps will be kicked out completely!
Notably developers like AppGratis got kicked for this and many others reasons.
Sorry can't disclose, if you have a developers account though you can check the requirements
from https://developer.apple.com/appstore/resources/approval/guidelines.html
I know this is an old thread but somehow it popped up and the answer selected is not entirely correct. The requester needs the custom B2B program here:
https://developer.apple.com/programs/volume/b2b/
That is specifically made for the purpose she/he asked about: to distribute customized apps to a business without cluttering the app store. There is no cost but your customers will need to join the Apple Volume Purchase Program for Business though that doesn't cost them anything.
The reason I say the accepted answer is partially correct is because obviously one should not spam up the app store with similar apps intended for one business, which is entirely correct. But that does not answer the underlying why they wanted to do this and how they could achieve the result they need which is to use the B2B program.
I have an app in the iTunes store that has full functionality. I attempted to release a Free version which contains half of the functionality, and contains a link to the full version if the user tries to use the other functions.
Apple rejected the app on the basis that rather than having two apps, I ought to have the main app released for free and have the extra functions unlockable using in-app purchasing.
That's fine; I can do this. The only problem is that since I released the full version initially, some people have already paid for and downloaded the full version. When I update this app so that it is free, it will be restricted by default. Those users that have paid for the full version will have lost the functionality they've paid for.
I don't really want to release a second version of the app since I intend on continuing to update the app and managing two release streams would be unwieldy.
Is it possible to somehow offer for free the in-app purchase to those users that have already bought the full version of my app when I update the app to the new (free, in-app supported) version?
Edit: An (unpreferred) alternative would be a way of refunding the purchases to the original buyers, along with a note explaining why. Any ideas how?
What I'd do is add a already paid option within the application itself, and then allow users to enter a license code, or email address depending what you prefer, Which you can automatically issue from their contact details if you have them or ask them to contact you if you don't, which most will as they have paid.
Now as far as the licensing and the verification of these codes you could setup a cheap VPS which verify s the code and only activates with codes that you have entered on the server, meaning you won't fall victim of Keygeners.
Just my 2 cents.
If your app doesn't currently have a username/password registration, I would suggest releasing an update to the paid app that explains to your users on an initial popup view something like:
Thank you for supporting our app. Due to changes in Apple's policies, we will be converting this app into a free app with in-app upgrades. Since you already purchased the full app, you will be awarded all features! Please input an [email_address or username] so that we can provide a painless transition.
If your app has a user login mechanism already in place (username/password), then just store those details and have the user log in later in the "free" app to unlock all of the features.
Obviously, both of these suggestions require a backend for validation, but shouldn't be too difficult to create that.
This is tricky due to section 3.3.3 of the license agreement and Attachment 2. I'm not a lawyer so I'll save my interpretation but, read them.
Another option would be to make the free version a new, different app and leave the original one in the store but unavailable. Then you can still publish updates to it but new users won't see it. Apple would probably allow this considering you are still only presenting one app to new users. The downsides are (1) you have to maintain two versions and (2) you have to start over in terms of reviews etc.