Hmm, no, I’m talking nonsense, we explicitly saw a reference to an

objc

initialize call in the error trace