by uckelman » December 31st, 2020, 9:46 pm
That's exactly the error message you should see in this situation, and it was sufficient for you to resolve the problem.
Thanks for persisting with me on this. The fix you have in that test build will be in whatever the next release is, either 3.4.13 or 3.5.0.