discord / discord-api-docs

Official Discord API Documentation
https://discord.com/developers/docs/intro
Other
5.95k stars 1.26k forks source link

Slash Commands that take an attachment as an argument don't get sent and instantly show an error. #5267

Closed XavierToresLopez closed 2 years ago

XavierToresLopez commented 2 years ago

Description

Currently only on PC, I and my users have been experiencing an issue when using slash commands which take an attachment as an argument. As soon as I press send, the message says "This interaction failed" and clyde sends a messaging saying: "Your message could not be delivered. This is usually because you don't share a server with the recipient or the recipient is only accepting direct messages from friends. You can see the full list of reasons here: https://support.discord.com/hc/en-us/articles/360060145013" This is the same message you get when trying to message a user who has blocked you.

When opening network tools in my browser and running the same command, the "interaction" tab turns red and I get a Status Code 500.

Steps to Reproduce

  1. Write a command that takes an attachment as an argument.
  2. Log into discord on a computer.
  3. Use the command and pass any file into the argument that takes an attachment.

Expected Behavior

The bot should complete the command successfully.

Current Behavior

The interaction fails and clyde sends this error message: "Your message could not be delivered. This is usually because you don't share a server with the recipient or the recipient is only accepting direct messages from friends. You can see the full list of reasons here: https://support.discord.com/hc/en-us/articles/360060145013"

Screenshots/Videos

image

Client and System Information

I'm using both Firefox and Brave browser, along with the latest version of Discord on desktop. The error is the exact same on all platforms.

Legorooj commented 2 years ago

I can confirm I get this too with another bot.

siriscmv commented 2 years ago

One of my users reported this [ Stable 139674 (8d84d45) - Win10 64 bit ] but works fine for me [ Stable 139460 (ea9eb84) - Win10 64 bit ] using the same bot.

RisingFog commented 2 years ago

Can confirm this happens on Desktop with Stable 139630 (a5dcd43) Host 1.0.9005 Windows 10 64-Bit (10.0.22622).

However, the issue is not present on iOS App 137.0 (33973) stable and the command works normally.

TIBI4 commented 2 years ago

I can confirm this bug! Stable 139674 (8d84d45) Host 1.0.9005 Windows 10 64-Bit (10.0.19044)

I just switched from message command system to slash command system TODAY. For my bot, this interaction is essential. What a bad luck.

Maybe I was to blame. I am sorry.

sivelswhy commented 2 years ago

Can confirm this bug, i have it too !

wrdg commented 2 years ago

As the author of my bot, I'm the only one who's able to send interactions with attachments, other users are not able to complete this interaction and fails with the same message as original issue.

typpo commented 2 years ago

We're looking into this now

Luna-devv commented 2 years ago

can confirm this as well 👍 image

sivelswhy commented 2 years ago

Client and System Information

I'm using both Firefox and Brave browser, along with the latest version of Discord on desktop. The error is the exact same on all platforms.

Updata, on mobile (ios for what we have tested), it works

etherohm commented 2 years ago

still down bad, was losing my mind - at least I know I am not alone | djs13.9, node 16

Newtonzz commented 2 years ago

still down bad, was losing my mind - at least I know I am not alone

I second this

Also can confirm same is happening for me; Screenshot of my bot having the same error

artificialai223 commented 2 years ago

I can confirm I am getting the same issue.

TimothyLandry commented 2 years ago

I am also getting the same issue. As the owner, I cannot send any attachment, the other commands are working fine tho. Migrated the bot from djs 13.9 to 14 and I still have the issue. (Went from using the api v9 to api v10) Stable 139674 (8d84d45) Host 1.0.9005 Windows 10 64-Bit (10.0.19043) image

richardscull commented 2 years ago

Also can confirm this issue! Strange that I moved to api v10 some time ago, and didn't get any errors at that moment.

image

advaith1 commented 2 years ago

this is a discord issue, the bot is irrelevant

typpo commented 2 years ago

This should be resolved as of earlier today

Revnoplex commented 2 years ago

its not fixed, its still occurring for me Screenshot from 2022-08-04 18-41-09

SuperchupuDev commented 2 years ago

yeah still happening to me too with Canary 139877 (bb2442a)

ratelimit-thief commented 2 years ago

yeah still happening to me too with Canary 139877 (bb2442a)

just ian again

Newtonzz commented 2 years ago

Issue is still not resolved!

artificialai223 commented 2 years ago

Still happening to me!

artificialai223 commented 2 years ago

@typpo This issue is still active.

Legorooj commented 2 years ago

appears to be working for my bot now.

typpo commented 2 years ago

Thanks for the followups. I think a separate but related issue cropped up and that has also been fixed - should be on stable shortly

artificialai223 commented 2 years ago

Thanks for the followups. I think a separate but related issue cropped up and that has also been fixed - should be on stable shortly

My bot does not get the interaction, It sticks on "Sending command" @typpo

artificialai223 commented 2 years ago

Hmm, alright. I will give it another shot in the morning.

XavierToresLopez commented 2 years ago

False alarm. It was working, but the problem is now back. Exact same error.

ratelimit-thief commented 2 years ago

ian i think the trolling has gotten too far

Yagihata commented 2 years ago

Same issue in JP region. image

XavierToresLopez commented 2 years ago

ian i think the trolling has gotten too far

Who's Ian?

ratelimit-thief commented 2 years ago

Who's Ian?

basically a clone of me, but older

SuperchupuDev commented 2 years ago

works for me in Canary 140141 (042a785), thanks for the fix!

Revnoplex commented 2 years ago

Can confirm issue no longer occurs for me on the latest stable