I'm stuck for hours now on this problem, I have my application created with the last version of Sencha, who works fine on IOS and Android, using Phonegap 2.2.0 to pack everything.
Now I want to put my app on Blackberry using Webworks and Phonegap.

When I launch my application it stuck on the SplashScreen, I search a solution and it seems that maybe Sencha Touch 2 is loaded before Phonegap and could bring some problem, so I tried to modify my index.html to launch ST2 after Phonegap :

I wrote 3 alert, one before the Javascript part for Sencha, one after and one in the function sencha method.
The first one is called but the others are not, so I guess there is a problem with the Sencha Part but I can't figure what it could be, is there a way to simply make a test inside of the receivedEvent function to check if Sencha is working? Or is Sencha not loaded yet when I call all this code and the last line Ext.blink({"id":"ba7734f5-ef3e-4477-bcea-70fb8b8a9663"}) is killing everything ?

Well, when I'm using ripple with the plateform : Apache Cordova / Phonegap 2.0.0 everything works fine.
If I'm using the plateform Webworks 2.0.0 I have the same result as on emulator, stuck on the sencha loading.
But I have no Javascript error at all, and if I comment most of my code, still the same result.

The only thing is on Webworks the deviceReady event won't fire, so I had to put all the Sencha Code inside of the receivedEvent method (see above) directly in the <script>.
The code inside of my app.js or the first view seems to be called.

Ocelyn,
I have personally avoided using Ripple as I found that the results (at least in so far as wrapping Sencha with cordova are concerned) are sometimes inconsistent with the actual device. Which device are you targeting?

You are correct regarding the deviceReady event. It does not execute - not really sure why, but I've seen the same behavior on devices. However, your code should still execute (i.e. I would revert back to the original). I encountered the same issue initially, and as I said, it was due to a javascript 'error'. I say 'error' as there was no error in the code, but for some reason the bb didn't like the javascript and threw an error. BUT.... I never saw that error when I ran the built 'production' or 'package' code.
To debug, I suggest that rather than building the app, (via Sencha cmd) and then trying to wrap, use your pre-built code(original source) and try to wrap it. This was how I discovered what it didn't like about my code - for some reason this showed the javascript error.

I tried many solutions with different result.
Trying to export with production mode : Stop at the SplashScreen

Trying to export with testing mode : Stop at the SplashScreen too, I opened the js files to check if there is some error, but nothing, also I commented all the console.log() just in case.
If I try to export with uncompressed files, my application is too large and won't be installed on Blackberry (around 15 meg)

It's really annoying, I started to have no clue on the way I could fix that problem.
Could you show me your index.html just in case ?

A few thoughts that might help you:
1) What version of ST are you using? I noticed a bug in ST2.1 where lists don't appear properly (at least on the Playbook). If you are using ST2.1 and your main view is a list, this could be the issue. Again, haven't tested this on an OS7 device.
2) While I'm not able to share my exact code with you the structure should be (this is pre-compiling for production):

However, the above will not compile webworks into the app. I.e. you won't see it in the built production directory and it won't have been compiled. So you have to make sure that you include it in the final exported directory. I doubt this is your problem, but figured I'd mention it.

3) I would try adding an alert statement in your app.js before the viewport adds the mainview.

As a last resort I can offer to take a look at your code this weekend - I don't have much time, but I may be able to offer suggestions - or at least try it on a playbook and see if perhaps its the device/os causing the issue rather than you code.

1) I'm using ST2.1, I have some list in my application but not in the main view, if the list can bring trouble, I could try to find another way to do some of my views.
2) I'm wondering what is js/webworks.js? One of your own class ? I haven't been able to find it in all of the files I downloaded.
3) I'm going to try to add the alert statement.

Thank you so much for your offer, I'll try to do my best to fix the problem as fast as possible, in order to not take your time
I should try my app in playbook emulator too if you think it could bring me some clue.