BootBot.js: TypeError: Cannot read property 'forEach' of undefined
See original GitHub issuetag: needs-investigation
Once in awhile, I get this error in my logs, but I can’t seem to find the cause:
TypeError: Cannot read property 'forEach' of undefined at data.entry.forEach(/app/node_modules/bootbot/lib/BootBot.js:408:24)
I’ll update if I get it.
Issue Analytics
- State:
- Created 6 years ago
- Reactions:3
- Comments:6 (1 by maintainers)
Top Results From Across the Web
TypeError: Cannot read property 'forEach' of undefined when ...
get is a method. guild will therefor be a function. A function doesn't have a members property -> undefined -> discord.js ...
Read more >Cannot read property 'forEach' of undefined in angular object ...
core.js:6210 ERROR TypeError: Cannot read property 'forEach' of undefined at UpdateUserComponent.ngOnInit (update-user.component.ts:34).
Read more >A brand new website interface for an even better experience!
TypeError : Cannot read property 'forEach' of undefined (Heroku logs)
Read more >Cannot read property 'forEach' of undefined discord.js-discord.js
Coding example for the question TypeError: Cannot read property 'forEach' of undefined discord.js-discord.js.
Read more >ERROR TypeError: Cannot read property title of undefined
HEY, SET YOUR LIKE THERE ! ... Your browser can't play this video. ... Solved: ERROR TypeError : Cannot read property title of...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Update: if you only want to stop receiving these errors there is a simple way to do that:
standby
No more TypeErrors, which is what I was after in my case.
@mraaroncruz this is a message that triggered this notice for me:
The interesting thing here is that everything still works fine, and I can continue the conversation without a problem.
Edit: Looks like it’s something to do with the Handover feature (https://developers.facebook.com/docs/messenger-platform/reference/webhook-events/standby/)