2
Vote

Toolkit 3.0, FQL problem

description

I'm trying to upgrade my Toolkit 2.1 app to 3.0, and I can't figure out how to get FQL to work. I keep getting the following error:
 
Object reference not set to an instance of an object.
Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.
Exception Details: System.NullReferenceException: Object reference not set to an instance of an object.
 
Source Error:
Line 292: strQuery = "select uid, name, pic from user where uid " + inStmt;
Line 293: Facebook.Rest.Fql q = new Facebook.Rest.Fql(Master.Api.Session);
Line 294: string result = q.Query(strQuery);
 
The 'q' variable is non-null.
 
Any ideas??

comments

sanjunaik wrote Nov 27, 2009 at 5:36 AM

Happens to me too... I wonder why the Work Item Details says "Low Impact"... not being able to do any FQL is "low impact"? lol

tdubroff wrote Nov 27, 2009 at 6:56 PM

So far, this toolkit is a sham. I think I'm heading back to the 2.1 version until Microsoft and Clarity get their act together. The 2.1 version barely works but at least its better than 3.0.

patja wrote Dec 3, 2009 at 5:11 PM

I agree the developer engagement should be better...but in my experience FQL does work. I get responses from this FQL just fine:
                    var response = api.Fql.Query(String.Format("SELECT first_name, last_name, locale from user where uid = {0}", user.UserID));

tdubroff wrote Dec 4, 2009 at 2:31 AM

Thanks very much patja. I've confirmed your code does allow the FQL to work. I imagine then, that my code shows a bug somewhere in the FDT 3.0.