KitchenSink never comes up

You must Login before you can answer or comment on any questions.

I have TestDesktopApp and my own, do-nothing MobileApp running. However, KitchenSink, which strikes me as a crucial device to short-cut the Titanium learning curve, just never comes up. I've tried looking through the (emulator) device application lists, here, there, everywhere, but can't find it.

What am I doing wrong?

I'm not an iPhone guy (so, the Appcelerator tutorials aren't totally helpful). I'm on Linux (doesn't work on Windows 7 either). I'm doing Android (am an Android developer looking at Titanium).

![KitchenSink not working](http://www.javahotchocolate.com/tutorials/tut-images/titanium-kitchensink.png "KitchenSink")

— asked 2 years ago by Russell Bateman
2 Comments
  • Debug log's viewable at http://www.javahotchocolate.com/tutorials/tut-images/titanium-kitchensink-debug.png. There's some error with the apkbuilder, but nothing's spelled out.

    — commented 2 years ago by Russell Bateman

  • Is there a way to write the TRACE to a text file? It's very hard to pore through the tiny, green listing.

    — commented 2 years ago by Russell Bateman

3 Answers

Okay, like the first (Dmitry's) answer, which was helpful, I can't say exactly what I did, but here is everything I did:

1) Make sure you have EVERYTHING possible downloaded into Installed Packages in the Android SDK and AVD Manager. Everything that will come up. I had to keep getting stuff that would show up even after I had got everything the time before. I even brought down the Market Licensing package. I even brought down the Samples for SDK n.

2) Delete any and all AVDs created using the Android SDK and AVD Manager. If you can't delete one because it won't let you, make certain all consumers of AVDs are dropped (Titanium Developer and Eclipse), then Start the undeletable AVD and, as soon as you can, just click its Close box. That should let you delete it. Don't create any AVDs by hand.

3) Don't drop KitchenSink just anywhere. Shorten the path. I created a link in my appcelerator folder (where, for now, I've been putting all my trial projects) thus:

$ ln -s ../appcelerator-KitchenSink-5d6e950/KitchenSink

This might be more important to do on Windows than it is on Linux.

4) Force rebuild of KitchenSink by touching the xml:

$ cd KitchenSink

$ touch tiapp.xml

5) Launch Titanium Developer, remove your original KitchenSink: click on the project, then on the Edit tab, then down on the Delete Project button. Ignore what the alert says because it's gobble-dee-goop: just click the Close box (not either of the buttons whose titles don't correspond to the instructions in the alert). Be careful to do it this way in order not to lose your KitchenSink code.

6) Click Test & Package. Select SDK: APIs 2.2. Click Launch. Wait patiently. When you see "Welcome to Kitchen Sink for Titanium" in the INFO log window, click the Menu button in the emulator (this seems to be a peculiarity of Android 2.2: it happens when you're developing to this platform even from Eclipse).

You should be in business.

One last thing:

Ignore the [ERROR] .../apkbuilder (or apkbuilder.bat on Windows). It's a red herring, only a warning that the Appcelerator guys have not had time to react to something Android has been doing for a while and they're posting an error about it, but it doesn't matter.

I hope this helps. I see a lot of people out there as perplexed at one point as I have been today. However, I (and Dmitry) have done our best to say how to solve this. Best of luck to whomever reads this.

Russell, I had same experience on both Linux (Ubuntu 10.4) and Windows 7 machines at first but I finally got it to run. I can't claim I know exactly what fixed it but here are some things you may try:

  1. Change Filter to 'Trace' and attach full trace log. This will help troubleshoot the problem.
  2. Try to delete all AVDs in Android SDK and AVD Manager tool. Next time you choose a particular SDK in Titanium, it will re-create the AVD.
  3. I found that I had to set SDK to APIs 2.2 for KitchenSink to work but I believe it should be working with other versions too, I just did not try enough times yet.
  • Look at Troubleshooting section in Getting Started guide. I found it quite useful.
— answered 2 years ago by Dmitry Olev
answer permalink
2 Comments
  • (For the next guy:) On #2, I kept getting the message "Android Virtual Device [name] is currently running in an emulator and cannot be deleted". I had to launch the AVD "stand-alone", then drop it cleanly by clicking in the emulator close box in order to be able to delete the last AVD in the list. Then I was able to delete it.

    — commented 2 years ago by Russell Bateman

  • I've tried them all; none work.

    [ERROR] /home/russ/dev/android-sdk-linux_x86/tools/apkbuilder

    is a red herring: it means little or nothing as I discovered elsewhere in this forum. Nevertheless, this has been around a long time; it should be in the docs to ignore this.

    However,

    [ERROR] /home/russ/dev/android-sdk-linux_x86/tools/adb push: /home/russ/dev/appcelerator-KitchnSink-5d6e950/KitchenSink/Resources/main_windows/controls.js -> /sdcard/Ti.debug/com.nolanwright.kitchensink/Resources/main_windows/controls.js

    obviously indicates a serious error and one for which there should be support. If I can't find it elsewhere in the forum, I'll have to go with my growing impression that this is a tool for Mac OS and iPhone people.

    — commented 2 years ago by Russell Bateman

Russell, I'm researching a similar problem... but wanted to answer your final question: "Is there a way to write the TRACE to a text file?"

On Windows, you can click anywhere in the Trace window, then press CTRL-A (to select everything) then press CTRL-C (to copy it). Now paste it into your usual text editor or email.

Your Answer

Think you can help? Login to answer this question!