Confirming that this error still persists, even after applying the updates discussed in this comment: