Project with multiple project assets, referencing the same utility in v22.1

General
, , ,
1

In v19.1, our project structure would generally consist of a startup project and a few child projects, each referencing a ‘utility project’ that contains functions we use accross the board (custom logging, message translation, etc.).

We’re now converting to v22.1 and it seems like this architecture poses a problem. Our initial thought was to convert the child projects to project assets, and then import those into our main project. But the fact that they all reference the same ‘utility project’ (now converted to a utility asset) seems to make Studio behave weirdly. More specifically, it looks like it breaks the debugger. Nothing happens when testing an automation or doing a ‘Run All’.

Are we missing a step to make this work or is this architecure just not supported anymore? If it’s the latter, how do you suggest we change our approach?

Thanks

2

INC-B36902 created for this

3

Thank you @Thierry_SLF for replying with your incident id. I have linked this Question with your incident for the engineers working on your case. Please share the resolution here once found to help other users who may have the same trouble as you.

4

Hi @Thierry_SLF

I received an update that your incident has been sent to our Engineering dept and I have updated your original post with the associated BUG-ID.

Thank you!

5

@MarissaRogers The fix for this will be released in R25 with plans to back port the fix to v22 at a later time due to the complexity of the fix.