Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about programming within the scope defined in the help center.
Closed 6 years ago.
Improve this question
I am currently making an app using Tinder API. It's very similar to those auto-liker apps that leverage Tinder API as well.
My app was rejected on the ground that the user is not presented Terms of Use Agreement before accepting to send login info to Facebook for use of Tinder token.
Now that is fine, but Apple also called me and said that
"There are rules not written in guidelines, and we do not accept apps that use unofficial APIs and scrapes websites that you do not own."
I checked the guidelines, and only things written there are that
Do not use unofficial API - I interpret as non documented iOS API.
Do not scrape Apple websites
Furthermore, there are dozens of Tinder auto-liker type apps, and yet more apps that scrape third party websites.
Why is the Apple review team telling me those things?
Has anyone else ever heard from the AppStore review team that:
We can only use "Official" APIs
We cannot scrape third party websites
There are rejection rules that are not written in the guidelines.
Any feedback is appreciated.
EDIT
The point here is that is there an unofficial non-written rejection
guidelines. I believe that is a gray issue since it can be grounds
for lawsuits and I want to get experiences of other developers if
they have received similar explanation over voice calls.
From my experience, any app that provides login-registration to users, needs to have a Terms of Service and a Privacy Policy page displayed to user before registration. Just add these 2 and resubmit the app for review.
Ok so after three phone conversations with Apple, the rejection reason was made more clear. It has nothing to do with "non-written" guidelines... there is no such thing. I am not sure why the reviewer mentioned in one of the conversations.
Basically I was exposing some data for Tinder users gained for API in a certain way, and Apple thought that I needed to gain their consent. Now, the other Tinder users are not users of my app, so it is impossible to gain their consent. That was the real rejection reason.
Related
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 4 years ago.
Improve this question
I’ve created an app using Ionic and Cordova. It runs on iOS, Android, and the web. The app helps streamline most tasks that small business owners face. It’s basically a CRM. In order to use the app a monthly subscription is required after 30 days. I’ve integrated Stripe as my payment processor and works well on every platform. However my app has been rejected twice now by Apple for not using their in-app purchaser which is required according to guideline 3.1.1. I just submitted the app a third time and this time I’ve structured my app exactly the same way as apps such as Salesforce and Insightly. When you download the app all you see is a login page. There is no option to create an account or a link/information pointing the user to a website where they can subscribe. All payment processing is handled outside of the app in the web browser. Im really hoping this change does the trick because I want the mobile versions of my app to act as simply companion apps after they subscribe on my website. I want to see if others could shed some light on this for me. I believe setting it up this way allows your app to fall under guideline 3.1.3(b). If I get rejected again for not using in-app purchases when my app is structured the exact same way as others currently on the App Store what can I do?
According to Apple:
3.1.3(b) Multiplatform Services: Apps that operate across multiple platforms may allow users to access content, subscriptions, or
features they have acquired elsewhere, including consumable items in
multi-platform games, provided those items are also available as
in-app purchases within the app. You must not directly or indirectly
target iOS users to use a purchasing method other than in-app
purchase, and your general communications about other purchasing
methods must not discourage use of in-app purchase.
I think the important point here is you CANNOT advertise anywhere in an app that you are selling something outside of iOS. So your example of Salesforce displaying nothing but a login screen does not violate these terms. Including even a link to your homepage will get you rejected by Apple.
The key point that Apple generally looks for is whether or not the purchase is being made to unlock in-app functionality. If users are paying for goods or services outside of the app, then Apple doesn't make you use their in-app purchases. (see 3.1.5 (a)).
Evaluate your application to see if it is clear that users are paying for out-of-app or multi-platform functionality.
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about programming within the scope defined in the help center.
Closed 9 years ago.
Improve this question
There's a service without free registration or something like that. Clients of this service have login and password. This service wants to develop an iOS app and distribute it in the App Store. This app won't be useful for regular users. Is it possible to submit this app in the App Store?
I understand that there are options like enterprise developer account, but for some reasons the developer wants to use regular account and regular app store.
I've read App Review Guidelines and didn't find any restrictions which require application be useful to anyone.
Of course test login will be provided for reviewer.
It is possible, look at concur & office 365 as examples
Closed. This question is off-topic. It is not currently accepting answers.
Want to improve this question? Update the question so it's on-topic for Stack Overflow.
Closed 10 years ago.
Improve this question
My App is rejected by the reason :
"We found your app inappropriately unlocks or enables additional functionality with mechanisms other than the App Store, which is not in compliance with the App Store Review Guidelines"
"It may be appropriate to revise your app to use the In App Purchase API to provide content purchasing functionality. "
What I have done is as below:
As this app is for my specific customer companies to use, I only want the companies who get the Invitation Code from me to use my app. There is no charge. I don not know is it necessary to use the In App Purchase API instead? if it is true , can you give me some tips?
Your application cannot be used by members of the general public, and thus does not belong in the App Store.
If you only intend your application to be made available to a few specific people, you should use Ad-Hoc Distribution to make it available to them.
Explain the purpose to the review team, sometimes they listen.
Also, maybe have that message as a "login page" instead. Have a username and password rather than a verification code. The verification code message may look more like you are selling the app behind the AppStore. Also provide the review team with an access code / login details if you haven't already so they can actually review the app.
Closed. This question is off-topic. It is not currently accepting answers.
Want to improve this question? Update the question so it's on-topic for Stack Overflow.
Closed 10 years ago.
Improve this question
I developed an app for the company who sells professional e-books by their website. In order to keep the content in sync with web data, app enforce login/registration and without that doesn't provide any functionality.
This is the reason why it has been rejected for Review Guidelines 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
My question is: is there a way to convince Apple to accept an app?
It is directed to the very specific proffessionals.
In the future the company want to add the possibility to sync books available on their website.
Also the books bought by in app purchase would be available on their website for the user account.
Isn't that enough reasons for Apple to accept this app? My client strongly want to have an account based app, the whole system was designed for that.
There is possibility to track user by udid but still it is not good solution because it is deprecated and Apple rejects apps using UDID for tracking reasons.
Does anyone have similar situation recently?
You say:
"app enforces login/registration and without that doesn't provide any
functionality."
Apple says:
"Apps that require users to share personal information in order to
function will be rejected"
So the answer is kinda obvious.
The app should provide (at least) some basic functionality without sharing personal data.
Maybe some book previews? 1 or 2 free books? App info? Why not apple's-bookstore? Does the website (before seeing anything) force you to signup too? Otherwise just make a web-app.
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about programming within the scope defined in the help center.
Closed 2 years ago.
Improve this question
I've had some trouble finding information about Apple's policies regarding in-app ads. I'm interested in developing a free iOS app with the intention of making money off of it using advertising. However, I don't want to use iAds or any of the other ad providing services. Instead, I'd like to manage and deliver ads on my own.
Does anybody know if Apple has any policies regarding this? I'm assuming that I can do it, since otherwise Google and other companies wouldn't be allowed to provide their own ad-providing networks. However, would I need to give Apple a percentage of the revenue, or would I be able to keep that money for myself?
Best, and thanks in advance for any replies,
Sami
Apparently you can.
iAd Network iOS Developer
If I do not wish to join the iAd Network, can I continue to use my
existing ad delivery service?
Yes. You can continue to use your existing ad delivery service even if
you do not join the iAd Network.