Make sure we initialize the login callback from fbDidLogin so it is still

[dokterbob]

Make sure we initialize the login callback from fbDidLogin so it is still fired when loggin in from non-multitasking environments. Fixes #14.

[dokterbob]

Meanwhile, I have merged your latest changes into my fork and removed some of the xcode slug you accidently checked in - it's safely ignored from now on.

Also, I noticed you moved the login to Facebook's request didLoad, which seems to make a lot less sense than having it in didLogin - which is where I put it (and where it seems to work just fine).

Lastly, I am wondering why you think it is a sensible design decision to automatically request the uid after logging in, per se? As mobile requests are quite costly and we should be perfectly able to do this explicitly, this seems to be unnecessary - but maybe I have missed something.

Anyways, thanks for writing up such a great product, anyways. :)

[davejohnson]

Having a look at this. I am not an obj-c pro so bear with me :)

The reason that I make the request for the uid is so that everything works as per the FB JS SDK. In the normal JS SDK the session object contains the uid once logged in, so just trying to keep it the same. I talked to guys at FB and this is the best / only way until they provide the uid in the native mobile SDK's.

[shazron]

hi @dokterbob you need to rebase your pull-request branch before this can be auto merged through Github. thanks

[dokterbob]

@shazron There you go. Also (accidentally) merged in a patch which more rigorously gets rid of some of the XCode leftovers in the example (a follow-up on b57793f and 79dc5cd).