Hey frannyj09,
Actually the issue is with the date_i18n
function of wordpress. The recent update (WordPress 5.3) introduced this problem, when they converted the function in a wrapper for the wp_date
function.
In short : the plugin authors are not responsible for this bug, WordPress is (which is kinda worse actually).