Skip to content

start() could not be fired#185

Description

@Kiznel

Plugin:

馃憖 ChannelsPreview

What version of BetterDiscord are you using?

1.13.14

What version of the selected plugin(s) are you using (if applicable)?

2.1.16

What client are you using?

馃數 Stable

Describe the bug

When loading up Discord on first launch, or manaully trying to enable the plugin, it shows the error start() could not be fired.

This seems to be fixed after a restart (CTRL+R), but loading Discord on a cold boot gives this error.

Previously, this error would show on every boot of Discord, but after an update yesterday, it now only seems to show after a cold boot.

Error: 2nd parameter should be function name at Xr.after (betterdiscord/betterdiscord.js:159:5978) at ChannelsPreview.patchChannelItem (betterdiscord://plugins/ChannelsPreview.plugin.js:505:13) at ChannelsPreview.start (betterdiscord://plugins/ChannelsPreview.plugin.js:382:10) at Na.startAddon (betterdiscord/betterdiscord.js:89:1799) at Na.enableAddon (betterdiscord/betterdiscord.js:85:1565) at Na.toggleAddon (betterdiscord/betterdiscord.js:85:2021) at betterdiscord/betterdiscord.js:113:63640 at betterdiscord/betterdiscord.js:113:50825 at betterdiscord/betterdiscord.js:69:5131 at lz (betterdiscord://BD/webpack-modules/patched/995/995197.js:7:159602) at eval (betterdiscord://BD/webpack-modules/patched/995/995197.js:7:165680) at tT (betterdiscord://BD/webpack-modules/patched/995/995197.js:7:46636) at l0 (betterdiscord://BD/webpack-modules/patched/995/995197.js:7:160835) at u4 (betterdiscord://BD/webpack-modules/patched/995/995197.js:7:186588) at u3 (betterdiscord://BD/webpack-modules/patched/995/995197.js:7:186410) at HTMLDivElement.n (https://discord.com/assets/sentry.d7c33bc8256dc2fb.js:12:4106)

Additional comments

This also did the same for other plugins under this repository too, such as "BetterGuildTooltip", but those don't seem to have the same issue anymore, since the recent update.

I have read and agree to the following:

  • I have searched existing/closed issues to confirm that this hasn't been solved already.
  • I've already tried to disable all other plugins (or themes) to confirm this issue is related to the plugin.
    This isn't necessarily required

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't working

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions