Search Unity

Unity Collaborate 1.8.0 Broke My Project

Discussion in 'Unity Collaborate' started by Joseph8706, Sep 2, 2021.

  1. Joseph8706

    Joseph8706

    Joined:
    Jan 3, 2021
    Posts:
    2
    I recently installed Unity Collaborate 1.8.0, and it has caused 9 errors saying that type or namespaces couldn't be found in the scripts that come with the collaborate download. These errors have made me unable to use Collaborate and made my project unable to run. How can I fix this? I've tried deleting my library folder and rebuilding it when reopening unity, but that didn't work. Even if I disable collaborate for the project the errors persist. I cannot figure out how to resolve them. Am I missing other necessary packages? Do I need to somehow modify the scripts? I've copied the errors below for reference.

    Library/PackageCache/com.unity.collab-proxy@1.8.0/Editor/Collaborate/Collab/Presenters/CollabHistoryPresenter.cs(21,9): error CS0246: The type or namespace name 'BuildAccess' could not be found (are you missing a using directive or an assembly reference?)

    Repeated 5x at different places in the script:
    Library/PackageCache/com.unity.collab-proxy@1.8.0/Editor/Collaborate/Collab/CollabToolbarWindow.cs(14,23): error CS0246: The type or namespace name 'WebView' could not be found (are you missing a using directive or an assembly reference?)

    Library/PackageCache/com.unity.collab-proxy@1.8.0/Editor/Collaborate/Collab/CollabToolbarWindow.cs(28,35): error CS0115: 'CollabToolbarWindow.webView': no suitable method found to override

    Library/PackageCache/com.unity.collab-proxy@1.8.0/Editor/Collaborate/Collab/CollabToolbarWindow.cs(109,30): error CS0115: 'CollabToolbarWindow.OnEnable()': no suitable method found to override

    Library/PackageCache/com.unity.collab-proxy@1.8.0/Editor/Collaborate/Collab/CollabToolbarWindow.cs(26,69): error CS0535: 'CollabToolbarWindow' does not implement interface member 'IHasCustomMenu.AddItemsToMenu(GenericMenu)'

    Any help would be much appreciated
     
  2. jonpul_unity

    jonpul_unity

    Unity Technologies

    Joined:
    Jun 20, 2019
    Posts:
    1
    I'm sorry you are experiencing this issue. Our team is looking at what might be going on here.
    Can you confirm the Unity Editor version you are using?
     
  3. Joseph8706

    Joseph8706

    Joined:
    Jan 3, 2021
    Posts:
    2
    I currently have 2020.3.13. Will updating to a newer version solve this problem?
     
  4. ByteDevES

    ByteDevES

    Joined:
    Mar 23, 2017
    Posts:
    1
    I have the same exact problem using the same version
     
  5. caine128

    caine128

    Joined:
    Feb 7, 2021
    Posts:
    1
    Hello there,
    I have the exact same problem. The version I am using is 2020.3.5f1 Personal
     
  6. mcfaddentjoe

    mcfaddentjoe

    Joined:
    Nov 8, 2019
    Posts:
    3
    Same problem and same errors - using 2020.3.3f1

    Any advice on how to fix would be much appreciated!
     
  7. ryanc-unity

    ryanc-unity

    Unity Technologies

    Joined:
    Mar 23, 2016
    Posts:
    1,758
    Hey all, I'm very sorry for the confusion and issues you all are experiencing!

    The Version Control (formerly Collaborate) package has a bit of a confusing versioning convention after v1.5.0. Due to restrictions we had from the Package Manager team on how we could version our package, we needed to support both 2019 and 2020+ versions of the Editor in the same major version (1.x).

    However, the Collaborate window is different between 2019 and 2020+. 2019 uses the original Collab Toolbar WebView while 2020+ uses the Collaborate Window built using UIElements. This means that 2019 and 2020+ versions of the Editor require different versions of the package to compile.

    For 2019 versions of the Editor, please use v1.6.0, v1.8.0, and subsequent Version Control versions with an even-numbered minor version.

    For 2020+ versions of the Editor, please use v1.7.1, v1.9.0, and subsequent Version Control versions with an odd-numbered minor version.

    We will continue this naming convention until 2019 long term support ends. When that happens, we will announce when all later versions of the Version Control package will support all supported versions of the Editor. Again, we're very sorry for the confusion!
     
  8. mcfaddentjoe

    mcfaddentjoe

    Joined:
    Nov 8, 2019
    Posts:
    3
    Hi Ryan - thank you for explaining the situation with the Version Control package.
     
    ryanc-unity likes this.
unityunity