LinqToTwitter no longer checks for expired Access Token

Jun 14, 2014 at 2:33 AM
Hello,
Before async, a very useful feature, came to LinqToTwitter, an error used to pop up when any method was called with an expired Access Token if the user had, say, revoked access to the app. Now, the error seems to be lost somewhere in the async operation. For example, calling
await (from user in TwitterCtx.User
                            where user.Type == UserType.Lookup && user.UserIdList == ids
                            select user).ToListAsync();
continues to run without a valid Access Token, and no error is shown. The operation is simply never completed, leaving the program waiting for something that isn't coming back.
Not even a call to account/verify_credentials shows that an Access Token is invalid.
Is there anything that can be done to fix this or check whether or not the Access Token is invalid?
Thanks for your help!
Elliott
Coordinator
Jul 1, 2014 at 3:42 AM
This discussion has been copied to a work item. Click here to go to the work item and continue the discussion.
Coordinator
Jul 1, 2014 at 3:43 AM
Hi,

I'm not sure what happened, but I copied it to an issue to take a look at.

@JoeMayo
Jul 2, 2014 at 4:15 AM
Hi Joe,
It turns out I was still listening for a WebException as I did from the older version rather than a TwitterQueryException. So, my catch blocks were never run.
Sorry for the confusion, and thanks for your response!
Elliott
Marked as answer by elliottvforde on 7/1/2014 at 9:15 PM