Error Building Apk - Android SDK

[droxon]

Hello guys, I had to reformat my pc and now that I re-installed the Android SDK (with android studio) I'm getting this build error message:

Buildfile: C:\Users\Luiiz\AppData\Local\Temp\And305D.tmp\buil d.xml

BUILD FAILED
C:\Users\Luiiz\AppData\Local\Temp\And305D.tmp\buil d.xml:84: Cannot find C:\Users\Luiiz\AppData\Local\Android\sdk\tools\ant \build.xml imported from C:\Users\Luiiz\AppData\Local\Temp\And305D.tmp\buil d.xml

Total time: 0 seconds

Can somebody please guide me in the right direction please? I already checked and the SDK path is set correctly

[Fernando]

what android sdk are you using the one for Android Studio?

[Wodjanoi]

Droxon, you can take a look at the Java + SDK Manager Guide(without Android Studio though) on Fusion 2.5 Steam page. It's a setup guide for people who are new to Android Exporter or for quick instructions after pc reformat measures.
Otherwise check Perry's pinned instructions here, if you want Android Studio:
https://community.clickteam.com/threads/101342-Users-that-cannot-build-with-Android-Studio-(ant-build-xml-error).

[droxon]

@Fernando
Yes, I'm trying with the SDK for android studio because I was not able to find a standalone version anymore...

@Wodjanoi
Thanks for the tip, I didn't know that Android Studio was not compatible with fusion, it was working fine before.

I tried searching for the Steam guide but couldn't find it, can you post a link?

[Manuel]

Standalone-Version --> https://dl.google.com/android/instal...dows.exe?hl=id

[Wodjanoi]

Alright, so typing something like this 'steam guide java sdk manager' into Google search box didn't work? Here is the link again:
http://steamcommunity.com/sharedfile.../?id=914599868
You can use Manuel's link with the old 24.4.1 installer, otherwise you find the link for 25.2.3 tools on the Steam page I mentioned. The provided exe file is necessary to run SDK Manager and you can use it to create a SDK Manager direct file shortcut.

[droxon]

Thanks a lot for your help guys! it's working now turns out the problem was Android Studio.