- What's your exact discord.js
npm list discord.jsand nodenode -vversion? - Not a discord.js issue? Check out #1081585952654360687.
- Consider reading #how-to-get-help to improve your question!
- Explain what exactly your issue is.
- Post the full error stack trace, not just the top part!
- Show your code!
- Issue solved? Press the button!
✅Marked as resolved by staff
#I am getting InteractionAlreadyReplied error My interaction is getting deferred from nowhere
11 messages · Page 1 of 1 (latest)
unfortunately your error just means exactly what it says
discord.js doesn't respond to interactions for you anywhere, so if you're receiving this error, that means that either you or a third party lib you're using is responding to the interaction before your intended response
it'll be much easier for you to debug your code to explicitly figure out what's executing and what shouldn't be
you may also want to ensure that there isn't a secondary process using the same token that's receiving/responding to the interaction (this can easily be done by resetting your token)
If you aren't getting any errors, try to place console.log checkpoints throughout your code to find out where execution stops.
- Once you do, log relevant values and if-conditions
- More sophisticated debugging methods are breakpoints and runtime inspections: learn more
also personally I wouldn't consider linking the first message in a conversation that lasted over an hour to be a "summary"
in future please actually give a quick summary and share specifically your latest code, even when migrating your issue to #986520997006032896
But I am getting the errors
And I have done this @austere canyon
you may also want to ensure that there isn't a secondary process using the same token that's receiving/responding to the interaction (this can easily be done by resetting your token)
I have done this and it didn't worked
@thick summit Try
interaction.followUp('Hello!') after you have already used interaction.reply('Hi')
(I'm new to this so sorry if I'm wrong)
it's true that if they wanted to create a new message through the interaction webhook after their initial reply, they should use followUp
unfortunately their issue (seen in the link dubbed a 'quick summary') is a little more complex than that
the interaction appears to be deferred and they're receiving the "Interaction already acknowledged" error upon interaction.reply() executing despite the fact that they did not believe any interaction.deferReply() should be executing
therefore as mentioned previously, they'd want to log throughout in order to determine whether anything that shouldn't be executing is doing so