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](https://developers.facebook.com/docs/reference/androidsdk/authentication/) 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?