I am actually beginning to wonder if 4.3.3(PC version) can be fixed. The 2 bugs I reported 3 months ago still exist in 4.3.3. They didn’t exist in 4.2.x. I wonder if Unity would refund my $1250 and if they ever fixed the bugs I would give the money back. lol.
And what are the bugs exactly?
I have resubmitted them(585463 and 585459). I will just summarize. Win7(PC) version. The one that really seems strange is Unity crashing on exit. It just locks up and the only way I can close is removing adb.exe. I have a work around by manually starting adb.exe(j:\android-sdk-windows\platform-tools\adb.exe devices). I am absolutely positive this worked in 4.2.x). The other is when I publish to my Droid 2. The Droid locks up when I leave the app. App works OK.
The adb.exe bug is resolved in Unity 4.3.3. I had that issue constantly, but since the update it disappeared.
Don’t know about the other one.
Well the adb.exe problem now works on one computer. Not mine.
In 4.3.2 I had only occassional lock ups due to adb.exe. In 4.3.3 that problem escalated to freezing when attempting to close the editor every time. Subsequently I have removed the Android SDK location from the preferences through regedit.
As the bug is supposed to be resolved according to the release notes, it would make sense to resubmit it. It obviously doesn’t work for everyone.
Maybe that’s because you both have different versions of something or your PC setup is different.!
I took a quick look at the two bug reports. It’s for QA to determine, but I’d suggest that there is not enough detail for the QA team to replicate your problems. Also, remember that the QA team are humans doing a hard job. Telling them it’s unbelievable that the bugs still exist kinda implies that they are not doing their job correctly.
Maybe it’d be a good idea for the QA team to send a message to the person submitting the error and letting them know if a certain status such as " there is not enough detail for the QA team to replicate your problem".
That way people know their errors arent being ignored or overlooked.
I know its a pain in the ass for the QA team, but it might cut back on complaints such as “are they ever going to fix it” and “again, my error never got fixed with this update”.
I for one definitely believe the QA team are doing a superb job. Why?
When contemplating the complexities involved in what it took to get Unity to the state it is now you can only surmise that the QA team are a battle tested unit of people that, in my humble opinion, are most likely the best in the context of this industry.
Sounds like a good idea at first glance, but when considering the practicality of it…
First, the same bug may get submitted by lots of people. Who gets the email? If it’s all of them then that’ll result in a flood of additional incoming data that all has to be sorted, etc, on top of having to have someone group together the matching bugs. Or if not everyone gets it, how do they select who does in a useful way?
I think that the now-transparent system that they have is probably mostly as good as it can get. There’s a balance between keeping people informed and actually getting the job done, and I wouldn’t want the former to get in the way of the latter.
I guess some automation could go a long way here, depending on what the current process is. If a bug is closed as a duplicate then does the system already have enough info to send an automatic email back with a link to the existing item in the bug tracker? And so on.
The adb.exe bug is NOT fixed for me. Unity editor still hangs till I kill the adb process via the task explorer.
Send a bug report so QA can track this.
Graham,
I start adb.exe manually using
j:\android-sdk-windows\platform-tools\adb.exe devices
and all is good.
I will wait another 3 months and maybe it will be fixed by then.
I thought the editor lock when exit was solved but it is still happening for me :sad:
The Unity hang on adb.exe at exit still happens for me with 4.3.3f1 installed. Also, it hangs on adb.exe when loading a new project as well. I was really hoping this was fixed in 4.3.3, is it has been around for some time and is really tedious.
If it’s happening to some and not others it may have something to do with the version of adb that is installed. If we can agree that we all have the android sdk installed we can then look art the android versions download and see who has what. you can find out which versions you have installed by starting the sdk manager in your android sdk folder and having a look at what you have downloaded sdk wise.
Specifically, what version(s) of the platform tools do you guys have installed?
I found this as well as a plethora of other links which show that a lot of developers, not just with unity, have problems when a certain version of adb is not installed.
Some complain of lock-ups, applications/games not starting an the solution which works for them seems to always be to update their version of adb.
http://stackoverflow.com/questions/15305725/i-cant-upgrade-from-adb-version-1-0-29
Before closing unity save the project and save the scene. When the editor freezes just manually stop the process. I haven’t lost any progress yet by doing it this way. It’s annoying, but no need to stop adb.exe.