I've integrated Facebook's AccountKit as the login system for my app. It has some bugs but usually works fine.
My developer reported a fairly bad experience though recently. He had to restart his computer, thus clearing the sessions, and when he went to re-login to the app via AccountKit, he realized that the same email address he had been using returned a different user_id than the one it had been returning previously. This of course caused a problem in that our backend could not find any account relating to the new Accountkit id.
I've been unable to find much information about this. I'm wondering if this is a bug or a feature! Any further illumination on this subject is greatly appreciated!
Every login will return a different Access Token or Authorization Code as documented here: https://developers.facebook.com/docs/accountkit/accesstokens
If you get the Account ID from the Access Token, it should always be the same for a user entering the same email address. What you're describing sounds like a bug and if you can still reproduce it, you should submit a bug report and someone will look into it. https://developers.facebook.com/bugs/
Related
Alright, strange problem that I'm encountering:
Our website uses Facebook to log in. Currently I'm using HybridAuth to get the user's information - I'm storing the identifier ('app_scoped_user_id' as I've now learned), and using it to check when people try to sign up or login through Facebook.
A few weeks ago, we went through a total rebranding of the site, separate domain entirely. I ended up creating a second Facebook app through their developer console for the new domain, because it wouldn't let me add that domain in the settings of the original one. I wasn't aware that the identifier coming back was within scope of that particular app - hoping that this won't be a major hurdle to fix.
So a problem occurred where a user went to sign up with Facebook, and was logged in as an existing user who had signed up under the old domain - so the app_scoped_user_id for this new user matched the app_scoped_user_id for the old user and signed them in. Clearly an issue.
Now the weird part is that for old users who had signed in through the original app are signing in fine through the new app - definitely sending through the new keys, connecting to the new app, but apparently the app_scoped_user_id being returned is identical between the two apps.
SO... am I not understanding things properly? If the app_scoped_user_id is different between two Facebook apps, is it possible to bring over the used ids from one app to the other?
EDIT******
Problem solved... if anyone else ends up making the same silly mistake I made, this is how I solved it:
Since the info coming back from Facebook includes their e-mail... just checking their e-mail field to see if they already exist, and assigning the new token to that entry. Obviously there could be a few cases where either the user changed their email on Facebook, or changed their email within our app, but our user base isn't too large yet, so glad to set this right now.
I'm sure this is something blindingly obvious, but I can't work it out.
I've added an admin and a tester user to my app (and I mean they're real people as opposed to the generated random named user that FB offers) but after a couple of weeks they're still listed as '(pending)' and they're unable to login to the web page that I've written using their Facebook account. OAuth responds with an error:
Sorry, this feature isn't available right now: An error occurred while processing this request. Please try again later.
I appear to be able to login just fine and can test the [currently] limited functions.
Our web page is right at the beginning of development but it's now at the stage where I'd like real people to mess around on the page and give me feedback.
The two users haven't received any messages - I sort of expected they'd get something in their inbox asking to confirm their role with the app.
So how do I go about getting real people to be test users? Have I missed the point of the test user role?
As of this writing (things change), have the Facebook user go to https://developers.facebook.com/requests/
They will need to be logged in to Facebook.
There should be listed one or more pending requests that they will need to confirm. If the Confirm button(s) is disabled, they may need to register as a Facebook Developer before the Confirm buttons are enabled.
Good afternoon, I am having trouble accessing any of the left-menu items in the Sandbox. I am able to login.
I see the same issue in every browser I have (Chrome, FFX, Safari, IE9) and I have attempted to login using an incognito session. As best I can tell, the error is that the browser never receives a response to an AJAX request to https://www.beta-sandbox.paypal.com/cgi-bin/webscr?cmd=_profile-display-handler&tab_id=ACCOUNT_SETTINGS&&view_requested=MiniPage&_=1367858742397.
I notice this thread, can't see sandbox test account 'Profile' on some computers, indicates a fix on 3/19 and it's 5/6.
I have seen a few workarounds for direct URLs, however, I am unable to figure out what the direct URL to edit the IPN settings would be.
Any help would be appreciated.
This is a known issue that we are working to resolve. I will be sure to follow-up as soon as this issue is fully resolved. In the meantime, you should be able to access your IPN settings using the following link:
https://www.sandbox.paypal.com/us/cgi-bin/webscr?cmd=_profile-ipn-notify
Thanks,
I have done much searching but not able to find a solution.
Trying to get my Twitter to Facebook feed setup but getting this error:
"Facebook reported an error. The error has been reported to our engineering team. Please try again as it might be a temporary problem"
From what I can gather it may have something to do with an old account that has been deleted, but I have no idea how to resolve this and nor do a lot of other people.
First up: this is not a programming question since it's not related to the Twitter API but to the Twitter interface. Therefore, it's actually to be regarded as "Off-Topic".
To give you a helping hand nevertheless:
What you are describing is a known bug Twitter bug. Check https://www.facebook.com/help/community/question/?id=110412992466716 and https://dev.twitter.com/issues/998
The problem comes up when your Twitter account was previously connected to another Facebook account that you deleted/deactivated without removing the Twitter app first. Now that you try to connect to a new Facebook account, Twitter still tries to authorize using the old credentials of that other account.
Currently, your only hope is to ask Twitter to manually remove the old account credentials from your Twitter profile's backend. From what I've been reading, Twitter frequently fails being cooperative in that point... you can only ask and hope someone at Twitter is able and willing to manually correct their bug.
I'm using the official FBConnect library for iOS and trying to get it working in my iPad app. Here's what's strange: when my friend logs in using the call to authorize:permissions:delegate, everything works fine: the dialog asks for his authorization to connect to Facebook, the fbDidLogin delegate method gets called, all is well.
However, when I try to login, the dialog never changes. The keyboard is dismissed, the password field is cleared and it just sits there. The issue is the same in both the simulator and on the device.
Here are the things I've checked and triple checked:
My login name and password are correct. If I do put in the wrong password, an "invalid username/password" message appears, and that isn't happening.
The application is not in sandbox mode.
The Application ID is correct (my friend can login without problems).
Some additional information:
Original application was created by my friend.
I created a second FB app and put in the new Application ID
My friend can login with the new Application ID
I can log in to neither.
This appears to suggest that there is something different about my friend's account, rather than the app itself.
We've been banging our heads together on this for a couple of days now. What could be causing this behaviour? Why isn't an error being generated?
Edit: It seems there are a lot of people affected by this, so in the interest of trying to find an answer, I've added a bounty.
There appears to be a server-side problem with Facebook logins as noted here:
http://github.com/facebook/facebook-ios-sdk/issues#issue/95
People have said that if they change their password on Facebook they are subsequently able to log in using the Facebook-iOS-SDK downloaded from github. Obviously that is a poor long-term solution and would be unacceptable in an app released through the App Store. On the bright side, there seem to be reports of similar login problems logging in from apps on other platforms as well.
Update: Facebook has a bug filed on this subject that can be viewed here:
http://bugs.developers.facebook.net/show_bug.cgi?id=13199