IX Model issue after 2.6.0 upgrade

[nitingondule-xdt]

Prerequisites

• I have read the Contributing Guidelines.
• I have not leaked any internal/restricted information like screenshots, videos, code snippets, links etc.

What happened?

While opening the ix model, an exception is thrown. This was OK with 2.5.0.

Uncaught (in promise) TypeError: Failed to execute 'appendChild' on 'Node': parameter 1 is not of type 'Node'.

What type of frontend framework are you seeing the problem on?

React

Which version of iX do you use?

2.6.0

[github-actions]

Thank you for creating this issue! It has been labeled as needs reproduction.

To help us assist you better, could you please provide a way for us to access the code (such as a GitHub repository or a StackBlitz link). Without a reliable code reproduction, it might be challenging for us to resolve the issue, and we may have to close it.
Thank you for your understanding!

[danielleroux]

@nitingondule-xdt Cannot reproduce any issue with your code (btw its not runnable) please avoid pasting your production code this does not help the team to provide you fast feedback because we have to adapt the code.

[nitingondule-xdt]

@danielleroux
As I mentioned, this was functioning properly before to the 2.6.0 upgrade, but it has now stopped. Even after trying 2.5.0, the problem persisted.

Note: It's fine if we're just building something new and it causes issue, but our codebase hasn't changed, and it stops working all of a sudden.

[nitingondule-xdt]

@danielleroux @matthiashader
As i have mention, it is not operation with IX version 2.5.0. PFA attached zip to reproduce issue. Please click on about icon of applicaion
ix-model.zip

Let me know if anymore steps are required to reproduce this.

[nitingondule-xdt]

Based on my investigation, I found that the "showModel" property of Model was previously supported with import { showModal } from "@siemens/ix". However, it seems to have been removed from this and added to import { showModal } from "@siemens/ix-react".

Note: As I mentioned in my previous comment, it was working earlier, but it suddenly stopped functioning in build 2.5.0 and not for latest 2.6.0 . This suggests that changes were made in a previous build as well.

Please check on your end as well. If needed, we can schedule a call to discuss, as I have to spend more time on this without your support.