Titanium Community Questions & Answer Archive

We felt that 6+ years of knowledge should not die so this is the Titanium Community Questions & Answer Archive

KitchenSink does not launch in Ti SDK 1.3.0, Windows 7 x64

Hi,

My setup is Windows 7 64-bit, JDK 1.6.0_20 64-bit, Android SDK, Titanium 1.2.1 with 1.3.0 SDK, Kitchen Sink 1.3.0.

echo %PATH% returns (among other things): C:/Java/jdk1.6.0_20/bin;C:/java/jre6/bin;c:/python26;c:/Users/victor/projects/android-sdk-windows/tools

Android emulator launches, but KitchenSink does not. Trace reports that classes.dex was not found in KitchenSink/build/android/bin

Info-level trace is here:

http://pastie.org/963192.txt

Trace-level trace is here:

http://pastie.org/963200.txt

Thanks in advance for any help.

— asked May 16th 2010 by Victor Snesarev
  • android
  • kitchensink
  • win7
  • x64
0 Comments

3 Answers

  • I was finally able to get KitchenSink running. I am not sure whether both of these steps are necessary.

    1. Uninstall x64 (64-bit) JDK and JRE and replace with 32-bit version.
    2. This is probably what's important: set Android SDK target to "APIs 2.0" instead of "2.0". This was gleaned from
      https://developer.appcelerator.com/question/26171/runningbuilding-kitchensink-android

    After step 1 the error message changed to [ERROR] Failed installing com.nolanwright.kitchensink: pkg: /data/local/tmp/app.apk, which lead me to the link in step 2. It has been a struggle to get even KitchenSink–an app written to showcase Titanium–running. So much so, that the general first impression of Titanium is, in one word, "flaky". I don't mean to be negative, just stating my experience with Ti so far.

    — answered May 17th 2010 by Victor Snesarev
    permalink
    1 Comment
    • It's a shame that things like this make it look like it's a problem with Titanium, but in general it's to do with the setup of the underlying SDKs which Titanium then relies on to do the compile.

      I've had a wasted 5 hours messing with Java on the Mac trying to get it all to work, but if I'd tried to natively compile stuff for Android (without Titanium) then it wouldn't have worked either.

      It'd be nice if there was a pre-packaged version of Titanium where everything was sorted out for you, but licensing would get in the way of that, and it'd be pretty difficult to get it right.

      — commented June 3rd 2010 by Matt Collinge
  • Sorry about the issue getting it loaded. We use to have a message that warned you that you needed an API emulator for KitchenSink. The 32 bit issue is a Google one for Android, not quite sure what to do about that.

    — answered May 17th 2010 by Don Thorp
    permalink
    0 Comments
  • I got it to work using @Victor's advice, but I had to do a few additional things to finally get the Kitchen Sink working. Some of the steps might be unnecessary, but I wanted to make sure I was starting from a clean environment.

    1. Uninstall x64 (64-bit) JDK and JRE
    2. Uninstall Titanium Developer
    3. Uninstall Android SDK (delete the SDK directory)
    4. Delete the directory you extracted the Kitcken Sink to.
    5. Delete the following folders: c:\ProgramData\Titanium, %APPDATA%\Titanium, %LOCALAPPDATA%\AndroidEmulator, %LOCALAPPDATA%\temp-android-tool.
    6. Do a search for 'Titanium' and 'Android' in both %APPDATA% and %LOCALAPPDATA% and delete anything that shows up
    7. Install the 32-bit JDK, (which will also automatically install the JRE)
    8. Add the 32-bit JDK to my path (which in my case was c:\program files (x86)\java\jdk1.6.0_20\bin)
    9. Install Android SDK. Run SDK Setup.exe and in the "Choose Packages to Install" window, hit "Accpet All" then Install.
    10. Install Titanium Developer
    11. When prompted by Titanium Developer, install the Titanium 1.3.0 SDK
    12. Extract the Kitchen Sink
    13. Import the Kitchen Sink 1.3.0 into Titanium Devloper
    14. Run the Kitchen Sink with either Android SDK 2.0 or APIs 2.0 (both worked for me).
    — answered June 14th 2010 by Carmen Wick
    permalink
    0 Comments
The ownership of individual contributions to this community generated content is retained by the authors of their contributions.
All trademarks remain the property of the respective owner.