Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

CreatedAt string from Twitter is sometimes null #13

Closed
steve-swanson opened this issue Nov 21, 2014 · 3 comments
Closed

CreatedAt string from Twitter is sometimes null #13

steve-swanson opened this issue Nov 21, 2014 · 3 comments
Labels

Comments

@steve-swanson
Copy link

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.

@abjerner
Copy link
Owner

I'll be happy to look into it, but I haven't seen this before, so do you have any examples on tweets where the date is NULL?

@steve-swanson
Copy link
Author

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!

@abjerner
Copy link
Owner

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants