November 18, 2019 at 3:54 pm #1849
After upgrading to the Unity 2019.3.0f11 I’ve come to know that the PBXProject.GetUnityTargetName() is deprecated. This results in Build error. I’ve tried with the given alternatives like PBXProject.GetUnityMainTargetGuid() & PBXProject.GetUnityFrameworkTargetGuid(). It didn’t work. Xcode 11.2.1 keeps throwing this error.
November 19, 2019 at 2:32 pm #1852
- This topic was modified 4 years ago by Senthamizh.
I tried changing the line 27 to string projectTarget = proj.TargetGuidByName(“Unity-iPhone”); directly. And this is what I’ve got.November 19, 2019 at 5:04 pm #1855
It seems your project isn’t linked against
Open xcode project, select your target, go to “Build Phases”, “Link Binary With Libraries”, click on a plus icon in bototm left and add “Speech” framework.November 20, 2019 at 7:56 am #1864
I’ve added the
Speechframework in Xcode as you said and I still get the same error.
I’m guessing the problem is with the
I’ve tried using the
string targetName =
and found by logging that
string projectTarget = proj.TargetGuidByName
returns Null value for both. But Build success with exception error. (In Unity only).
Removing the entire asset files and tried. Unity and Xcode builds without any issue.
Using the plugin is causing the issue. You probably need to update the asset maybe?
my current setup.
Xcode Version 11.2.1 (11B500)November 20, 2019 at 9:57 am #1865
I am not sure why Unity broke this API, but as a workaround you can simply go to
Speechframework manually as I described above.November 20, 2019 at 2:30 pm #1866
Yeah I’ve tried what you said exactly and again it get build errors.
I’m attaching the them. Please check. Thanks.November 20, 2019 at 6:08 pm #1868
Regarding screenshot from Unity about
PBXProject.TargetGuidByNameerror – this is coming from
UnityAdsEditor, not Speech Recognizer – it seems Unity broke their own plugin with this API change, you probably should file a bug for them 🙂
Regarding xcode – not sure where you added, but there’s no way your project would have only one framework linked against. It should look like that:December 9, 2019 at 1:54 pm #1917
This issue is fixed in latest version.December 10, 2019 at 4:39 am #1920
Great! Thanks, I will try it now. 🙂
- You must be logged in to reply to this topic.