Thanks. I tried to rebuilt the affected xaml on 1.11.1 version, but am getting the same error upon publishing. I am starting to think that there’s nothing I can do about this issue. Could it be that this is a bug inside the Office 365 package 1.14.1 version?