Thanks for your message - this is a known issue that is currently being addressed, to remove the incorrect error message.
