I also have similar issue, and the warning disappears after successful build. I know it is not a solution, but I would ignore this warning because it seems to be an error in Xcode.