Custom nodes do not work in v2
I have a few custom nodes that refuse to work in v2 while functioning perfectly fine in v1. Moreover, these nodes don't work regardless of the node content as shown in the screenshot. The error message is the same across nodes
Cannot read properties of null (reading '_$keys_'). The code in these nodes is locally unit-tested and type-safe and once again work flawlessly in v1
2 Replies
AI Support Bot Information
<@850809315366797322> you can react on the relevant answer (message) with a ✅ in this thread when you think it has been solved, by the bot or by a human!
Anyone can react on this message with a ❌ if the GPT bot is unhelpful or hallucinating answers.
Please note: Team members will review and answer the questions on best efforts basis.
AI Response
The error message "Cannot read properties of null (reading '$keys')" you are encountering with nodes in v2 could be related to differences in how node execution is managed between v1 and v2. This might be due to changes in the API or the framework used in v2.
To troubleshoot this, you might consider:
1. Checking Node Inputs: Ensure that all input parameters are properly defined and not null. In v2, the node might be stricter about type safety and the presence of expected properties【4:19†buildship-docs.json】.
2. Updating Node Logic: Use the Node Editor to check the logic within your node. It might require adjustments for compatibility with v2【4:19†buildship-docs.json】.
3. Consulting BuildShip Documentation: Refer to the BuildShip Documentation for any updates or migration guides from v1 to v2.
4. Submitting a Support Ticket: If the issue persists, consider sending a support request via in-app support. You can also join the BuildShip community on Discord for more immediate troubleshooting【4:19†buildship-docs.json】.
For a more accurate resolution, detailed inspection of your node logic in context with v2 changes is recommended.
BuildShip AI Support