Answered: Issue deploying on Playbook device

Hi,

I have a Sencha Touch 2.0 PR4 application which displays a list with a header bar and if you click on a line item it shows some details for that item. This app is destined to run on a Playbook device.
Now, I can run this application on the Playbook simulator without any problems. But when I deploy it on the Playbook device (unsigned version, using a debug token uploaded on the device), I see the splash screen appearing (which is defined in the webworks config.xml file), but then instead of having the application load (as on the simulator), it simply exits out.

I have tried a really dumb down version of the app, which displays simply a header bar with a title and a html panel with some text below. This works and gets displayed correctly. I thought at first that this issue might be related to my list having to fetch it's dummy data from a ".json" file. So I tried a simple store object with inline data for my list. This simple list example works fine in Chrome and on the Playbook simulator, but again, not on the actual device.

Has anymore encountered such behavior on the Playbook device? If so, how to resolve it?
I tried using the Web Inspector tool, but since my app does not even load, there is no point. Has anyone ever found log files that we can analyze to see the cause of the error ?

I setup my viewport with a titlebar and a panel below. This panel has a "card" layout and the initial active child item is a html panel and a second child (not shown at startup) is my stripped down list. I also setup a button to switch from the html panel to the stripped down list. The app loads ok on the Playbook device, but as soon as I click on the button to switch the parent panel's active item to the list, it exits out.

I tried a simple list with Sencha Touch 1.1.1 and it works fine on the Playbook device. I used the list example from the Sencha touch 1.1.1 SDK (slightly modified to have it fullscreen instead of a fixed size).

I know a lot of changes were done in ST 2.0 in comparison to ST 1.1, but would you have an idea as to what in the ST 2.0 PR4 "list" implementation would cause the app to exit out on the device ?