@richpatrie reported in a separate, but related thread, that he was told the fix for this issue was expected on March 5th. Hopefully it's true! Very frustrating.
