08-03-2012 04:53 AM
same for me.
but I can run the app without ripple services! (Playbook & BB10)
08-03-2012 05:50 AM
If anyone have problems with running without ripple services, check if you have checked box "Allow accessto file URL's" on extension settings page.
08-03-2012 06:35 AM
helioz wrote:in BBUI sample i've the same error when loading the index.htm page
Do you have added the latest webworks-1.0.x.y.js file to the header. Try the source of the latest index.htm of the bbUI.js Next repo and uncomment the lines 25 + 71 to add the eventhandler for "webworksready" event. Attention: this sample index.htm uses the bbUI-0.9.4.js/.css, so perhaps you need to change some lines back to your file or only add the lines 25 + 71 to enclose the existing bbUI.js source code of your existing index.htm! Give it a try.
08-03-2012 07:25 AM - edited 08-03-2012 07:57 AM
LBP wrote:
helioz wrote:in BBUI sample i've the same error when loading the index.htm page
Do you have added the latest webworks-1.0.x.y.js file to the header. Try the source of the latest index.htm of the bbUI.js Next repo and uncomment the lines 25 + 71 to add the eventhandler for "webworksready" event. Attention: this sample index.htm uses the bbUI-0.9.4.js/.css, so perhaps you need to change some lines back to your file or only add the lines 25 + 71 to enclose the existing bbUI.js source code of your existing index.htm! Give it a try.
Done, still no luck.
chrome version: 21.0.1180.60 m
ripple version: 0.9.6
webworks version: 1.0.1.6
bbui version: 0.9.4 - now, ealier 0.9.3, thanks for the tip ![]()
ERROR:
Uncaught Error: INVALID_STATE_ERR: DOM Exception 11 ripple.js:483
h ripple.js:483
i ripple.js:483
h ripple.js:483
c.exports.initialize ripple.js:483
f.pass ripple.js:452
f.pass ripple.js:452
f.pass ripple.js:452
f.pass ripple.js:452
f.pass ripple.js:452
f.pass ripple.js:452
d.initialize ripple.js:475
In Chrome v 20 every thing works fine.
08-03-2012 08:30 AM
Hi.
I'm running Chrome Canary 22.0.1224.0 here with Ripple 0.9.7 (released 19.07.2012) and it is working really well, except some bugs in bbUI.js needed to be fixed at this time, but it looks like it should at this time:
I attached an empty template with only that "home" screen for testing purposes and with the respect to BB for using bbUI.js sample sources within the attachment.
08-03-2012 09:13 AM
LBP wrote:Hi.
I'm running Chrome Canary 22.0.1224.0 here with Ripple 0.9.7 (released 19.07.2012) and it is working really well, except some bugs in bbUI.js needed to be fixed at this time, but it looks like it should at this time:
I wrote ealier that canary is the solution, see the solution ![]()
But the problem is current stable version chrome (v21) and ripple 0.9.6 - last one from RIM.
I think the problem is with the browser or current ripple working on it.
I wrote about BBUI just because this app you may know better and has the same error - for your answer "The INVALID_STATE_ERR is something to say all or nothing in an application if you do not know the source code, and we don't"
Sorry for the confusion.
Your app has the same issue.
08-03-2012 09:24 AM
helioz wrote:
I wrote ealier that canary is the solution, see the solution...
I wrote about BBUI just because this app you may know better and has the same error - for your answer "The INVALID_STATE_ERR is something to say all or nothing in an application if you do not know the source code, and we don't"
Sorry for the confusion.
Your app has the same issue.
What issue do you have with my sample. When loading the content within Ripple I get this console log:
Can not see any INVALID_STATE_ERR output in my console.
Do you have some piece of source code running, we do not know and can not give a response to at this time, that causes the INVALID_STATE_ERR to come up?
08-03-2012 09:51 AM
08-03-2012 10:15 AM
@helioz
How did y installed the ripple emulator?
I had exactly the same 'don't panic' that you shown here!
In Chrome V20 .... ok
In Chrome V21 .... Don't panic
I uinstalled Chrome
I installed Chrome Canary
Then I installed the Ripple Extension via Chrome Canary (Settings / Extensions)... then everything was fine!
08-03-2012 10:21 AM
Hello all, we're taking a look into this to see what the cause is. In the meantime it seems that there's some good information in this thread, but we'll follow-up with what we find ASAP.