Voice channels are options when forwarding messages

(#415) Bug Fixed messaging

6mo agoby FullestReviewer edited by moderator originally by @Emptiest on GitHub

Summary

When forwarding messages, voice channels are options. Since they don't have integrated text channels like Discord, this functionally does nothing. They probably should not appear in the menu. Currently the behavior if you try to forward a message to a voice channel is it just takes you to that voice channel, but obviously no new message appears to be forwarded.

Steps to reproduce

Click Forward message
Select a Voice channel
Forward
????
No profit

Environment (optional)

canary build 88 (28da28c), 2026-03-11 14:24:31 UTC, Electron 39.2.7, Linux 6.17.7-ba25.fc43.x86_64 (x64), desktop canary 0.0.7

Logs or screenshots (optional)

image

563812273-2bc858cc-30b2-4ac0-a473-238b7c0b337e.png
437×250 | 15 kB

History

2 comments

RexSystem 1 vote 6mo ago originally by @cproudlock on GitHub

The issue is in fluxer_app/src/components/modals/shared/ForwardChannelSelection.tsx lines 31-35. FORWARDABLE_CHANNEL_TYPES dynamically includes all channel types except GUILD_CATEGORY:

const FORWARDABLE_CHANNEL_TYPES = new Set<number>(
    Object.values(ChannelTypes)
        .filter((value) => typeof value === 'number' && value !== ChannelTypes.GUILD_CATEGORY)
        .map((value) => Number(value)),
);

This includes GUILD_VOICE (type 2), which can't receive text messages. The fix is to use the existing TEXT_BASED_CHANNEL_TYPES constant from @fluxer/constants/src/ChannelConstants:

import {ChannelTypes, TEXT_BASED_CHANNEL_TYPES} from '@fluxer/constants/src/ChannelConstants';

const FORWARDABLE_CHANNEL_TYPES = TEXT_BASED_CHANNEL_TYPES;

Permalink

RexSystem 1 vote 6mo ago originally by @Jencansee on GitHub

I have also fixed this couple days ago, but didn't have much time to push it. I opened PR on my side with explanations, feel free to contact me and I'll open PR on main repo

Permalink