I am submitting an app that integrates with another system. In order to use the app you need to have a system login which Apple would not have.
What are the guidelines for sumbmitting an app of this nature? I assume there could be some issues if the only screen that the Apple test team can see is the login screen.
Thanks,
Joe
I created a couple of apps similar to this. We provided Apple with more or less dummy accounts that could get past the login screen, and view the basic functionality of the app, but didn't release any secret information we didn't want out
You should provide a test account for Apple reviewers and specify the login credentials when submitting the app.
Related
I got following email from apple
1.0.1 Binary Rejected June 16, 2015
17.2 Details We noticed that your app uses Facebook login for authentication purposes but does not include account-based features
offered
I got following attachment
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
17.2 Details
We noticed that your app uses Facebook login for authentication
purposes but does not include account-based features offered by that
site, which is not allowed on the App Store.
Next Steps
Please modify your app to include account-based features of that
social network or use your own authentication mechanism.
what is the reason behinds it.
I have study the following links
https://www.parse.com/questions/app-rejected-facebook-login-doesnt-complete
App got rejected because only using Facebook as login option?
Apple rejected app 10.6 because Facebook opens Safari to login
Apple review Guidelines says here
5.1.1 Data Collection and Storage
(ii) If your app doesn’t include significant account-based features,
let people use it without a log-in. Apps may not require users to
enter personal information to function, except when directly relevant
to the core functionality of the app or required by law. If your core
app functionality is not related to a specific social network (e.g.
Facebook, WeChat, Weibo, Twitter, etc.), you must provide access
without a login or via another mechanism. Pulling basic profile
information, sharing to the social network, or inviting friends to use
the app are not considered core app functionality.
I've a published app that has an optional login feature without any "account-based features".
I think providing a "continue as guest" option will fix the issue.
This means that your app didn't implement another feature of Facebook anywhere else in your application, if you're asking for explanation. If you make an app that just has Facebook's Log-in API, but nothing else, then your app will be rejected. Find another feature of Facebook (such as sharing or invites) that you can implement somewhere in your application, and try again.
A few possible steps you can take:
Ask App Store review people for clarification. Wait until you didn’t
get a response from them
You can make user registration optional or only prompt for it where
it actually requires
Try it.
Add note, while submitting app,the purpose of using Facebook login in resolution center without uploading new build it will be approve.
If still you face any issue then add some functionality of user login.
For Ex: Use of facebook login is for keeping all records of user in our database and also explain a bit about your app functionality why you use login feature.Hope it will help
Also check
iPhone app rejection 17.2: app requires users sign in with their Facebook accounts
Hello Everyone I am using the prime 31 facebook plugin for the Unity 3D engine and I am running into an issue of testing out the ability for our users to post a message containing their score onto their facebook wall.
I believe the issue is related to needing to add a publish_permission to my app yet I can't test this feature because I believe I have to have that permission approved to utilize it in my pap.
I also noticed that the approval process calls for explaining your usage of said permission and submitting your app with what I imagine would be a form of implementation .
So I guess my confusion has to do with the general process of having my publish permissions approved and whether or not i can make use of the publish permissions in my not-approved app for testing at the very least .
You should always be able to test your permissions with the admin/test/developer users of the specific app.
Have a look at https://developers.facebook.com/docs/apps/review/login#do-you-need-review which is stating that
...your app's developers will be able to see, and grant, any permission without requiring review by Facebook.
Note: People who are listed in your app's Roles tab will have access to extended permissions without going through review (e.g. publish_actions or manage_pages). For example, if you use the Facebook Plugin for Wordpress to publish your blog posts to your Facebook Page or Profile, you do not need to submit for review so long as all your publishers are listed in your app's Roles tab.
Also, if you're the developer of an app and are the only person using it, then your app doesn't need to go through review. Since you're the developer, all app capabilities should be available. You will still need to take your app out of developer mode, but you should be able to do that without going through review.
I am working on an application, which requires authentication (username and password). The user creation is done from a backend system.
So I would like to know if signup process is mandatory for application which require login/authentication?
I would be able to provide a test account to Apple to test my application for the approval process.
No it is not necessary to have a signup process and during the whole approval process you have to take care of thing that encourages a user to signup or buy subscription from your website.
I recently have gone through same issues, my app got rejected, but now it is in AppStore.
Refer to my this thread here: https://stackoverflow.com/a/19536184/362310 and my application is ICD-10 Search Version 1.0.0
There are apps on the AppStore that require login, but don't have sign up.
As always it's up to the reviewer, but as long as you provide test login credentials to Apple, you'll probably be ok.
Here's one
https://itunes.apple.com/us/app/storyworks/id620068637?mt=8
Well, you have to create an account for Apple app tester to let him to look into all your app content.
As #Andrew said to you do not need to provide a sign up system on your app.
Our iOS app requires users to login using their Facebook account and we need to provide the AppStore reviewers with a test account(s).
Can we take for granted that Apple have their own Facebook accounts that they use to test out apps that solely rely on Facebook for login?
Do we need to set up a Facebook "test user" via their Test User API?
Grateful for any pointers from someone who did this.
Short answer: assume they have an account.
I think you're in a bit of a catch-22 here. It's probably against Facebooks terms of service to create a test account and hand those details to a third party... but, you're right, Apple may ask you for details.
However, in practice, they seem not to. One of my apps requires a login to a third-party website and I just put "you need an account" in the iTC notes section. I've been rejected once (since 2008) because I didn't specify a specific username/password. I explained why (see first paragraph) and it sailed through on the next attempt.
Having said that, apparently Facebook allows a way of creating test accounts. This is probably what you want to do if they insist.
For any app that requires a login you need to provide Apple with a guest/demo login account to test the app. So yes, give Apple a login/password to use.
I need to add log in screen and registration forum to my application, such that the user register or log in to the application,
is it legal issue or my application will be rejected
You can have a log in screen. Many apps have them.
But Apple has been rejecting apps with a login registration screen, or even a registration web site URL within the app, depending on the exact conditions for that registration. You may have to get users to register for your app outside your app and/or before running your app. Make sure to preregister Apple with a demo account for use during app review.
It also helps greatly if your app has some general usefulness even without registering (e.g. banking apps may have a map to the nearest branch even for users who don't have customer account logins, or some public info about interest rates, etc.).
There are plenty of apps that also live on the web and so require some sort of login, e.g. Foursquare, Facebook
There are no issues at all with creating a login screen for your application. When you submit your app to the App Store, you will be asked to provide login credentials for the testing team to login and test your app. I wouldn't force them to go through the account creation process as it may delay your app getting approved.