I'm rather new to sencha and probably struggle with lot's of issues most of you will only frown at.
But still....
Currently I develop my sencha-touch-2-project with Netbeans on Ubuntu 11.04 and on my local browser my project runs fine. However, when I do "sencha app build -e production" the build is working, but can't be changed later.
Doesn't make any sence, so I'll try to explain better. ;-)
I take the production-build and put it in a directory on a production-web-server. When invoking this ULR with chrome or my android-gadgets, everything works fine. Then I change some detail with Netbeans, which works on my local system. I perform a new build, and copy the result to the same directory on the same production-web-server, so it ands at the same URL. When I invoke this URL I get told "hey, there is a new app, do you want to upgrade?" which I do. And then I always see the flashing dots of doom, because loading of the app fails. Unless I reset my browser-cache, which solves the issue.
I have no idea what I'm doing wrong. Any help would be greatly appreciated. Basically this is currently only proof-of-concept and I aim to do native apps later (perhaps phonegap), but it should work anyway. :-(
Any help would be greatly appreciated.
I'm running sdk-2.0.1 and sencha-tools 2.0.0beta3 on linux, 32 bit.
I just tried upgrading to 2.0.1.1, but got other issues, which I will explain shortly.
as mitchellsimoens said, if looking on chrome open up the web developer tools and look in the console section this, should display some nice red errors, copy these to paste on here so we can see whats beeing called/error'd or thi smight help you solve it yourself.
F12 on a windows, alt/cmd and J on mac not sure on lynx to bring up the dev console.
OK, so there is no fundamental misunderstanding of the correct process on my site?
To clarify: I delete build/production, I delete archive/*, then I do a build, deploy it to my webserver and everything is fine.
Then I change the title of an Ext.List-object (or do some other minor modification), do a build again without touching build/production or archive, deploy again. After I accept the popup to install an update the application is broken