I've been working with Sencha Touch 2.0 for awhile, and have had a framework set up and functioning during that time. Recently I attempted to upgrade to 2.1.1, to align it with the newest available release, and updated Sencha Cmd to v. 220.127.116.118.
Everything seemed to be working fine, until I attempted to build a testing build. After doing the build, I noticed it deployed into the following directory:
Previously, it had been deployed into:
<application directory>/build/<application name>/testing
It now seemed to add an additional subfolder between "build" and "testing". This seems to cause it to quit working, as the app now no longer seems to work. When I load the app using the new location, it simply loads the Sencha Touch loading screen, which never goes away.
Is the new version of ST 2.1.1 supposed to deploy into that additional nested folder? Or is there something mucked up with my setup?
So, I've done some more playing / testing with this, and I think I'm getting closer to the solution. After doing some digging, it appears that putting the build in the new, deeper subfolder is normal, and is to be expected with the new version of ST / Sencha Cmd.
However, I've noticed that the app.js file, located in the:
folder is empty! I'm guessing this isn't supposed to be that way... It's just completely blank, even though following through the debug output in Sencha Cmd when typing:
appears to be correct. Any ideas?
sencha app build testing