Authoring Tool Crash - Android SDK bug [FIXED]

[demosthenesk]

I have Authoring Tool 1.4 and it crashes on start.
Please see error image below

[demosthenesk]

The crash occurs also when i change the Android paths in settings

I made an upgrade on Android and i try to set up the new paths for SDK and NDK.

[Shaderman]

Are there special chars in the SDK paths you select in UAT?

[demosthenesk]

The path contains _ and - are these special characters?

But i tried also C:\sdk and C:\ndk i have the same results

The path for the NDK seems to be accepted. The path is "C: Android android-ndk-r9d"
The path for Android SDK seems to pop up the error.

[demosthenesk]

It seems there is something inside directory sdk that Authoring Tool does not like.
I tried to move sdk directory to C: so the path to be simple like "c: sdk"
but it crashes again and again.

I tried to google the error and in results says to reinstall Visual C++ Runtime libs.

I have instaleed both Visual Studio 2010 and 2013 Express with all VC++ Runtime libs but again it crashes.

Please help...

[Shaderman]

You wrote about problems before in the thread , so just some ideas/questions:

- Did you uninstall ShiVa and all of its components and then just made a clean install of ShiVa?
- Did you install ShiVa on top of an older installation?
- Are you sure you're starting the correct UAT version or do you still have a older version and maybe shortcut which you're using?
- Did you download and install a separate UAT version or are you using the one which comes with the ShiVa download?

[demosthenesk]

Hi,

@Shaderman
yes all are correctly installed, it was not this the problem

i found the problem.
It seems there is a conflict inside Android SDK directory for API 19, 4.4.2
I delete the files for API19 from SDK Manager Tool and now the Authoring Tool works perfectly.

Does this happen to anyone else?

[dpharaoh]

It happened to me as well, but it was the fact that I added the Wear SDK via Android Dev Manager. I had to remove it and then I was good to go.

[NiCoX]

Hi guys,

Just to tell you that indeed the "Android Wear Software Image" package is causing troubles. We fixed that in the upcoming integrated 2.0 UAT that will be available very soon in beta (including HTML5 engine, etc.). Until then, as Dave said, the workaround is to uninstall the Wear package.

[Andre_h2]

Hi NiCoX,

nice to hear from you.
I've been asking in a dedicated thread about a beta of shiva 2.0.

Is there any more info on what very soon means?

Thanks a lot,
Andre