-
Notifications
You must be signed in to change notification settings - Fork 1
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
No tweets at all! #2
Comments
I think a lot of tweets aren't geocoded any more, so you wont get much
coming through :(
…On Sat, May 6, 2017 at 6:36 PM, BasharAG ***@***.***> wrote:
I configured everything correctly up to the point of running node index.js
The server runs and the map shows, but it has no tweets at all
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#2>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AB1DAAFD3CUV8JZ-JcMx0EVXsZouGP52ks5r3PYIgaJpZM4NS7oj>
.
|
You should still get some tweets coming through though – this repo is live here if you want to see the UK geocoded responses. @BasharAG Are you getting any responses at all? Seems like if everything else is working it would be your connection to the Twitter API that is the problem. Have you tried outputting some console logs to check that the connection is being created? |
@ashleynolan ashleynolan Yes, I am getting your responses. I checked your live rep. I can see the colo-coded circles, but no tweets are showing on my end. I tried using 3 different Twitter account with no working results. |
Are you getting responses showing in the terminal/console of your own application? Best thing to do would be to log the flow of the application and that way you can see if the connection to twitter is successful and to log out in your terminal any messages being received. |
I configured everything correctly up to the point of running node index.js
The server runs and the map shows, but it has no tweets at all
The text was updated successfully, but these errors were encountered: