Facebook is about to sunset (abandon) Facebook Connect, forcing developers with working apps and sites to do everything all over again.
It would really be nice if they bought us dinner first. But I digress.
One casualty of this change early on is making Facebook OAuth 2.0 authentication scheme work on Android.
Or not, as the case is proving to be.
If you’ve written an OAuth implementation on Android, more likely than not you’ve used a library like signpost and implemented a custom protocol to direct your callback to an appropriate intent in your application to handle the callback package.
Except that apparently Facebook only recognizes http and https as “legit” callback protocols.
In short, for the time being, those of you looking to do an Android version of the new Graph API and FB OAuth 2.0 scheme are hosed.
Logorrhea 
Would the desktop flow work for you? http://developers.facebook.com/docs/authentication/desktop
LikeLike
Would have to give it a whirl and see, if I have some time over the weekend. Thanks.
LikeLike
whats the problem in using http as a callback url?
first of all you can register a hostname on the uri in the intent declaration. the youtube app also does this.
second, unless you (for some reason) need to use the system browser for the authorization page, you could show it in a webview inside your app where its easy to intercept the callback url and no need to restart the app through any url-intent at all.
LikeLike