Component already registered for another node!

Application ID: C74AF032-95DA-1CFA-FF06-482F08A67000

...
sdk.js:14 Component with uid: '41f88e4ed0287846975cb955d983ea78' already registered for another node!
sdk.js:14 Component with uid: '41f8edcdcbf8ab711711fbf8c5f811fb' already registered for another node!
sdk.js:14 Component with uid: 'bbc8bf61a2a80bd8f018c6782a6ff6f1' already registered for another node!
...
[Violation] 'click' handler took 190ms

Problem description

I’m trying to develop my first app with UI Builder with more reusable components on multiple pages. I got lot of warnings in browser console output. What could be wrong?

Steps to reproduce

Open the page where I use any reusable component.

Hello @Martin_Krajcir1

Thank you for reporting this issue, however, I can not check it in your app because the trial period for the app has expired and the UI-Builder is not available anymore, could you. please try to reproduce the problem in a new app?

Regards, Vlad

Hi,

I have encountered the same issue as @Martin_Krajcir1 .

To reproduce:

  • create a reusable component with some UI components included
  • duplicate the reusable component
  • create a page where both reusable components are loaded at the same time

Here is a sample output I have received:

1 Like

@vladimir-upirov can you please have a look at this issue again? Thank you.

Hi, @Nicolas_REMY

Thanks for the steps. We created and internal ticket, BKNDLSS-28374, to investigate the issue. We’ll let you know about the fix in this thread.

Regards,
Marina

The workaround I found was to duplicate the reusable component, then within the reusable component, duplicate every ui component, and then also duplicate the logic from the old ui components to the new ones, because it isn’t carried along. And then delete the old ui components.
It works, but on the whole, it’s not really an easy duplication :slight_smile:

If I may, what I suspect happens is that the reusable component is indeed duplicated, but in the process the uids of the ui components within are not replaced by new ones. This probably creates a duplicate when they are loaded on the same page.