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?
tkrosenblatt
Users receive reputation points by contributing quality content to the forums.
Posts include post and replies published on the forums.
Post authors can mark replies as Accepted to indicate successful solutions.
Apple Developer Forums admins can mark replies as Apple Recommended to indicate an approved solution