Does anyone know whether there is an actively tracked bug on connect for this whether there is a workaround (or an explicit description of the situation that causes this bug, so we can look for it/avoid it in our code base)?