I think I traced down the issue:
I logged the output of the xml import and got back a warning:
"Error: unknown type <qa:ContextInformations>
at Registry.mapTypes (webpack-internal:///./node_modules/moddle/dist/index.esm.js:525:11)
at Registry.getEffectiveDescriptor (webpack-internal:///./node_modules/moddle/dist/index.esm.js:550:8)
at BpmnModdle.Moddle.getType (webpack-internal:///./node_modules/moddle/dist/index.esm.js:775:32)
at ElementHandler.getPropertyForNode (webpack-internal:///./node_modules/moddle-xml/dist/index.esm.js:424:25)
at ElementHandler.handleChild (webpack-internal:///./node_modules/moddle-xml/dist/index.esm.js:479:23)
at ElementHandler.BaseElementHandler.handleNode (webpack-internal:///./node_modules/moddle-xml/dist/index.esm.js:263:19)
at handleOpen (webpack-internal:///./node_modules/moddle-xml/dist/index.esm.js:812:26)
at eval (webpack-internal:///./node_modules/moddle-xml/dist/index.esm.js:871:7)
at parse (webpack-internal:///./node_modules/saxen/dist/index.esm.js:1047:13)
at Parser.parse (webpack-internal:///./node_modules/saxen/dist/index.esm.js:301:5)"
with the message:
"unparsable content <qa:contextInformations> detected
line: 6
column: 8
nested error: unknown type <qa:ContextInformations>"
When I save my extension “contextInformations” it is written with a lower case first letter but apparently when loading the xml it cant parse this because it is expecting it to be written with capital first letter. I completely searched my code and I never write it with a capital letter. When I do, everything works fine. Is this some kind of convention to be followed? Funny thing is, if I write it with capital first letter in my code and save it to xml, it is written with a lower first letter inside the xml.
<bpmn:extensionElements>
<qa:contextInformations taskType="ACDSF" />
</bpmn:extensionElements>