Apparently I am getting same error message, downgrading to 13.0.2 will solve the issue (it appears from 13.1.0). Did you submit the bug @daviddionis ?