I had the error with 5.2 as well but mine wasn’t to do with collisions (as such)
Thankfully the warnings told me:
After fixing this the error went!