Yes, we are aware of this and working on a solution.
This should no longer be the case with Core Update 137.