Closed nibzo1 closed 6 years ago
An interesting observation while fixing this issue was that when the user not found
error caused the code below to stop listening correctly. We have not been able to figure out what is happening here but im assuming that this.userById(event.in_reply_to_user_id, true)
this code is updating some state objects with an incorrect value, preventing the listen logic working for the correct user
Rx.Observable.merge(...R.map(client => client.listen(), R.values(clients)))
.subscribe({
next: message => console.log(JSON.stringify(message, null, 2)),
error: err => console.error(`Something went wrong: ${err.message}`),
});
Thanks for this. Let me look in to that second comment of yours before we get this merged up.
Great thanks for the review. It should be easy to recreate the scenario
Issue:
User not found
error occurs when listening for a TweetChanging
event.in_reply_to_user_id
to useevent.in_reply_to_user_id_str
as described in https://dev.twitter.com/overview/api/twitter-ids-json-and-snowflake fixes user not found error.From Twitter Documentation
Fixing
user not found
in broid twitter integration.