Unity Package Manager Error

Unity 2018.1.0b5 is not working with Unity Package Manager Error.Unity 2018.1.0b4 too.

This error is smiler to Unity 2017.3.0f3. fixed on Unity 2017.3.0p2 and Unity 2017.3.1f1.

Create new project. This dialog with few mints.

And then I got this dialog.

Push [Retry] Button.
I got this dialog.

next I Push [Continue] Button, Editor is start... but not working.

 

Hi Pascal,

I tested b6......
Unfortunately, the problem is still alive.
Same as b5.

Of course Unity 2017.3.1f1 works fine!!

Thanks.

 

@LeonhardP I have the same issue, still present in beta 6.
I did a post before:
https://forum.unity.com/threads/pac...packages-modules-missing-and-feedback.514352/

 

Did you submit a bug-report, as LeonhardP asked in his previous post?

 

OK, @LeonhardP I filed a bug report (Case# 1000696) with an attached project, lengthy description and screenshots.
Although I think to reproduce on the attached project you have to be offline and with no cached packages (in /Program Data/Unity/cache/..)
@Peter77 Do you have broadband speeds?

 

According to speedtest.net I have 50 Mbps download and 10 Mbps upload.

 

QA were able to reproduce the issue, it should be on its way to developers.

 

I sent a bug report now(Case 1002498) with b7.
The problem is still alive......

 

I've solved this issue by allowing Unity.exe access to the internet.

 

Can I get hot to do it?

I test b8 now... but the problem is not fixed.
I already got the information of the problem will be fixed from QA.

 

Even after allowing Unity.exe access to the internet the problem is not fixed because the connection is slow.
QA emailed me and said it is fixed in Beta 8 but it's not the case.

 

Hello @xCyborg,

It is regretful that you are having issues with this release of Unity.

A few questions: Is this the only restriction you are imposing to Unity/internet at this point? Are you under a firewall? Is your internet connection proxied?

Thanks kindly!

 

I tested b9......

The problem is not fixed yet.

What's wrong? Proxy?

 

@pedro_unity Check the case number, QA reproduced it.
I disabled Windows firewall alltogether, antivirus, it's still happening in Beta 9.
BTW I use a hotspot access point from my Android device.

 

It seems all good to me, everything else downloads normally.

 

b10 is same......

 

Can this be fixed before final release please?

 

b11 is same......

 

2017.3.1f1 is no problem with upm-win.exe. works fine.
2018.1.0b13 is not work...

I do not use windows defender.
I use "ESET ENDPOINT SECURITY" and I tested it OFF. BUT nothing different.

Of course 2017.3.1f1 works with ESET.

Thanks.

 

I am faced with the same problem, but with version 2017.3.1f1, I have a deadline at this stage and I get this error.
I tried all the solutions listed on this page and they did not help me https://answers.unity.com/questions/1462126/failed-to-start-unity-package-manager-unity-versio.html .

WTF Unity?
Why complicate the life of developers by inserting unstable versions of this F***ing package manager? I do not know now how I can cope with this problem.

Very disappointing yours product.
Now I'm forced to downgrade to version 2017.1.3p3, because in this version this problem is solved. But there are missing some solutions about the progressive liightmapper which are very important to me.

 

This problem is fixed in 2018.2 beta thread.
Here is the thread.
https://forum.unity.com/threads/failded-to-start-unity-pakage-manager.527494/
It is cause my mistake of proxy settings. but it is little bit strange.

hi iwan-iwan,I think so too.
The Package Manager is not good.
I got a problem(crash and hang) when update versions.

Unity support said newer version is fixed many problems about the package manager
so how about try 2017.4.1f1?
This version is update same day 2017.1.3p3.

Thanks,
Hirokazu

 

Hi iriguchi. thanks for link.
I tried to run the project on version 2017.4.1f1, but the problem was also available.
If am switch to beta version, then I think it will be a mistake for me, since I will probably run into the rewriting of the source code and again lose a lot of time.
In any case, I will stay on version 2017.1.3p3, I have no other way

Many thanks to the package manager.