I’m having trouble with a shared version control project. It’s a small project and we want to keep the number of people to three to avoid paying at this point. Even though one person has been given access to the project, they can’t open it in Unity Hub. More details:
User A created a free Unity account, a Unity organization, and a single project under that organization.
User B created a free Unity account, and when prompted created a new Unity organization.
User A added User B as a guest to the specific project in their organization.
User B opens Unity Hub and sees only their own projects. Add UVCS Repository shows absolutely nothing
User B opens their account in a web browser, can see both organizations including User A’s shared project
Even after logging out/in to the web and to Unity Hub, the User A organization and project doesn’t appear in the Hub. It seems stupidly obvious that there should be a drop-down box to switch organizations, but there isn’t. The Add UVCS Repositories continues to show absolutely nothing.
I’m just lost. This is all so ridiculously confusing. So there’s something called UVCS seats, Unity organizations, Unity Cloud… and I don’t even know where the Plastic SCM references fit in. Just tell me where to click. When you sign up they make a big deal about being able to have three people work on your project for free. There’s just nothing to make it remotely clear how do I add a fourth? A fifth? I need to suddenly pay $280/user/month? Or maybe it’s $7/user/month? I can’t even get three people to be able to find the project in Unity Hub. There’s no way I’d pay anything when even the “free” tier doesn’t seem to work. All I want to to is click “Add User” and get more people to be able to open the same project in Unity Hub. Or maybe that’s the failure. Is Unity Hub the wrong tool? I have ZERO IDEA of what to do and I’ve been a software developer for over 20 years. I apologize for the venting but this is just insane to me that it’s so confusing.
You have to go to Unity Cloud, seats, and add the emails there. Other seats after the third one are $7.
The unity hub is the right tool if other users want to import the project, you could also use the UVCS client but it also requires that the user is invited/has a seat to the UVCS organization.
We’re consolidating and simplifying, hopefully the seat system will be fully integrated with Unity organizations this quarter.
I’m having the exact same problem. My friend made a project, added me as an owner, but when I go into the hub and look for the project I get “No UVCS repositories found.” Any solutions?
If you have proper permissions, you should be able to see the repositories via Unity Dashboard web.
When you have the proper permissions and cannot see it in “open remote project/add UVCS repositories”, the users will need to follow the workaround below.
Anyone facing similar issue, Added a user but still can not see repository. Click on edit User in the seat section of UVCS to assign permissions. Please note every repository has its own individual permissions. From the drop down you can select the project and then assign permission accordingly for specific repo. Hope it helps.
We already have many projects. A new project was recently created by another team member. It does not matter how many times I click “Refresh UVCS projects” in Unity Hub, the project never shows up. I’m unable to access it. This whole user/project/organization mess is ridiculous.
My menu option in DevOps does not say “Seats.” It says “Users” I’ve checked all the permissions for the project in question and they are the same as every other project. Yet, Hub never shows it in the list. These issues are causing SERIOUS productivity problems for us. This whole thing needs to be dramatically simplified. I think it’s become so complex and convoluted that even the developers responsible for maintaining it can no longer make sense of it!
In Unity Hub, a different project that I had previously downloaded says “NOT CONNECTED.” So I click the dot menu button, “Connect To Unity Cloud”, click on “Connect” with the right organization selected and I get a notice at the bottom saying “Project Connected!” But the cloud column in the project list always says “NOT CONNECTED”.
These are just 2 of the many and frequent issues we have managing projects with VCS through Unity. It’s a nightmare. At this point, we’re about ready to just scrap Unity VCS and use Github straight up.
Thank you for responding. It’s v3.8.0. We’ve finally figured out how to link the repo that was initially created through DevOps in the WebGUI with the “Cloud Project” through the actual Unity Desktop client. Which is needed in order to get it to show up in Unity Hub for other users. That has solved the problem. There are LOT of problems with the management of “Local Projects”, “Cloud Projects”, “UVCS Repositories”, “Cloud Organizations”, and “Cloud Users”. It is needlessly complex.
There needs to be a better strategy for managing and handling the data AND GUI relationships between each of the various mentioned entities and the GUI’s that manage them.
Unity Hub conflates and confuses the difference between the two. A “Local Project” is NOT in any way, the same as a "Cloud Project.” This is confusing a LOT of people. Unity Hub handles these two, in a NOT equivalent NOR consistent manner:
The creation of a “Cloud Project” in web GUI of Unity Cloud seems to create a corresponding “UVCS Repository”. This allows it to show up in Unity Hub.
The creation of a “UVCS Repository” in Unity Cloud does NOT create a “Cloud Project” and therefore does absolutely nothing for Unity Hub. This is confusing because Unity Hub UI’s “Add” option lists “UVCS Repository”, not “Cloud Project.” However, that repository WILL show up in the “Unity DevOps Version Control” thick client for the desktop, which does allow you to open it up in the Unity Desktop Editor and do work. A great deal of work can then be done without anyone else being able to use Unity Hub for anything at all, let alone allow others to collaborate.
This leads to some people creating a UVCS Repository in the Web Cloud GUI and then expecting it to “Show up” in Unity Hub when browsing UVCS repositories. However, when a Repository is created, it does NOT automatically create, nor get “linked” to a “Cloud Project”, if it even exists. However, to my first point, when you create a project, it DOES create a repository. This causes a problem where, the ONLY way to “link” a newly created “UVCS Repository” to a “Cloud Project” is to do so through the actual Unity desktop editor by manually copying and pasting the Cloud Project GUID into the editor and then committing the change to the repository. Until that happens, no one else can see that project in Unity Hub. Once that happens AND the change is committed to the repository, at some point in the near future, it DOES show up in Unity Hub. This is a problem! Unless you intentionally WANT and have a good justifiable business reason to have a many to one relationship between repositories and projects, STOP THAT!
That said, there is a very real bug in Unity Hub which allows to establish that “link” between a local project and a cloud project and/or a UVCS Repository, but only for the user who created the project locally in Unity Hub WITHOUT the “Connect to Unity Cloud” checkbox checked OR the “Use Unity Version Control” checkbox checked AND has downloaded the project via the thick client for “Unity DevOps Version Control.” We actually had to expand the Unity Hub thick client to even discover there are all these other checkboxes available for handling that relationship between local and cloud projects and repositories. Those relationships are not well-managed. I supposedly successfully “linked” a local Unity “Project” to a cloud “Project.” And Unity Hub told me it had been successfully linked, but did not reflect that in the user interface, even after closing it and opening it again and no other users could see it from their Unity Hub.
This inconsistently in how the nomenclature and actual data entities (Organization, Project, Repository, User, Access) is wreaking havoc for Unity users and is desperate need of some serious cleanup.
I was able to glean a lot of this inferentially through experimentation in partnership with my team over many hours this past weekend.
All this is to say there a great many “gotcha’s” associated with allowing and enabling multiple collaborators of Unity projects. Specifically:
Local works fine.
Cloud native works fine provided the project AND repo are created through Cloud Projects Web GUI.
The integration of local and cloud projects and repositories is complex and not well automated.
Excellent work on this write-up! Your explanation is spot-on, and it perfectly captures the problem we’ve been experiencing. It’s really helpful to have such a clear understanding of the underlying issues. Unity definitely needs to make some major improvements to this process. Other IDEs like Visual Studio are much more user-friendly, and it shouldn’t be that difficult to replicate those features.
Well, it turns out figuring all of that out was pointless. We are back to square zero, not even square one. For my colleague, Unity HUB is now showing only a single repository. We have no idea where it came from. We didn’t create it, and it’s certainly not referencing our organization’s DevOps repositories because it isn’t in there. He’s never seen it before. We did a screenshare because I was so surprised. My repos are all coming up blank again. All we did was add a Unity Pro license for me (which I previously had, but has apparently since been lost.) I added it to Unity Hub, but Unity still doesn’t acknowledge it
Also Unity Cloud isn’t showing us having the pro level of cloud service, but on the services page, it says it’s included with a Unity Pro license.
I’ve come to the conclusion that Unity Hub is not production ready. I’m uninstalling it. It’s more hassle and headache than it’s worth. I just got a survey asking if I’d recommend Unity. I gave it a 3 and described how painful collaborating on any Unity project is and how buggy Unity HUb is. We are literally bleeding thousands of dollars a week fighting with all the various Unity tools to make them work together so we can work together. It’s asinine, and really dang expensive! I’d pay another $100/mo for our pro licenses if they could clean up all this garbage! We’re easily paying 5x that amount on troubleshooting these issues! Heck, at this point I’d just settle for a stable set of problems I know! I can’t even get that!
I can’t believe how bad this stuff is! If they want to hire me as CIO/CTO, I’ll come clean it up for them…and I’ll do it quickly in ways that disrupt service for users as little as possible, but at this point it’s such a mess, I don’t think they can clean it up without disrupting service to users.
Would the mystery UVCS project happen to be TNET2? We are fighting the exact same issues you listed above. Edit: I’m the colleague. Did not recognize the user name. Can verify this is a serious issue.
I have the exact same problem, I even logged in as the team member and confirmed the issue, when i relogged in myself I now also have the bug lol. Work around you can send a .zip of the project and it should load correctly, cutting hub out of the process.
We are still currently debugging and trying to fix the problem because there are some other customers also affected. The issue started to happen last Friday.
In the meantime, can you please confirm whether downloading and using the full Unity Version Control client allows you to do the initial download of the repository? If it does, you can then add the project to your Unity Hub from disk.
I hope this information is helpful to you. Sorry for the inconvenience and I hope this workaround helps in the meantime.
@harinechoi this looks like a different problem. The problem in this thread is related to the UVCS repositories not appearing in the Unity Hub. The problem seems to be solved upgrading to the beta 3.9 version of the Unity Hub. To do this, in the Unity Hub go to Preferences → Advanced and select the beta channel. After doing this, restart the editor and you should have the version 3.9 and all of you cloud repositories ready to be added.
But it seems you are having some issues opening a project. Could you open a support ticket?
As someone else said already.
You guys have to go with the Creator of the Orga into Unity Hub, select the Project, select DEV OPS, Go into Seats and add the E-Mail. Now its working!
