Error: Unable to determine textarea instance

[FearedFusionX]

So I recently installed this plugin for my Vencord client and when I tried to send a sticker, it gave me this error:

Here's what happened:
https://github.com/user-attachments/assets/26ace0f3-0c91-4dc7-b927-713a1b0190db

Is it possible for you to take a look at this?

[Pitu]

@FearedFusionX could you try disabling all your other plugins and css first to see if it's a problem with one of those?

[FearedFusionX]

Interesting, it started working but I don't know what is causing it. here's the logs that I am getting:

magane.vencord.js:2209 Error: Unable to determine textarea instance.
    at Ji (magane.vencord.js:2128:33)
    at Array.<anonymous> (magane.vencord.js:2844:488)
    at HTMLImageElement.p (magane.vencord.js:977:14)
Ji @ magane.vencord.js:2209
(anonymous) @ magane.vencord.js:2844
p @ magane.vencord.js:977

I want to know if I can keep my plugins without disabling them for this to work.

[FearedFusionX]

I've also confirmed it's not the CSS that is affecting it

[BobbyWibowo]

Are you still getting this? It's either an edge-case, or you were enrolled to an early preview of Discord's updates that haven't gone live for the rest of us yet. I'm unable to replicate this as of right now.

[FearedFusionX]

Still getting this, here is my list of plugins:

[BobbyWibowo]

are those all supposed to be third-party plugins not available from vencord's built-in repo? then unfortunately that's far outside the support scope

in short, one of them must be modifying the text area a bit more extensively than usual*, for our method to fail. but yeah, we wont be able to inspect those

* some plugins such as simple char counters, or other plugins that simply add more buttons to the text area, are supposed to play nice with magane already

[FearedFusionX]

yeah, they are third party plugins, I just am not sure what could be causing it

So you're saying the text area is where plugins add buttons to the chatbar?

[yourself-q]

After checking the code, I found that the plugin partymode is currently the one causing this error.
At least in my environment, that's the only issue.