Hello again zer0X, Like you, the module name causing the crash on our side had an underscore in it. Renaming the module by simply removing the underscore fixed the issue for us. Regards

Hi zer0X, We ran into a similar issue (with the same crash log). We found that the source of the problem, in our case, was the use of an UIViewControllerRepresentable implementation in a module. Moving the code to the main app source tree "solved" the issue for us. Of course, this is not acceptable in terms of code isolation, but this workaround will do for now... Would you happen to use this protocol in a child module too? Regards