I know this was an issue in January, but I have version 1.0.1.25 and it still isn't working for me.
Any advice?
Comments: ** Comment from web user: tcap479 **
This isn't the January problem. That problem caused an "unauthorized" message to appear in NodeXL.
You didn't say which Twitter importer you are using (Search, User or List), but Twitter does sometimes return empty networks to NodeXL, and sometimes it gives NodeXL a partial network and then quits. I think you are seeing examples of both. It's not predictable, and it's something that NodeXL has no control over.
If you get this again, you can try importing the network again to see if Twitter is just temporarily restricting things. If you'd like, you can also tell me which importer you're using and what all the settings are in the "Import from Twitter..." dialog box, and I can try it here to see if I get different results. If it's a huge network that could take hours, though, I might have to try a more limited import.
-- Tony