Looks like this may be the issue. I think there’s a report here:
Good news is there’s a fix in the pipeline.
(Ah, I missed Jagster already suggesting it. )
)