, thank you for creating the bug!
FYI, the workaround in that forum post does not work for me. The only workaround that works for me in 4.13.1 is to use a wildcard for the application id in the provisioning profile. I don’t know if wildcards are even allowed in publishing profiles (as opposed to the development profile I am using right now).