11-17-2020 10:04 PM
Is there any remote chance this problem will be fixed in the future? It is lv 2020 now and the whole world still breaks if a child implementation is broken even if it is not called anywhere. I get the feeling classes are getting some attention now and started to hope 🙂
01-18-2021 08:56 AM
Does anyone have a workaround for this besides temporarily deleting the offending sibling class out of the project?