Nope! And still no response to my FA. It actually happened to me for the first time yesterday after I upgraded to iOS 18 and I was looking forward to debugging but playing the same resource today works without the error. @talkingsmall confirmed that he was also unable to resolve the same error. @JoeKun -- any ideas?