Search Issue Tracker
Not Reproducible
Votes
0
Found in
2018.1.0b6
Issue ID
1000696
Regression
Yes
"Failed to resolve packages". The Editor force excludes modules when an internet connection is slow
To reproduce:
1. Limit upm-win.exe and Unity Editor.exe upload and download speed to KB/s with NetLimiter to simulate slow connection
2. Create a new project with a Lightweight - Preview template
3. Wait for approximately 4 minutes
4. When the pop up window appears notifying about failure to resolve packages, press Continue
5. When the project opens, select the Main Camera object in the scene
Expected: packman shouldn't fail to resolve packages and then proceed to not add any packages to the project if the internet connection is slow
Reproduced in 2017.3.1p1, 2018.1.0b6, 2018.1.0b7, 2018.2.0a1
Did not reproduce in 2017.2.1p4, 2017.3.1f1
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Duplicate External Textures start appearing when a Texture created with "CreateExternalTexture" is modified causing Memory Usage spikes on VisionOS
- Silent crash when using a "Blend Shape" in a "Skinned Mesh Renderer" to move vertices to Vector3.positiveInfinity, and "Occlusion Culling" is baked
- Some Prefab Source and Override content bounds are misaligned
- The Package Manager's "install packages by..." panels break when Domain Reload is triggered, and the panel is open
- Crash with multiple stack traces when leaving a docked VFX Graph open
Add comment