Feel free to reopen this issue if necessary. For now, we don't have information enough to find out why the incorrect exception is thrown.