Closed GoogleCodeExporter closed 9 years ago
I got the same problem too....
Original comment by haveanew...@gmail.com
on 13 Nov 2010 at 12:54
Same here. 'user' property is null, rather than an object containing the user's
full information.
Original comment by jchap...@gmail.com
on 23 Nov 2010 at 1:08
This just seems to be the way the code is designed, which seems odd. I don't
know about the availablePermissions parameter, but the user property is
populated in the AIR version of the SDK, if you pass in an access token. If
you do that, the SDK calls the verifyAccessToken() function, which calls:
api('/me', handleUserLoad);
and
protected function handleUserLoad(result:Object, error:Object):void {
if (result) {
session.uid = result.id;
session.user = new FacebookUser();
session.user.fromJSON( result );
if (loginCallback != null) {
loginCallback(session, null);
}
} else {
if (loginCallback != null) {
loginCallback(null, error);
}
}
}
I guess it's just a case of duplicating this logic manually in your own code,
for now.
Original comment by psyked84@gmail.com
on 23 Nov 2010 at 11:13
How can I find out current extended permission that user have? Is there any
other way to find out?
Thanks.
Original comment by tohj...@gmail.com
on 11 Dec 2010 at 9:09
If you know what permission you're looking for, you can obtain information
about it from an FQL request, such as:
Facebook.fqlQuery( "SELECT publish_stream,email FROM permissions WHERE uid =
me()", onFQLResponse );
and
function onFQLResponse( success:Object, failure:Object ):void {
if ( success ) {
for ( var i:String in success[ 0 ]) {
trace( i, "=", success[ 0 ][ i ]);
}
} else {
trace( "FQL query failed." );
}
}
Original comment by psyked84@gmail.com
on 29 Dec 2010 at 10:59
Original comment by edwar...@gmail.com
on 12 Jan 2011 at 10:59
Muchas gracias psyked84, con tu ayuda organice un codigo para validar permisos
de un usuario en una aplicación. Te doy la gracias en mi blog.
http://graciasinternet.blogspot.com/2011/05/verificar-permisos-de-facebook-de-tu
.html
Saludos.
Original comment by elkin0...@gmail.com
on 25 May 2011 at 4:50
Original issue reported on code.google.com by
treest...@gmail.com
on 25 Oct 2010 at 11:02