I am embarrassed to say that I was missing a 0 in my provider config, and was using `4.6.0` instead of `4.60.0` Wow.. just wow. I knew this bug was too ridiculous to be true. Thanks for the response, @krishnaduttPanchagnula Closing