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 3 years ago.
Improve this question
I want to publish some kind of a banking app to the App Store. I don't want to create a test user account on a backend, because that will cause a security hole. So I came with an idea to have one demo account in my app which does not connect to the backend but presents some test hardcoded data? Is it going to be okay for Apple review process?
As per apple rules & guidelines if you will submit App with demo data, sandbox data or any other test details which are used for temporary basis than they will reject your application.
In your case it looks like its a login based app. Than in that case you will have to provide demo account credentials to the apple review team for testing. Otherwise they will reject the app or may be ask for more detail by rejecting metadata.
For the security purpose you can keep that test user account secret & pass to the apple review team in Login info section. And once you get app approved you can remove that registration from the backend part.
Hope it will help.
Related
Closed. This question needs details or clarity. It is not currently accepting answers.
Want to improve this question? Add details and clarify the problem by editing this post.
Closed 4 years ago.
Improve this question
Is the app will be approved by apple if the user registration is only through website not through app and can access the login content in the app.
In the website it might use some payment if needed.
Thank you in advance.
Yes, they will approve. Make sure to follow these steps:
Leave no traces about your website or payment in your app.
Provide a demo username/password to Apple so that they can login and go through your app at the time of review process.
Good luck!
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 7 years ago.
Improve this question
I want to develop one app with only Facebook Login feature but I'm worried about Apple guideline. Is it possible to avoid app-rejection due to this?
Short Answer: NO
I did the same thing in one of my app. I added the Facebook login feature but did not use it for any significant feature in the app. My app was rejected. This was the not I got from Apple.
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.
In order to use Facebook for authentication, your app must include
significant account-specific functionality from Facebook. For example,
your app should include sufficient account-based features from
Facebook other than pulling profile information or sharing on the
user’s page.
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.