discord / discord-api-docs

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

HTTP API v10 does not provide message content even when bot has message content intent #4552

Closed onerandomusername closed 2 years ago

onerandomusername commented 2 years ago

Description

Fetching a message with Get Channel Message with message content intent enabled will not provide any additional information that the message content intent is supposed to provide.

Steps to Reproduce

Expected Behavior

Message has content, since the bot has the intent enabled in the dev portal.

Current Behavior

Message has no content provided.

Screenshots/Videos

image

Client and System Information

any

onerandomusername commented 2 years ago

Update: this is also applicable to Get Channel Messages

onerandomusername commented 2 years ago

I figured out a solution to those possibly affected. Toggle any intent, and save it. Then toggle it back and save again. This triggers some sort of internal syncing on discord's end and will provide message content when using the HTTP API.

Leaving this open for now as its still a bug nonetheless. Additionally verified bots are not able to toggle any intents above if they are impacted.

onerandomusername commented 2 years ago

At this point, this problem has inverted itself, and I always receive message content on one of my bots over the HTTP API even if I have the intent off in the dev portal. I am using HTTP API v10.

yonilerner commented 2 years ago

@onerandomusername thanks for the report! can you provide us with an application and bot user ID?

braindigitalis commented 2 years ago

Can confirm this is still happening, had a report from a D++ user of the same issue via REST requests: image Bot ID: 797612182610378835

yonilerner commented 2 years ago

@braindigitalis If you toggle message content intent on and off in the dashboard, does that change anything?

yonilerner commented 2 years ago

We had a bug that caused the developer dashboard to incorrectly update necessary data to serve message content over HTTP and sometimes gateway. The bug is fixed now. If your message content is not working as expected you may have to toggle the flag in the dashboard, unfortunately.