"Signal already connected" error for inherited scenes Godot3.2

[SaffronStreams]

---

Note: This issue has been confirmed several times already. No need to confirm it further.

---

(Although there are some similarities with #6106 ; there are also differences, so Akien asked to make a new bug report; nevertheless, possible regression? in the other thread issues starting popping up again since May 2020)

Using Godot 3.2 stable (longer term project so haven't switched yet, was waiting for 3.2.3 stable to fix the polygon2D clipping problem); on Windows 10

I am getting a "Signal already connected" for each signal that I connect for a scene with inheritance.

The error pops up right after I change scenes, going from one level to the next via get_tree().change_scene(). These levels all extend my Level class, where I connect the signals. Maybe there's a desynch between disconnecting the signals of the old scene and connecting the new ones?

My scenes had editable children, but I made them uneditable again. The problem persists. (Here we seem to deviate from the earlier issue)

The error I get is:

E 0:01:08.592 connect: Signal 'freeze_player' is already connected to given method 'on_freeze_player' in that object.
<C++ Error> Method failed. Returning: ERR_INVALID_PARAMETER
<C++ Source> core/object.cpp:1464 @ connect()
LowerGuallidurth.gd:27 @ make_connections()
Level.gd:20 @ _ready()
LowerGuallidurth.gd:14 @ _ready()

Looking up that line in the source (not versed in C++) it looks to have something to do with it?

void Object::_clear_internal_resource_paths(const Variant &p_var) {
switch (p_var.get_type()) {

[francoisdlt]

I have the same issue using Godot 3.2.3 stable mono on macOS.

[verillious]

Same issue using v3.4.beta4 on macOS 10.14.6

[NotDaze]

Same issue. 3.3 on Windows.

[Calinou]

Related to #12373.

[graydwarf]

Not sure where this belongs but I finally found a solution for my case of "Signal 'AddCardsToWastePile' is already connected to given method 'AddCardsToWastePile' in that object."

The scenario in which I get the error:
waste-pile.gd

extends  CardPile
func _ready():
      InitSignals()

func InitSignals()
        Signals.connect("AddCardsToWastePile", self, "AddCardsToWastePile")

card-pile.gd

extends Area2D
class_name CardPile
func _ready():
  InitSignals():

func InitSignals():
 Signals.connect("AddCardsToPile", self, "AddCardsToPile")

The solution was to get rid of the InitSignals() function and place the signal connection directly in _ready. This can be done in one or both files.
card-pile.gd

extends Area2D
class_name CardPile

func _ready():
	Signals.connect("AddCardsToPile", self, "AddCardsToPile")

[cixil]

Not sure, but may have been fixed by #97303

[LUNART231]

I'm in 4.4 and the issue is still there.

[othd06]

I'm still in 4.3 but it's definitely still here and quite annoying.

[cixil]

The PR I mentioned was reverted, there's a new PR addressing the duplicate signal issue: #100965

I think it will solve this issue too, I will have to double check and tag it if so

[cixil]

I can't recreate the bug in 4.4, can someone provide MRP or tell me steps to reproduce?

[LUNART231]

I can't find a way to reproduce this bug from an empty project. It appears when my project starts to scale up.

The only way I've found to reproduce this bug is to directly duplicate the signal connection in the .tscn file using a text editor.

Three days ago, because of the error, I changed the code to no longer use signals in this case, so I can't say if the .tscn file has this same error.