12-15-2012 03:09 PM
I am trying to do something similar to the example here:
I have learned to expect problems with the QML preview, but this error is happening when trying to launch the app on my DevAlpha device! The exact errors are:
Critical: bb::cascades::QmlDocument: error when loading QML from: QUrl( "file:///apps/com.example.rim/native/assets//main.
qml" ) Critical: --- errors: (file:///apps/com.example.rim/native/assets//main. qml:3:1: module "bb.data" is not installed import bb.data 1.0 ^) Critical: bb::cascades::QmlDocument:createRootObject document is not loaded or has errors, can't create root
Note, I HAVE added the -lbbdata to the LIBS in my .pro file, so there should be no reason why the app cannont find bb.data! Has anyone else seen this problem or discovered a solution? This is essentially blocking any further progress on my app!
Solved! Go to Solution.
12-15-2012 11:54 PM
check this one if it is similar problem:
12-16-2012 06:51 AM
Thanks for the suggestion. I tried moving my ListView to another qml file and importing bb.data there, but I still get the same error, it thinks bb.data isn't installed!!
I even tried creating a new project and trying this, just in case there was some leftover weirdness from creating my first project with the Beta4 SDK. I'm using the Gold SDK now. When I installed the Gold SDK, I uninstalled the Beta4 SDK first, so that should have prevented any install problems from upgrading Momentics and the SDK.
So I'm still stuck and at a loss as to what could be causing this error.
12-16-2012 07:41 AM
When I first created project using Gold SDK, I had to include more libraries for some of my codes to work.
Pls check if you are looking for libbbdata library. It is the library for data access, e.g. JSON, SQL, etc.
12-17-2012 01:43 AM
try including this line in your main:
the release notes say that this has been deprecated in the gold release but it doesnt seem to be the case...i created a new project using the gold sdk, and had the same issue as you did if i used a DataSource class...the above line fixed it!
01-11-2013 08:57 PM
I just wanted to say thanks for your reply. This is the solution I ended up going with to get past this error. Looks like that really isn't deprecated yet...
01-24-2013 05:53 AM