|
I just upgraded from Unity 3.5.7 to 4.1.2. I built to Android with no problems on Unity 3, but right now I cannot build using Unity 4 and I can't seem to find out why. Here is the error which is produced in Unity:
(comments are locked)
|
|
I found the answer/current workaround in another Unity Answers thread. The problem seems to be caused by using Android SDK Tools revision 22, and can be fixed by reverting to revision 21. To do this:
Thanks for the thorough explanations - however this did not fix the problem on my machine. On this Mac I never had any older software running, and so I expect that the reason that some people can make this work is that for them it's enough to replace the r22 with r21. But on machines starting up with Unity 4.1.2f1 and the current (r22) Android SDK with the accomplishing ADT bundle something more fundamental must be wrong. Replacing r22 with r21 is not fixing the issues. Or it's only possible on PC, I do not know. State of the matter is that I purchased software that does not work. It's quite hard to grasp and stay calm about - it's USD 1,900 software after all. And it's not working. I have been in contact with support, who asked me to file a screen dump of my About screen, but that is all from them so far. Now 3 days ago and counting..
May 22, 2013 at 08:59 AM
Fritsl
A lot of people seem to have this problem so hopefully they will fix it soon. I agree that it is ridiculous to pay a large amount of money and it doesn't work. Have you actually tried replacing the Android tools, or did you not know where to find them?
May 22, 2013 at 03:49 PM
Daveoh
I have made some hacks, and have some stuff working on downgraded versions, thanks. My biggest challenge now is that Unity Support tells me that the problem is on my side, that I am not following instructions. I hope you all write them and let them know that I am not alone, the problem is on their side - or we will never have the option to work with r22 and what that brings.
May 23, 2013 at 11:40 AM
Fritsl
Those steps worked for me, thanks!
May 23, 2013 at 10:26 PM
davekalina
Genius! Thanks! #fixed
May 24, 2013 at 12:23 AM
kingdutka
(comments are locked)
|
|
For me, simply copying the tools folder from the r21 zip over my android-sdk\tools\ folder did the trick. (Be sure to close ADB etc). Upon restarting the SDK manager, it listed the version as 21 (with 22 available) for "Android SDK Tools", and I was able to successfuly download "Android SDK Platform-tools" Thanks for the nudge in the right direction Daveoh\mrueger. thanks.. @sicklebrick your answer helps me a lot..
Jul 25, 2014 at 07:14 AM
kenjoegolo
(comments are locked)
|
|
What worked for me (on mac):
there is probably some unnecessary stuff in the above list, but it got me back into a working state
(comments are locked)
|
|
I created a zip with r21 based on mrueger post. Simply extract it to any folder, then set unity to work with it (edit, preferences, external tool, Android SDK Location). You can download from here. Did you lock that download or something? It says I can't access it with my google account.
Feb 19, 2014 at 09:13 PM
kr4ft3r
(comments are locked)
|
|
Is their a proper fix for this issue yet? I have not yet tried to downgrade because I would hope a year later there would be a change. Am about to down grade though and will post results now
(comments are locked)
|

Im getting the same thing, tried updating JDK and getting latest SDK.