Is there a way to check count of test users created for the facebook app.
The maximum number of test users that can be created is 2000.
https://developers.facebook.com/docs/apps/test-users/
Related
Is there a way around the rule where Google says that test users that you remove from your unpublished app will still count against the allowed user cap?
Our app is still in private beta so we're okay with the limit of 100 users but I don't get why if we remove a user, it won't free up space for another tester.
my Google Cloud Platform App is in Test mode in order to be later submitted to Google for approvation.
This App was proviously in production, so there are more that 100 accounts authenticated to the APP.
This means that I'm above the limit for 100 max users in Test mode and I cannot add new account i need to make some test.
I'm not able to find a way to list the currently authenticated users and remove them.
Anyone could help?
limit of 100 users reacher
There is no way to list the users who have authorized your application, there is also no way for you to remove them. You need to wait for verification of your application before you can add new users.
option one
If you have refresh tokens for the users you can try to revoke them and see if that grants you another additional users. However my research says this will not help as the 100 limit appears to be the number of users who have granted your application authorization not the number of users who currently are authorized by your application.
option two
You could also create new project and go though the verification process again, this time taking care not to gather have to many users before the verification process has been completed.
I have published one application which uses facebook login. I have created facebook developer account and get app id for my application and it was working fine. Its been a year I have released my application on google play.
But now I am not able to access my facebook account. I am facing this error "Security check - This account isn't eligible for this process for MY App name"...
What I am thinking now, is to get new app Id from different fb account and and change that in my application and give update of my application. But my question is, the existing users, who have not taken the updated version can still use facebook login, with previous app id. I mean can my application have two different app id from two different fb account?
Thanks in advance,
Krishna
I know you get a users "likes" from the graph api by doing
https://graph.facebook.com/v2.10/userid?fields=likes
However this only works with Real User Ids. What I don't understand is how is my app supposed to get the users "likes" if the App can't get the real User ID?
Originally I was testing this with my Facebook account and everything worked. But I'm now guessing this because I'm assigned as a developer to the App, I was get the Real User ID.
I'm doing some kind of load testing with Facebook Test Java API for some app using fb authorization.
Since I'm doing selenium test in parallel, i'm able to see some effect:
I'm creating some test user
I get it's loginURL
I'm authorizing in selenium-driven browser with this loginURL
I'm creating many other users, each of them doing some stuff and becoming friend to the user from point 1, that is seen in selenium-driven browser.
At some moment I see this user logged off from facebook in browser. The exact moment is not clear, since the other test users are created and made friend with the target user in parallel threads, but it looks like this happens when i create 500 users.
When I try to log in again with loginURL obtained at step 2 it is still impossible. The fb redirects me to the login page.
It is possible to create much more than 500 users (at least 2000) with the api before the api will return the error, but the logging off is observed much before the reaching this limit.
The question is what is the limit of test facebook users supported with no problems?
And also, I've noticed that at beginning of the test test user access tokens worked okay, but by the end of the test all they were invalid and graph api didn't allowed to upload photos using that tokens.