Currently I’m writing an adapter class to provide a convenient way for communication with the facebook API.
The way I thought about using it is to run the authentication when the app is starting up, downloading user’s private picture, and later in the app publishing updates on users facebook wall using an AsyncFacebookRunner.
However flipping through the documentation it seems for every authorize() implementation the first parameter have to be an activity.
void authorize(Activity activity, final DialogListener listener):
And here I begin to wonder.
Thinking about activities and life cycles what will happen when the activity I threw in will be destroyed? Wouldn’t the reference for this object Facebook.mAuthActivity become invalid as well.
I see the logout() method “only” asks for a context.
String logout(Context context) throws …:
context – The Android context in which the logout should be called: it should be the same context in which the login occurred in order to clear any stored cookies
From what I see I can not guarantee the “login-activity” will still be present as app’s uptime increases – actually the opposite is more likely.
Are there any special situations I should consider to prevent the app form total crashing in a later state?
using facebook API for the android is easy and in your case you don’t need to save the Facebook instance the only thing you need is to save the authKey of the facebook on the first login then you can use it anywhere.
this means that you can create more than one instance of the facebook object in mutiple activities based on the authKey.
Otherwise you need to put this facebook object in a singleton handler to save it among the application :
but this way is not the best way to implement the code you need to create a Facebook instance for each activity using the authKy.