Even if interaction is not replied - Interaction has already been acknowledged
I check both
this.interaction.replied || !this.interaction.isRepliable()
before replying to an interaction, but I still get Interaction has already been acknowledged.
Is this a bug?
8 Replies
• What's your exact discord.js
npm list discord.js
and node node -v
version?
• Post the full error stack trace, not just the top part!
• Show your code!
• Explain what exactly your issue is.
• Not a discord.js issue? Check out #useful-servers.I know the issue happens when you reply twice, but I cannot possible see how that could be the case, unless it's some race condition. I don't get it every time (only sometimes, haven't figured out a pattern). And I figured that this should still make sure it doesn't happen regardless?
interaction.replied is not reliable
(at least for this)
and isRepliable only checks for interaction type btw
I see
I guess I'm going insane, I can't figure out for the life of me how this could occur. Some kind of weird async race condition I guess
.replied or .deferred are set after it's replied or deferred. If you do the code below, you'll most likely get an error, because the first reply isn't awaited
yea
I don't think I'm missing any awaits
¯\_(ツ)_/¯
Unknown User•3y ago
Message Not Public
Sign In & Join Server To View
Most likely two instances of your bot are running