Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
removing a user's messageReaction seems to result in error.
See original GitHub issuemy code is literally
client.on('messageReactionAdd', (messageReaction, user) => { messageReaction.remove(user).catch(console.error); });
always results in an error '{"user_id": ["Value \\"undefined\\" is not snowflake."]}'
Issue Analytics
- State:
- Created 7 years ago
- Comments:6 (2 by maintainers)
Top Results From Across the Web
How to remove only one user's reaction from an emoji
My Problem: The code above mostly works. Whenever someone reacts to the specified message, it will remove their reaction. However, it removes ......
Read more >Reactions - discord.js Guide
Removing reactions by a user is not as straightforward as removing by emoji or removing all reactions. The API does not provide a...
Read more >"Unable to delete the user" message when trying to ... - IBM
Therefore they try to delete the user again. This time an error appears. Symptom. The following message appears when trying to delete a...
Read more >21 Things to Know About WhatsApp Message Reactions
10. How to Change a Message Reaction. If you accidentally reacted with a wrong emoji, you can easily change the reaction without removing...
Read more >hikari.messages - hikari 2.0.0.dev113 documentation
A message to indicate that the grace period before removal from discovery has started. ... Anything else will result in a hikari.errors.
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 Free
Top 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
It’s because the master branch has lots of changes worthy of a minor patch. Also, the developers can’t agree on a release date for v11.1.0, which is necessary to get this patch out…
You can use
npm i hydrabolt/discord.jsas a temporary workaround for the time being. (You will need Git installed for this to work.)This bugfix has not been deployed to the stable branch yet, because for some reason we haven’t been releasing patch versions… cough
If you want the fix, you’ll have to
npm i hydrabolt/discord.js