Why is this problem still exists in 2017.2.0p1 and not fixed.
It's first convinced and answered on 2017-01-16 in the following post on stackoverflow.
https://stackoverflow.com/questions/16843128/xcode-will-not-parse-project-from-unity
It's an automated typo error.
It's first convinced and answered on 2017-01-16 in the following post on stackoverflow.
https://stackoverflow.com/questions/16843128/xcode-will-not-parse-project-from-unity
It's an automated typo error.