Important note: Once I switched from "Pre-release version" to released version, the problem disappeared. This means that the attached extension issue you see here is not the same as the extension ...