So according to the email I received today, there will be a new release of Titanium next week.
Unfortunately for me, I have to make a final decision about sticking with Titanium/Appcelerator or finding a new solution by this Friday. Due to the headaches we have run in to over the course of the upgrade to 1.2.1 I can't justify spending additional time/resources waiting.
Can someone give me an idea of what is being fixed?
Is the missing Android Simulator problem to be fixed?
What about java problems on Macs who have gone from 1.2 to 1.2.1? For me all the SDK's loaded fine in 1.2. After going to 1.2.1 everything disappeared. (This happened the same on 3 different machines.)
I really, truly believe that Titanium is the solution our org needs, however, these problems that have come up and the seemingly lack of interest in fixing them in a timely fashion has me questioning whether or not I want to build my mobile development strategy around this system. More importantly, it has those around me questioning it.
I know the front page of the site says 41,861 active developers currently. When I started here it was probably half that. Of all those new developers, are they able to get functioning systems? I'm assuming they are all having the same problems that I am having from looking at many of the posts here in the q&a forum.
Maybe a better question to ask is: how can I help?
I'm not a stellar c/obj-c/java programmer. That is why I love the notion of Appcelerator/Titanium. It allows me to use things I already know to build.
But, maybe there is something I can do to help in some way? What is it?
I ran into some trouble with 1.2.1 and I think i just got it fixed.
I am going to point out the steps i took to get apps running on the android simulator without crashing, including kithen sink.
1 - Get the latest 1.2.1 SDK from http://drop.io/bhootu4 ( Thanks Kevin ) and you will need to place that in Library/Application Support/Titanium/mobilesdk/osx/
2 - Get ALL the Android SDK including the APIs. Install them using the AVD manager, restart Titanium and make sure you see 1.6, API 1.6, 2.1, API 2.1 etc.
3 - If you create a project and cant see the Run on android emulator tab you need the fixed android.py file <a href="http://github.com/appcelerator/titanium_mobile/raw/55fea80fe28a5940b890c2291ec68b7a756a3c27/support/android/android.py">HERE</a> it goes in /Library/Application Support/Titanium/mobilesdk/osx/1.2.0/android
4 Restart Titanium, create a new project you should get tabs for iphone and android, run Android emulator, dont worry if it fails the first time, wait to yhe emulator is running and hit launch again. Hold tight ( it takes while, at least on my Mac ) and you should be Rolling.
5 - For Kitchen sink, Grab the latest from Github dounload, create a new Project, DONT IMPORT this one, the copy the Resources folder from the Kitchensink and overwrite the new project's resource with the kitchen sink.
one. Before you launch on emulator make sure you are using API X.X, 1.6 and 2.1 work fine for me. Since kitchen sink uses maps it will need to be run with that SDK. It seams to take forerver to launch , but again, wait to the emulator is up and running and hit launch.
I'm pretty sure next release won't need all the workarounds ( I HOPE )
This is the one issue I have with Titanium. Bug fixes take forever. I'm not trying to sound ungrateful, but ever since the whole upgrade for better support came around, the ball's been dropped. Thus I'm re evaluating Adobe Air.
@Bryce, I'm not sure how the ball has been dropped on bug fixes. Of the 146 in the queue we hoped to fix for 1.3.0 82 have been addressed 76 fixed. Many of the items have been directed specifically at the Android fastdev problem created in 1.2.0. We had the android.py workaround almost immediately and had the other fixes available and listed in Q&A on several Questions.
We've also been providing up-to-date 1.2.1 builds for Android to people that ask and have set up a temporary download location at http://drop.io/titanium_android_nightly Neither these updates, nor the source have been restricted to premium members they have been available to all Appcelerator users.
@Juan at this point, you should be able to grab one of the nightly builds and not have to do anything other than point your project at it. No more patching android.py etc. You will still have to provide the pre-requisites like android sdk, platform libraries, java, etc.
@Jason here list of Resolved 1.3.0 items. Not every fix has a ticket, but most of them do. I'm not sure what "everything disappears" refers to wrt to 1.2.1.
The 'everything disappears' was in reference to Titanium just losing the ability to find any of the Java SDK's for the menus. It's the issue with 'loading….' just never going away.
I will look through those 1.3 items with fresh eyes in the morning.
Thanks for the input. It's appreciated.
@Jason. That usually means, but not always, that the android sdk location on the profile page is incorrect or the platforms haven't been downloaded. Check your profile page first. Also if you can provide a Trace level log, we can usually diagnose it.
One of the problems is that we get no notifications that questions have been updated yet. So we have to go through all the questions and check for updates. If some question is taking to long, neither @marshall_law or I (@donthorp) mind getting a ping on twitter with a link to the item. It doesn't mean we can drop everything and get to it, but it does mean we know a response is needed. Hopefully Q&A will be updated soon to address that issue.
I admit the journey with Titanium is a rocky one for me too but once I get all the quirky stuff sorted out, it is still an easier solution that objective-c (i think).
Since this is open-source, I wonder if there are enough contributors to make it better and more robust. It would be great if the community can chip in!
I had some trouble on the latest one trying to
"build for device" on iphone it kept on asking for android sdk path (which I dont have installed). In this case, just set the path in the profile tab as "/" and it skips this check.
1.2 has been really good, fast and almost bug free. I've found that the installer has given me more greif than any thing else :)
Keep up the good work guys! And maybe have a cheaper upgrade plan for just analytics and I"m sold in the upgrade too!
After spending most of the day today trying to get this stuff to work I have made some headway.
I am seeing the proper Java SDK's showing up in the menus now.
For whatever reason the android updater on my box is having all types of problems and can't seem to update the SDK's, so I ended up dumping the directories and pulling them over from another machine. (the 'add-ons' and 'tools' directories)
I did not make any changes on the profile page, I did check it and it was pointing to the proper directory and it worked before the 1.2.1 upgrade. But after dumping the sdk files and bringing in these copies from the other machine it works. I didn't expect it to work like that, but it did.
I have KitchenSink running on both iPhone and Android emulators now. That is great.
I was also able to install KitchenSink on to my Nexus One. That's huge progress and I'm pretty excited.
However, I am unable to get the app that we have developed here to run on the android emulator. Upon startup it crashes every time.
I then created a super simple base app that contained nothing but 3 windows and it does the same thing. The 'unexpectedly closed' error.
"The application XX (process com.XX) has stopped unexpectedly. Please try again."
Upon searching through the Q&A forum I found this:
Which seems to point to it being a Snow Leopard problem. I am running Snow Leopard on all the machines I'm testing with, so I'm guessing this is it.
However, I'm able to get KitchenSink to run and install, just not apps create here. Not even that extremely basic app.
But…I did get both apps developed here installed on the N1 now. The simple app runs, but the larger apps crashes just as they both do in the simulator.
So I guess my question at this point is: is this a Snow Leopard issue or something else? The fact that others are having problems with Snow Leopard makes me think that is a part of it, however, the fact that KitchenSink works fine has me thinking that maybe it's not a Snow Leopard issue.
@Don, I was talking about the desktop sdk
When launching on the iPhone simulator I get this error:
[ERROR] Script Error = * -[NSCFString appendString:]: nil argument at app.js (line 82).
However, line 82 is simply this:
tips.js lives at the same level as app.js
Any reason this should happen?