> Rather than fix the error, it decided to switch to another library

I’ve had a similar experience, where instead of trying to fix the error, it added a try/catch around it with a log message, just so execution could continue