You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
TwitterUtils.ParseDateTime throws a null reference exception at times because of a null string from Twitter. I don't know if this is the same for the ParseDateTimeUtc when parsing the date/time string for tweets, but I would assume it could be an issue as well.
The text was updated successfully, but these errors were encountered:
Sorry I didn't provide more information when I created this issue. We were doing some processing on Twitter users and saw this error, but I didn't have the user information. Basically it was the CreatedAt on the TwitterUser that was returned as null from Twitter and then the ParseExact was failing. I tried to run through the users again this morning but didn't get the error. It was consistent on Friday, but maybe it was only a temporary issue.
Thanks again for all of the work on the other issues too!
Seems like a temporary issue with Twitter. I can replicate this with the users/tweets that I have tested, and the API documentation doesn't mention that the creation date can be null. I will keep this in mind, but close the issue for now.
TwitterUtils.ParseDateTime throws a null reference exception at times because of a null string from Twitter. I don't know if this is the same for the ParseDateTimeUtc when parsing the date/time string for tweets, but I would assume it could be an issue as well.
The text was updated successfully, but these errors were encountered: