Closed victoriagomezv closed 4 years ago
I’m not sure about that callback URL. We’re authenticating with the API so it shouldn’t be an issue and the instructions on that screenshot say to leave those blank.
Would you mind sending me a screenshot of your heroku config output and your local_settings.py so I can troubleshoot locally on my end? Here’s how to email me.
Hi there! I'm having the same exact issue. Here's what comes up on my command prompt:
@samiaab1990, can you share your heroku config output and local_settings.py so I try it on my end? Here’s how to email me.
Also, this looks likely to be a duplicate of https://github.com/tommeagher/heroku_ebooks/issues/57 Can you read that thread to see if it helps solve this? @samiaab1990 @victoriagomezv
Also, this looks likely to be a duplicate of #57 Can you read that thread to see if it helps solve this? @samiaab1990 @victoriagomezv
Actually, yes, this solved my issue! I was looking at an older tutorial where the local_settings.py contained the variables, so I was confused. Thank you so much.
I was additionally wondering if there is a way the bot can grab source tweets from private account, given that the private account is my main twitter account. I unlocked my account to test the bot but may want to put my account back on private in the future
I haven’t looked at the API in quite a while, but I think if your bot follows your private account, this should work fine, @samiaab1990.
@victoriagomezv I’m going to close this issue as a duplicate but if that other solution doesn’t fix your issue, we can reopen this discussion.
keep running into this issue when running heroku worker
when i run "heroku config" my API keys show up fine
i did change the local settings file because a tutorial i followed prompted me to replace the Haroku variables with the keys themselves (Tom himself said not to do so) but still having the same issue
have a feeling it may have to do with this Twitter request, i don't see steps for filling it in any tutorial but it's requested of me when I create a new dev app. I had it previously filled with "http://127.0.0.1/twitter/callback" per a Google search but think that might be the culprit as it relates to oAuth