Last night I was working on a canvas image and all the sudden I started having this pop up saying “Importing (iteration)” pop up after every change I do. I never seen or heard of this happening before and it constantly takes a couple seconds to save. It pop’s up if I make any changes to my scene, adjust anything in the inspector or or do pretty much anything including saving a project.
Does anyone know how to fix this issue?
The current version of unity I’m using is 2019.3.0a10
I updated to 2019.3.b1 and told it to import the project I am currently working on. It does appear to be doing things, but it has been importing now for 4 or 5 hours and is on iteration 220!! This has never been an issue before.
I too face this issue at right now. I can’t open my main project. Anyone suggest to me prevent from this issue, Anybody share the best practice of importing assets “importing iteration 2” loading issue.
This issue is still there on 2019.3 b6. I can’t open my main project as well. Deleting the Library folder temporarily fixed my issue; I was then able to open Unity, but opening a shadergraph caused a crash. I am now back to the “importing iteration 2,” as Unity reimports and re-imports my shadergraphs.
Opening an already upgraded project on 2019.3.0b8 and this is still an issue. It was ok at first, but after sitting for a few minutes it started flashing the “Importing (iteration 2)” dialogue every second or so. I had to record it on my phone’s slow motion camera to even read it.
Tried to force quit from Task Manager, then reopened and got the “Importing (iteration 2)” dialogue as soon as the project opened. Still flickering quickly.
Probably should post this in the 2019.3 beta forum instead of here, since anyone from Unity looking for threads on pre-release 2019.3 issues will not be looking in this forum for them.
Hi,I also encountered the same problem, and later found that there was a call to the “PlayerPrefs.DeleteAll ();” method. After blocking this function, “constant Importing (iteration)” did not occur,But I don’t know the specific reason.
HI,This problem was discovered suddenly, and it took a lot of time to find it, because there were no errors or warnings. No any problem in previous use …
I meant more the “PlayerPrefs.DeleteAll()” during asset importing causing the import iteration loop; I misunderstood your previous post, thinking you meant that it causing the loop was intended / by design.
Yes, it might indeed be causing the loop if the asset might be trying to use PlayerPrefs and if you are using DeleteAll , it could cause problems. Would be easy to test in your situation.