Aaaah, I see! Thank you! Will do that now and then report back if it worked :))
When signing up, I get an error message:
{
“error”: {
“message”: “Unknown path components: /oauth”,
“type”: “OAuthException”,
“code”: 2500,
“fbtrace_id”: “EvATeCyHSo8”
}
}
Seems to be the “https://graph.facebook.com/v2.12/dialog/oauth” part in Login Dialog Redirect. At least when I put this into the browser, I get the same error message, but what else should I put there, it’s what you have there in your example, too @NigelG 
https://www.facebook.com/v2.12/dialog/oauth is what you need I think.
1 Like
It looks like we’re getting closer!! 
Now it just tells me
“Please log in to access this data”
But then goes blank without redirecting much. But when I try initialising the call it still says:
"There was an issue setting up your call.
Raw response for the API
“{"error":{"message":"Invalid OAuth access token.","type":"OAuthException","code":190,"fbtrace_id":"D6d7twqxYXy"}}”"
And when I try logging in without the debugger it tells me:
API connector error: the Oauth2 API Facebook is not tested yet. Please run in with the debugger to validate your settings.
And I’m getting this now:
I have added all the whowho.bubbleapps .io/index and co. to the facebook redirect URIs, so I’m not sure what this is referring to.
****** We’re back to no error messages, but this and nothing else:
“Please login”
After I added another URL
Solved this part:
Select “Use generic redirect URL” and add it in your Facebook app’s login settings!
Then it worked.
But now when I click on “Initialize Call” I still get this:
my settings for the call:
Ant idea where this issue might be, @NigelG?
Also, when does more show up in the workflows, so I can actually use the data? Because when I saved one call that actually worked, it still only showed this:
Is your scope public_profile ?
You may need to go back and login again then initialise straight after.
Do you get this message ?
I did.
So current status:
scope=public_profile
login with Facebook API
I correctly get: name and picture and gender, but I can’t access them in my workflows with “Current User’s Name” only through “Get data from API”
I wanted it like the Bubble plugin, so I can distinguish between “current user” and “current page user”
Plus: When logging in with the API connector, unlike with the Bubble Facebook plugin, the email doesn’t get automatically saved into the new user! I could create a new “email” field, but can’t access the “built in” email field.
AND: Since I “log in with facebook” through this API, while it does create a new user, it doesn’t lead me through the workflow to the new main page.
No, that is right. It is annoying.
If you ask for the email in the scope, then you can request it via https://graph.facebook.com/v2.12/me?fields=gender, email
But it does not always get pulled back in the Login.
Yes.
So generally it is working, but I still want to create the user with the Bubble FAcebook plugin, since that one actually gives me the user with an email address. But I really need the gender. So I created this:
But now, every time I “login with facebook”: it takes my name + email + gender (female)
When then a friend “logs in with facebook” (Main Facebook Button) afterwards (different location, different device, different everything): it sets MY gender to male (in this case) and creates correctly a new user with his name and his email but NO gender
Tried the other way round:
He “signs up with facebook” (Main Facebook Button): name + email + gender (male) all correct
I “signup with facebook” (Main Facebook Button): sets HIS gender to female, logs me into HIS profile and creates a new user (me) with correct name and email but NO gender
It feels like a bug, but it’s probably a mistake in my API settings?
Any ideas why that might be happening?
I really just need the public profile with gender, which is part of it. But 1. every tiem I set up the login with it, it doesn’t go further in my workflow and 2. it doesn’t create the “builtin email” anyway.
Encountering very similar issues in my app as well. I think the issue here is that the Bubble API connector isn’t recognizing the fields we should have access to based on scope. For instance, public_profile is enabled by default, but when using the API connector to authenticate, we don’t have access to those fields. (email, profile pic etc) as you pointed out.
I’m personally working around this limitation, but will be attempting to build out a plugin for FB specifically to address this issue unless the bubble team gets to it first (unlikely) or I abandon all hope and sponsor a plugin with Salar/Cobubble (more likely).
1 Like
I think this was raised as a bug a while ago, the issue with multiple signups overwriting each other. I know I had similar problems but that was when the user was already signed up.
The email not being returned is not right, and I am sure it used to be. Email is not part of public_profile.
It should be part of this …
I changed User ID key path to be ID, and now it is being stored.
But email is not. Despite it being asked for…
Just tried changing it to “id” in order to get the email addres. Unfortunately it still doesn’t work.
Also the picture I get from the profile is tiny and super pixely
It’s not the nice porfile picture I get with the Bubble Plugin. The API connector only gives me for “picture” this:
But anytime I add “profile_pic” to the GET request, I get an error message:
Raw response for the API
“{"error":{"message":"(#210) This call requires a Page access token.","type":"OAuthException","code":210,"fbtrace_id":"Hw9nl6sO9s0"}}”
As soon as I remove the “profile_pic” (as shown in the Facebook graph API explorer), the other things work (despite the “picture” being super bad quality.
I’m also trying to work around it but failing miserably!
Please, let me know if you find a way to login the user getting all the public profile fields. That’s really all I’m trying to go. Unfortunately, Bubble’s plugin does only half the job. 
1 Like
Any update to this?
Were you able to solve this issue @NigelG?
I will have another look over the weekend for you.
Thank you so much!