BetterFriendsList React error

[AKASGaming]

Has been doing this for a couple months, stopped using BD for a while, then came back and updated all plugins, still having the same issue :/

[tsukasa]

Greetings,

I have tested DevilBro's BetterFriendList plugin (v.1.5.4, all settings in the BetterFriendList settings panel toggled to active) but cannot replicate the issue you posted. Adding the additional columns (i.e. the additional categories, shared servers column, and the additional sortable columns for name/status) works fine.

I do have a theory, though: You also cannot open the plugin's settings panel.

My best guesses are:

• Another plugin somehow interfers.
  To test this, you could create a VFS backup, format the VFS to start with a clean slate, and then add BetterFriendsList and 0BDFDB for tests.
• BetterDiscord itself might be outdated.
  To validate this, you can use the spiffy "Delete Asar from VFS on Reload" extension option to remove the betterdiscord.asar from the VFS and force a fresh download on the next reload.
• 0BDFDB's data file is outdated for some reason.
  You can test this by removing 0BDFDB.plugin.js and 0BDFDB.data.json from the VFS, reloading the page, adding 0BDFDB.plugin.js again and letting the caches refresh:
  • require("fs").unlinkSync("AppData/BetterDiscord/plugins/0BDFDB.plugin.js");
  • require("fs").unlinkSync("AppData/BetterDiscord/plugins/0BDFDB.config.json");
  • require("fs").unlinkSync("AppData/BetterDiscord/plugins/0BDFDB.data.json");
  • require("fs").unlinkSync("AppData/BetterDiscord/plugins/0BDFDB.raw.css");
  • Reload.
  • Add 0BDFDB.plugin.js again.
  • Reload.

[AKASGaming]

Doesn't seem to want to fetch it automatically, but I'll try manually

[AKASGaming]

So I backed up the VFS and extracted it, removed the 0BDFDB files, then imported it back. When it asked to download it again, it worked temporarily, but as soon as I reloaded it, the errors came back. Here's the log, maybe it'll help:
discord.com-1686412703826.log

[tsukasa]

This indicates an issue with the background service worker not setting the declarative net request rules and the rest just being follow-up issues.

To verify this, open Chrome's extension page, click "Details" on BdBrowser, and click on the service worker background page. A new console window should open, where you can issue the following command:

await chrome.declarativeNetRequest.getSessionRules()

Ideally you should get two rules back (Note: the extension id is random for every machine/installation):

[
    {
        "action": {
            "type": "block"
        },
        "condition": {
            "initiatorDomains": [
                "discord.com",
                "canary.discord.com",
                "ptb.discord.com",
                "hpopdkgjjnpfbiocpcpigmoaghebmboe"
            ],
            "regexFilter": "(http|https)://discord.com/api/webhooks/.*"
        },
        "id": 1,
        "priority": 100
    },
    {
        "action": {
            "responseHeaders": [
                {
                    "header": "Content-Security-Policy",
                    "operation": "remove"
                }
            ],
            "type": "modifyHeaders"
        },
        "condition": {
            "requestDomains": [
                "discord.com",
                "canary.discord.com",
                "ptb.discord.com"
            ],
            "resourceTypes": [
                "main_frame"
            ]
        },
        "id": 2,
        "priority": 100
    }
]

The DNR rules ensure regular fetch operations from the main frame go through. A non-working service worker could explain why the 0BDFDB data might not get updated, as the shims for the http/https/request modules are being routed through the service worker to avoid any CORS issues.

The DNR rules should automatically refresh once you disable/enable the extension.

Unfortunately I have no explanation as to why the worker would just vanish for you.

[AKASGaming]

Does this look about right?

[tsukasa]

Yes, this is exactly as it should be. I am therefore a bit puzzled as to why the Content-Security-Policy headers still seem to affect your fetch request in the log.

[AKASGaming]

Haven't used BDBrowser since, but when I turned it back on today and updated all plugins, it was fixed.
Sorry for the extra trouble/concern!