I get a "Querying package manager for currently installed packages" pop window forever

Hi,
Suddenly I started getting this pop up window and it stuck there thinking.



I'm using Unity 2019 LTS and my packages seems to be up to date.
Is there a diagnostics I can run?
P.s. I'm using XR manager and XR toolkit.

Thanks

Aviv

 

I am getting the same, and it has completely frozen the editor on several occasions especially when returning from editing a script in VS.
Windows 10
Unity 19.4.0f1 (LTS)
XR Plugin Management 3.2.12 (Oculus)
Also see this in the console
"Package Metadata store error. Check if there are any other errors in the console and make sure they are corrected before trying again.
Failure reason: Timeout trying to get package list after 30s.
UnityEditor.EditorApplication:Internal_CallUpdateFunctions()"
I have restarted both the PC and the editor and the problem persists.

 

same. its annoying

 

Same. It times out after 30 seconds and most of the editor remains usable. Did the endpoint for the package list change and can now no longer be reached?

Package Metadata store error. Check if there are any other errors in the console and make sure they are corrected before trying again.
Failure reason: Timeout trying to get package list after 30s.

The stacktrace points to XRPackageMetadataStore.RebuildCache()

 

I rolled back the XR Plugin Management package to version 3.2.10, as 3.2.12 comes with this popup and 3.2.11 seems to be in preview status. Looking into the changelog https://docs.unity3d.com/Packages/com.unity.xr.management@3.2/changelog/CHANGELOG.html, I found this:

[3.2.11-preview.1] - 2020-05-15

• Fix FB 1242581 : Fix a number of issue around cache rebuilding and persistent UI display of cache rebuilding even though nothing was happening.
• Fix FB 1245181 : Fix nullderef access of settings manager instance.

 

Also having this problem. Really annoying.

It seems to go away randomly if I click through the package manager, but this only seems to work sometimes. Definitely a bug of some kind.

 

rolling back to 3.2.10 fixed it for me as well

 

Same here.

 

Also experiencing this, seems the stability claims of Unity LTS have fallen short. Experiencing severe issues with auto-complete and VS Code as well.

 

I am also having this issue. Any fix other than reverting?

 

@transparentz I think reverting is the easiest solution and you can see in the changelog that there is nothing critical you are missing out on. You can also wait for an update, as apparently there is already a fix in 3.2.11-preview1, as you can also see in the changelog. You can also try and merge the fixes from 3.2.11-preview1 manually into 3.2.12. But I really don't see the issue with reverting to 3.2.10 until the fixes are merged.
@CMHatch I have to disagree with your assessment. For once, VS Code is independent from Unity and the issues you are experiencing are unrelated and likely a configuration problem. Second, the package under discussion here is not part of a specific Unity release, but a package. Thirdly, there is already a fix which has just not been merged into the main branch of the package, as I wrote above. Fourthly, the revert to 3.2.10 is an easy and painless workaround.

 

Same issue here. It started happening more often too. I have no idea why?

Also I'm running Pi-Hole and can see every request made. Absolutely zero requests to Unity servers are blocked. This is a botched update.

 

How exactly are you downloading 3.2.10? I appreciate everyone saying its a painless workaround, but the package manager does not give you access to older versions...

 

Like this


Then select the version you want and click "update"
Alternatively, you can edit the "packages/manifest.json" file. And edit the version there so that the line reads
[...]
"com.unity.xr.management": "3.2.10",
[...]

 

3.2.10 not available if you update Unity 2019.4.2f1. I thought Unity fix this in 2019.4.2 but nope.
Best way is use Unity 2019.4.1f1 and use version 3.2.10

 

Same issue, it says verified for 2019.4 however i feel something was missed

Tried older version, which are not compatible with latest LTS.
Also tried remove and reinstall the plugin, no luck either.

This might need to be escalated to Unity.

 

2019.4.2 works fine for me with XR Plugin Management 3.2.10

 

Still comes up with 2019.4.2 and 3.2.12 (I don't even see the 3.2.10 any more in the package manager). I have a feeling this has to do with XR management itself rather than the editor version.

 

Was also getting this, reverted!

 

+1 on this. The rollback workaround did the trick earlier this week but after updating to latest LFS (2019.4.2f1) that is no longer possible. Super annoying :'(

 

I rolled back to 2019.3.15f1 and then XR plugin management 3.2.10 is working fine..

 

Same here, also experiencing this issue. Can't roll back to a previous XP Plugin Management version in 2019.4.2f1.

 

This seem to be fixed on 3.2.13.

 

Hi I cant seem to enable ARCore in XR Plugin-in Management, does anyone have this issue? I am using Arfoundation 4.0.2 and have installed ARCore 4.0.3 but when I click the checkbox for ARCore in plugin-in management it does nothing

 

I am not familiar with AR and not sure if this would help in your case, but I had a similar issue with Steam XR plugin. I had to enable something else (e.g. oculus) then disable it. After that try re-enabling the plugin in question. Restarting also worked in my case.

 

I have already tried that, still does not work. I thought it had something to do with the timeout error and would be fixed but still isn't. I am using XR Plug-in Manager 3.2.13.

 

I am also using 2019.4.2F1, do you have the same?

 

Yes I am using 2019.4.2f1. I did not have any issues with ArCore in previous versions without xr plugin manager

 

I also tried 2019.4.3 same problem

 

I just updated to 4.3 and no issues.

It might be something to do with the AR part of this? probably a good idea to do a bug report.

 

I solved the problem by deleting the XR Folder in Assets and reinstalling the XR packages

 

Hey folks, please do file a bug report on this if you're still getting issues. This is a problem with the package, as opposed to the Package Manager itself.

 

Upgrading to 3.2.13 fixed the issue.

 

Unity 2019.4.4f1 can upgrade to 3.2.13 as well. Fixes the issue!

 

weirdly just clicking thru (without changing anything) fixed it... btw... i don't see 3.2 avail for ARFoundation for 2019.4 just 3.1