08-12-2012 11:30 PM
08-13-2012 02:21 AM
Hi. Sounds mysterious. You are using Linux I assume from folder name? The file 'MANIFEST.MF' should be within your .bar file in the 'META-INF' folder, isn't it? If not something went wrong when signing. Or the .bar may not be accessable at all due to permissions when installing?
08-13-2012 10:22 AM
Using Mac OS X. And I haven't done anything different than I did with earlier releases of both the WebWorks SDK and the Dev Alpha OS.
Also, as suggested by a friend I tried building it with the PlayBook Tablet SDK instead. That resulted in the app building and installing correctly but running it on the device gives me nothing but a blank screen. I investigated that with the remote webkit console but I didn't see anything in there that could help me either.
So right now with the BB10 WebWorks SDK I get this error when installing on the Dev Alpha and with the PlayBook WebWorks SDK I get an app that doesn't run. Kind of stuck here
Staff UI Prototyper (read: full-time hacker)
08-13-2012 01:47 PM
Wow, really mysterious what is going on with signing. I was able to sign for PlayBook but not BB10 and now, after registering new keys I'm able to sign BB10 but not anymore for PB with them.
But, back to topic: did you add the "-d" for debugging within the Web Inspector and also activated the development mode on the device, hopefully you did and this isn't something can help?! So I assume another problem the RIM admins/devs here in the forum should have a closer look at if they aren't yet all on vacation. Being unable to sign for the one or the other seems to be the new favorite employment of us developers here and causing gray hairs, at least for me.
08-13-2012 02:56 PM
08-13-2012 03:36 PM
I troubleshot with Marco offline a little while. Here were the issues causing it to not package and deploy properly, hopefully this will help others as well in the future.
The problem was just a couple things.
- Missing the application ID property in the widget element
<widget xmlns="http://www.w3.org/ns/widgets" xmlns:rim="http://www.blackberry.com/ns/widgets" version="220.127.116.11" id="your_app_id_goes_here">
- Missing a script include. I always use Web Inspector's Network tab to make sure all my includes are loading. It's amazing how many times I've personally done this
- Missing 'webworksready' event listener. In Marco's case, this didn't break his app, but we must wait for this event before calling any WebWorks API's now.
BlackBerry 10 config.xml sample
BlackBerry 10 sample apps