Summary
The
GET /guilds/{guild_id}/channels REST endpoint returns HTTP 200 with an empty JSON array
[] when any channel in the guild has a Unicode emoji character in its name. The issue is persistent — removing the emoji from the channel name does not restore the endpoint. Other guild endpoints (
/roles,
/guilds/{id}) work correctly with the same bot token.
Steps to reproduce
- Create a guild with text channels that have plain ASCII/Latin names (no emoji)
- Call
GET /guilds/{guild_id}/channels with a bot token → returns all channels correctly - Add a Unicode emoji to any single channel name (e.g. rename "Introductions" to "🎙 Introductions")
- Call
GET /guilds/{guild_id}/channels again → returns [] - Remove the emoji from the channel name
- Call
GET /guilds/{guild_id}/channels again → still returns [] (damage is persistent)
Observed Behavior
The endpoint returns HTTP 200 with body [] (empty array). No error code, no 500 — the failure is caught internally and swallowed. This was tested across 10+ consecutive requests with 2-second delays, with consistent results.
Other endpoints with the same bot token on the same guild work correctly:
|
GET /guilds/{id}/roles | 200, returns all roles |
GET /guilds/{id} | 200, returns guild info |
GET /guilds/{id}/channels | 200, returns [] |
The bot can still post messages to channels by ID, receive gateway events (MESSAGE_CREATE, VOICE_STATE_UPDATE), and the Fluxer client UI displays channels normally.
Expected Behavior
The endpoint should return the full list of channels regardless of whether channel names contain emoji characters.
Reproduction confirmed on two separate guilds
- Guild A had emoji in channel names from the start → endpoint has always returned
[] - Guild B had plain channel names → endpoint returned 9 channels. Added one emoji to a channel name → endpoint immediately returned
[]. Removed the emoji → endpoint still returns []
Environment (optional)
- stable build 190 (44b6925)
- 2026-03-27 14:07:52 UTC
- Electron 39.2.7
- Windows 11 10.0.26200 (x64)
- desktop stable 0.0.8
Bot is using direct REST API calls via
httpx (Python). Authentication:
Authorization: Bot <token>. No Discord library involved — raw HTTP requests to
https://api.fluxer.app/v1.
Notes
This may be related to the
text-channel-flexible-names guild feature. Guilds with this enabled can use spaces, mixed case, and emoji in channel names. The emoji appears to cause a serialization failure in the channels endpoint response builder. Since the damage persists after removing the emoji, the corrupted state may be cached or indexed server-side.
1 comment
Comment by Rex