Now, I am going to submit my app for approving. The problem is that, when the first time logging the app, you have to enter a verification code provided by me (by email or oral to my target user). So how can I give the code for approving.
May be I could set a default verification code programmatically, but when the app is approved , I have to update the app to disable the default verification code and this lead to another approve process.
So, can someone give me some advice to solve this problem?
When you're in iTunesConnect preparing to submit your app there's a box for review notes (Source, page 49), where you can put a verification code for the reviewers to use.
iTunes Connect provides an area for Review Notes. The app tester will look at this and use it during review.
Simply put the verification code and any other information inside that area. they WILL read it.
Related
So we've developed a Facebook App (and similar apps on Twitter and Instagram) that allow users to post and read content using an external system. We'll sell this integration directly to our clients, so it's a private application.
Basically the user will see a very simple page with a button "Log in to Facebook" and a disclaimer regarding the authorization (we'll use some query params fixed in the url, depending on the client). The client authorize us and we capture the access tokens.
To submit the app review, though, we have to explicitly give a test user to the reviewers, but that's not really possible because the real "action" happens within the integrated systems, NOT within the app itself. And those systems are not public (they shouldn't be).
So just to be clear: our app is basically a very simple "Facebook login" that we use to get tokens, generated by specific clients authorization. It's not going to be published anywhere.
Until we have around 5 to 10 clients we can add the specific users in our app as Testers/Admins/etc, but what if we scale up? Say we have 20 clients. How are we supposed to get our app to be "live"?
To follow the app review steps we would have to create some users in our local systems (we have some dev environments), open them to the internet so the reviewers can log in and see how it actually works? Is that it?
(btw I'm asking this because our app review was rejected twice and I want to make sure I'm submitting everything they ask this time).
Thanks :)
I think the Login Review FAQ answers most of your questions. The key point:
Our review team will actually test how your app uses each permission on every platform you have listed in the settings section of your app.... You'll need to explain exactly how to test each permission or feature in your app so that we can make sure it works and follows our policies. We can't approve your app if we can't fully test how it integrates with Facebook.
In other words, it's not enough to just allow them to log in to your app, you have to expose all Facebook-related features to the reviewer.
To follow the app review steps we would have to create some users in our local systems (we have some dev environments), open them to the internet so the reviewers can log in and see how it actually works? Is that it?
Yes, though I'm not sure what you mean by "open them to the internet". You should be able to create a test user on your local system and link that account to a test Facebook user. Then you can have the Facebook reviewer use that test account for their review. (From the FAQ: "In the Items in Review section, you'll see a Test User (optional) section that allows you to type the name of the user you wish to be used in your review.")
I created an fb application which uses the following permissions: manage_pages,publish_pages, and read_insights.
The main purpose of the application is to give to the authenticated user reports and statics about the popularity of his own fb page.
I noticed that I can't use those permissions until I submit the app for review.
In the facebook developer account, I noticed that for each of the above permissions I have to complete some notes:
1. How a person logs in with Facebook
2. How a person sees the permission used in your app.
Also they want me to upload a video to show them that I use the permission correctly.
The problem is that I'm not sure what should the video contain in order to clarify the point 1 and 2.
Right now my application is only doing the authentication phase (signup), and in the next release we are going to create and display analytics for each user who joined the platform.
I would be grateful, If you could give me some suggestions regarding what facebook would like to know in order to approve the permissions.
Thanks,
Your App needs to be working before you can send it in for review. Meaning, you need to have at least a working prototype. For development, you do not need to go through the review process, every permission works for everyone with a role in the App without review.
In other words, you can´t go through review with permissions you don´t even use right now.
I have a Facebook app which is currently live, but would like to add additional functionality which involves requesting additional permissions (mainly publish_actions). The new permissions, due to Facebook policy, need to be reviewed by their team before they can be used live.
Is it possible to use one app for this? Is there a way (and is it acceptable by Facebook) to lead the user down a different flow if they are a tester, rather than a user during the review process?
I've also looked into the possibility of a test app, but I'm not sure if it's possible to flag that the app to review is a test version, which would then be approved on the live app. Facebook's FAQ seems to suggest this is not possible.
I'm not marking this as a definite answer, as it's a bit hacky and I have no confirmation that this will work until the review process has been completed. However, you can use the FB API to determine whether the user viewing the app is a specified test account or not by adding conditionals based on the user ID. It will also help if you make the test account an automatic user of the app on user creation.
For example, if you want to include new functionality, check if the user ID is a specific test account ID or not. If it is, display it. If not, display something else.
I have written a desktop application and on the main interface there is a button to launch a Facebook status update form (it is a different program). In order for the status update to work, I need the publish_actions permission and for that I need to submit my app for review.
When I try to do that, it asks me to add a platform but when it comes to windows, it only accepts Windows 8 apps.
What can I do? Any help would be appreciated.
Hello I had the same problem and found the solution.
What you have to do is submit it as Website and state you are submitting a Desktop Application. I submitted as Website following a suggestion from the Facebook Team in a Bug Report.
However, at first they rejected my review submission with the standard message "Your Website does not support Facebook Login". I submitted again explaining I have a Desktop Application and I was choosing the Platform Website following their suggestion from that link, and then they read my step-to-step screenshot instructions, approved some of the items and gave me feedback on the others.
Good luck!
I'm trying to add a "Register with Facebook"-button on our website, and I want this button to have the user_birthday privilige.
Simply put, our service requires the users birthday.
So, I we need our APP to clear submission.
Problem is that the Facebook team wants to use the APP in order to approve it. (Of course they do). But we do not want to add a broken "Register with Facebook"-button to our website. (It's broken as long as we don't have the birthday privilige).
There must be someone else who've faced this problem. Is it possible to direct the Facebook team to our test server? Which is located on another URL. Having a broken button on our website for up to seven days makes no sense..
I received this answer from David Doyle on Facebook:
"You can direct us to a test server or staging area and we'd be happy to review from there.
Just be sure to provide any login credentials in your review instructions.
Most developers start their review instructions with a note that says "please find our staging area here " that might be easier for you than changing your app settings."
Good enough for me! :-)
https://www.facebook.com/groups/fbdevelopers/718033091573541/