I faced the same issue, and specifying the provisioning profile UUID instead of the profile name worked for me.