Closed nikku closed 1 month ago
Root cause:
id
or name
is present on reports, which is not the case if no-bpmn-di
reports "missing DI"Moving to ready
due to impact.
The root cause is fixed in https://github.com/camunda/camunda-modeler/pull/4518
The error is actually caught in componentDidCatch
of App component, but it goes into an infinite loop. My idea would be to have the bottom panel container closed in its own error boundary so that if it crashes, it doesn't take the whole app with it. Not sure if we want to investigate it now tough.
Describe the bug
I try to open the following BPMN diagram and it breaks the application.
I only see a blank screen, and cannot to use the app. Due to the fact that "last opened diagrams" is remembered, I cannot easily recover from this, too.
Steps to reproduce
Expected behavior
Environment
Additional context
Questions: