I have one project in 2020.2.0b7 where I use scoped registries. I added this via project settings and the manifest.json file reflects this. in this project, going to the package manager shows “My Registries” from the dropdown and allows me to browse my registries in the GUI
I my new project, in 2020.2.0b14, I have the same set up. I go to project settings, add my scoped registry to the manifest, and go to package manager. The drop down does NOT list “My Registries”. None of the selections show the packages, except where we manually added the package folders to our Packages folder.
I have recreated this in a fresh 2020.2.0b14 project. Create a new project, open Project Settings, add your registry, and open Package Manager to see that there is no “My Registry”.
However, as long as the scoped registries are in the manifest, you can add your packages to the dependencies list and it will grab them just fine. So this is less of an issue of “My stuff doesnt work!” and more of an issue of usability, and also the appearance of non-function.
Hi! Thanks a lot for reporting it. I did some testing and it seems to have been broken between 2020.2.0b10 and 2020.2.0b12. I will report a bug to the Package Manager development team.
Update: the development team found the source of the problem introduced after the release of 2020.2.0b10 and is working on a fix. You can still hardcode your scoped registry info and the packages your project needs in your project manifest. The bug is UI only.
I’m not sure if it’s related, but I have another issue with UPM, whenever I update a package, the install process is never released even if the package is installed and compiled. So the install and update buttons are greyed out (thinking the install process is not done). The only viable solution, for now, is to…restart the editor :cry
I was going crazy searching for solutions and now I see this is a bug.
Is there any way to manually add the dependencies? - I am struggling to install different google firebase packages into one build (Auth + Firestore + Storage).
It is so disappointing to see that this STILL isn’t fixed in 2020.2.2f1.
After 4 releases I’m left wondering if it was intentionally removed, or if the team that owns this feature really doesn’t care enough to mark it as a ship blocker. The fact that such a major feature can slip through QA at all is hard to believe. This should obviously be a SEV! We’re talking about an official release here, not some beta release nobody uses…
Can I ask if there is still no in-between asking on forums or paying 2k$/m for support?
If not IMO you should have an indie version of the support for a few hundred rather than 2k.
I literally lost days because of features that are not done and would love to have a way to reach out to Unity in those cases.