Search Unity

Unity's version control component has been upgraded to Plastic SCM.

Cannot enable Collaboration toolbar

Discussion in 'Unity Collaborate' started by dgaspe, Jan 10, 2019.

  1. dgaspe

    dgaspe

    Joined:
    Dec 30, 2018
    Posts:
    2
    upload_2019-1-10_22-26-13.png
     
    hippocoder and erikkb like this.
  2. dgaspe

    dgaspe

    Joined:
    Dec 30, 2018
    Posts:
    2
    Unity collaboration stopped working. I tried logging out and logging back in. I also tried linking and unlinking project.
     
    erikkb likes this.
  3. hippocoder

    hippocoder

    Digital Ape

    Joined:
    Apr 11, 2010
    Posts:
    29,723
  4. romain1994

    romain1994

    Joined:
    Oct 23, 2018
    Posts:
    26
    same here!
    BUMP
     
  5. Animatony

    Animatony

    Joined:
    Feb 7, 2019
    Posts:
    1
  6. armizafel

    armizafel

    Joined:
    Jan 16, 2019
    Posts:
    1
  7. Ryan-Unity

    Ryan-Unity

    Joined:
    Mar 23, 2016
    Posts:
    1,993
    Hi @armizafel, can you please verify on the Developer Dashboard that you have been assigned to the Project and have been given a Teams seat?
     
  8. Manuel447

    Manuel447

    Joined:
    Dec 17, 2017
    Posts:
    6
    Hey @armizafel & @ryanc-unity
    I came across this problem a few days ago (2019.2.13f1) and found a way to "fix" it. Since this approach already worked on two different PCs (and users) it's probably worth posting here:

    1. Click on the little cloud icon (which opens the services window)
    2. Now you see different service features, klick on "Collaborate"
    3. Wait for a few seconds.

    Unity should then be "checking for changes" (as if you had just opened your collaboration project). After it's finished, everything should be working again.
    @ryanc-unity I haven't found any way to reproduce this problem so I cannot file a bug report. However, maybe this "fix" gives you a clue on where to start. Cheers.
     
  9. soft_sound

    soft_sound

    Joined:
    Aug 11, 2012
    Posts:
    39
    ^Thank you @Manuel447 That also is a fix for Unity 2019.4.16f