Skip to main content

Facebook Sdk Callback Mechanism in Android

manages the callbacks into the FacebookSdk from an Acitivity's or Fragment's onActivityResult() method.

This javadoc of  CallbackManager class from facebook sdk doesn't explain very well on how the facebook sdk interacts with our app components. It exposes just one public method : onActivityResult() which is to be called by our app's ui components from their onActivityResult.

We create an instance of class CallbackManager, using CallbackManager Factory which essentially returns a new instance of CallbackManagerImpl, the only implementation of CallbackManager interface in facebook sdk.

CallbackManagerImpl : 
So, this class gets callback from our app components. But what does it do with that? 

Different facebook components such as the LoginManager, AppInviteDialog register themselves with this class to be invoked for their particular case. They do so by the publicly exposed  registerCallback method and register themselve against one of the request codes defined in CallbackManagerImpl.RequestCodeOffset. These two images explain this very well :










But when does these different facebook components register these callbacks?
They do that when we register our callback on these components. Sounds like a cycle, right? It is.

Let's take the example of Login Manager.

When we are using the facebook sdk to let the user log in through facebook, we register a callback on the LoginManager instance through its publicly exposed registerCallback method and with that, pass it the callbackManagerImpl instance that we have created. After this, the LoginManager registers itself on that callbackManagerImpl instance and makes sure that it'll call us when it gets back a callback. The last part, from where does callbackManagerImpl gets the callback? If you don't have an answer for this, I suggest you to read this post again.

I've tried to summarize everything is this final image : 

  

Let me know of any doubts in a comment below.
Labels:

Comments

Post a Comment

Popular posts from this blog

Android : AbsSavedState cannot be cast to $SavedState

Android AbsSavedState cannot be cast to $SavedState I came across a strange crash today. This is the stacktrace : Fatal Exception: java.lang.ClassCastException: android.view.AbsSavedState$1 cannot be cast to android.widget.ScrollView$SavedState at android.widget.ScrollView.onRestoreInstanceState(ScrollView.java:1810) at android.view.View.dispatchRestoreInstanceState(View.java:14768) at android.view.ViewGroup.dispatchRestoreInstanceState(ViewGroup.java:3123) at android.view.View.restoreHierarchyState(View.java:14746) at android.support.v4.app.Fragment.restoreViewState(SourceFile:470) at android.support.v4.app.FragmentManagerImpl.moveToState(SourceFile:1326) at android.support.v4.app.FragmentManagerImpl.moveFragmentsToInvisible(SourceFile:2323) at android.support.v4.app.FragmentManagerImpl.executeOpsTogether(SourceFile:2136) at android.support.v4.app.FragmentManagerImpl.optimizeAndExecuteOps(SourceFile:2092) at androi...
2 comments
Read more

Android Tip : Handling back button in Fragments

Android Tip : Handling hardware back button in Fragment and DialogFragment This post explains how to handle hardware back button in a Fragment OR DialogFragment . In DialogFragment, it’s quiet straight forward to achieve this. You’ve to get the dialog instance and set onKeyListener on it : if (getDialog() != null ) { getDialog().setOnKeyListener( new DialogInterface.OnKeyListener() { @Override public boolean onKey (DialogInterface dialog, int keyCode, KeyEvent event) { if (event.getAction() == KeyEvent.ACTION_UP && keyCode == KeyEvent.KEYCODE_BACK) { Timber.i( "hardware back button pressed" ); } } }); } This can be done in the onViewCreated callback. For fragments, this method doesn’t work and fragments doesn’t have a direct callback to catch this event. So in this case, the approach that we follow is : You...
Post a Comment
Read more

Android Material Showcase View - Part 1

In this series, I'll be talking about a library which is used by a lot of android developers for showcasing their in-app content,  MaterialShowcaseView . I used this library sometime back for my work and had to modify it to fit my needs. In this process, I ended up digging it a lot and would like to share what I learned. The original library offers a fix set of features, which are demonstrated by the screenshots in the README. Let's jump on the technicalities right away. The original library offers two things : 1) highlighting a view ( see the README to know what I mean by highlighting here) 2) showing a content box that tells user what the highlighted view is about. Here's how it does this : The library adds a direct view child ( this class ) in the window decor view, so that it's drawn on top of your activity's view ( here ). Then, for drawing the overlay and highlighting our view, it overrides the `onDraw()` method of this view and uses android...
Post a Comment
Read more