-
Notifications
You must be signed in to change notification settings - Fork 599
api.getThreadHistory returns and empty array #486
Comments
Do you get any errors? Are you sure the threadID is correct? |
🤔 |
@leonardlabuneti please show us a sample of non-working code 😄 |
The function returns no error and an empty array, the threadID is correct and the same code used to return messages a few days ago. I will come back with my code example. Thank you |
getThreadHistory got response : null [] The threadId used is correct, the getThreadList works ok and I am using the same threadId I get from this api response |
Mmmh I just tried here with one of my chats and it worked. Are sure there are any messages in that thread? Are you sure the bot is in the thread? |
There are messages in the thread and I am in that thread, I will double check my code. Good to know it works. |
I'm using master actually. There are definitely issues depending on where you live though, since FB rolls out changes weirdly across the world. Seems like 1.4 also works for me. |
Could someone try this code please ? |
I doublechecked the issue was my testing fb account, it looks like you get some kind of block if you hammer the fb servers. thank you guys |
Thanks for following up @leonardlabuneti. As we state at the top of our README, facebook employs a number of rate-limiting measures to avoid people hammering them and this api explicitly doesn't attempt to circumvent them. |
api.getThreadHistory returns and empty array version 1.4.0 called like the docs
getThreadHistory(threadID, amount, timestamp, callback)
The text was updated successfully, but these errors were encountered: