Is there a definitive answer to this question? This seems like the easy solution, given that this will not be fixed for Swift 6 release, but I'm worried it might be a footgun if there is some edge case where awakeFromNib is called by the system from a background thread. It would be great to have clarity here or a direction for how to resolve this for legacy apps that use this a lot.