Search Unity

  1. Welcome to the Unity Forums! Please take the time to read our Code of Conduct to familiarize yourself with the forum rules and how to post constructively.
  2. We have updated the language to the Editor Terms based on feedback from our employees and community. Learn more.
    Dismiss Notice
  3. Join us on November 16th, 2023, between 1 pm and 9 pm CET for Ask the Experts Online on Discord and on Unity Discussions.
    Dismiss Notice
New Forum User Notice Update to the Unity Editor Software Terms Unite 2023 - Ask the Experts Online

Error in PBXProject.AddFrameworkToProject documentation

Discussion in 'Documentation' started by sam_ettinger_sm, Feb 10, 2017.

  1. sam_ettinger_sm

    sam_ettinger_sm

    Joined:
    Dec 1, 2016
    Posts:
    19
    Hi all,

    I am using the method PBXProject.AddFrameworkToProject, as described on this page: https://docs.unity3d.com/ScriptReference/iOS.Xcode.PBXProject.AddFrameworkToProject.html

    I have observed that the boolean 'weak' does the opposite of what's described in the documentation. When my post-process method includes the line
    Code (CSharp):
    1. proj.AddFrameworkToProject(projectTarget, "VideoToolbox.framework", false)
    ...it exports an Xcode project where videotoolbox.framework is required. If I change that line to
    Code (CSharp):
    1. proj.AddFrameworkToProject(projectTarget, "VideoToolbox.framework", true)
    ...it exports an Xcode project where videotoolbox.framework is optional. Is this a problem with the PBXProject class or with the documentation?

    I am running Unity 5.5.0f3 on a Windows 7 virtual machine, and Xcode 8.2.1 on a Mac running OSX 10.11.6.
     
    sam_ettinger_sm, Feb 10, 2017
    #1

  2. Graham-Dunnett

    Graham-Dunnett

    Unity Technologies

    Joined:
    Jun 2, 2009
    Posts:
    4,287
    Have asked the iOS team to take a look and give an answer. The docs team have a link to this, too.
     
    Graham-Dunnett, Feb 12, 2017
    #2

  3. povilas

    povilas

    Unity Technologies

    Joined:
    Jan 28, 2014
    Posts:
    427
    Hi, thanks for the report. It's indeed a bug in the documentation. weak (i.e. weakly linked) frameworks are optional, non-weak (i.e. strongly linked) frameworks are required.
     
    povilas, Feb 15, 2017
    #3

  4. sam_ettinger_sm

    sam_ettinger_sm

    Joined:
    Dec 1, 2016
    Posts:
    19
    Thanks for the replies. Any updates on this? The documentation online still lists the incorrect information.
     
    sam_ettinger_sm, Mar 23, 2017
    #4