(Case 1191723) Package Manager refresh doesn't refresh local packages

Tested on 2019.3.0b2, 0b6, 0b7
Works on 2019.2.2f1

I'm working on local packages where new versions are pushed to our own registry.
In 2019.2.2f1, pressing "refresh" in Package Manager correctly shows updates to the manifest (for example version change, changes to samples, dependencies, ...).
In 2019.3.0b6, "refresh" doesn't do that anymore. Also, closing/reopening Package Manager doesn't help. Only restarting Unity actually reflects those package.json changes to the UI.

@okcompute_unity is this desired behaviour? Seems like a bug.

Edit: I reported a bug, (Case 1191723). This makes working with custom packages pretty much impossible.

 

Turns out it's even more broken on 2020.1.07a, where changing the version in the manifest afterwards throws one exception per frame in the Editor.



Clicking the "select manifest" button even selects the right manifest which shows the new version.

 

@okcompute_unity any news about this? This is a big workflow blocker for us as working with our own code in packages is really hard with this. 2019.3.0b11 went out and this bug is still in there.

 

@okcompute_unity @LeonhardP this is still broken in latest 2019.3.0f1.

I want to point out that this bug makes it pretty hard to establish a proper package workflow with 2019.3 for us. We're developing a lot with inhouse custom packages, and can't do that on 2019.3 right now.

 

Thank you! Can you double-check that the bugfix not only fixes package.json not updating but also manifest not updating? (I thought it's the same issue, just want to make sure that's fixed as well). E.g. adding a new scoped registry to the manifest updates Package Manager fine on 2019.2 but does not update Package Manager until Unity restart on 2019.3.

 

I can confirm that this is NOT fixed in 2019.3.0f4.
@okcompute_unity @LeonhardP

Issue Tracker notes that this is "fixed in 2020.1" without backport to 2019.3 in sight.
Is that correct? If this is the case 2019.3 will not work for us for package development at all.

EDIT: also not fixed on 2019.3.0f5. @okcompute_unity any info on when will this appear in 2019.3 branch?