I'm encountering the exact same issue. Any progress on its resolution, or workarounds?