Getting errors " TypeError: Cannot set properties of null (setting 'credentials'): undefined "

[hardillb]

From Freshdesk support ticket 296

Hi, I have an issue with the nr-tool plugin you just release last week. I got these error messages : " TypeError: Cannot set properties of null (setting 'credentials'): undefined " " Request Failed: TypeError: Cannot set properties of null (setting 'credentials') " I tried with different node-red instances, 3 differents raspi, one on windows 10 and one docker, with the same error. Thanks a lot for your help, I'm developping a multiple node-red instance with over 30 raspberry pi for a customer and the troubleshooting part direct on devices before mass deploying is game changer. thanks

[fdplourde]

1. ​Version of Node-RED you are using (3.0.2)
2. How you installed the plugin (via the pallette manager)
3. Details of what you were doing when you got the error

• when doing the rollback of the snapshot taken in the node-red red instance, in the snapshots page of the project, in flowforge cloud

4. Where are you seeing the error (in the browser console or in the Node-RED logs) - the error popup in the snapshot page directly in the upper corner right.
   

[hardillb]

Can you let us know the name of your project please (you can reply to my support email if you don't want to post it here)

Also just to be clear on the when part. Can you give a little more detail about the mix of snapshots you are working with here, are they all created with the tool or have you created any from the cloud instance?

[fdplourde]

So the project is "BTB-RFID-Dev" in the team "BTB Development"

The Snapshot "29nov2022 id: 0EG3QdNZXW" is from the cloud instance without the plugin.

The snapshots "29nov2022 test id: JB0ZkK5Zqw" and "test docker id: dkKZp4bZQ5" its from the plugin

[fdplourde]

duplicate that project make it work

[knolleary]

Hi @fdplourde,

Sorry for the slow response. We will investigate the original issue and identify why it failed for you.

It sounds like you have managed to workaround the issue by duplicating the project? If so, are you now unblocked and able to use the plugin successfully?

[fdplourde]

Hi @knolleary exactly.

If that can help you, in danger zone ( settings -> Danger> Change project Stack ) on the old project I can update the Stack but not in the duplicated project

[hardillb]

What version of the stack (which is what the cloud instance of the project runs in) should not have a bearing on this.

What may is how things are copied when the duplicate was created.

When you created the original project, did you do any development in the cloud based editor before pushing a new snapshot from the local instance of Node-RED?

[fdplourde]

The Stack is "Small Node-RED 3.0.2" ( for the original project ) As you can see I have the Update button availlable

For the Duplicated is "Small Node-RED 3.0.2" so the same, but the update button is not here , and we have more informations ( Node-red Version, Launcher Version, Node.js Version )

When I created the original project, It was existing before the 1.1 release, so yes I did development in the cloud based editor before pushing a new snapshot from the local instance of node-red