Archive for July, 2013

Getting started with Parse is a backend-service for mobile apps, or web apps. It allows you to create simple back ends for mobile apps, without requiring developing your own data-layer. I wanted to try it out, to see if I could get a simple “Hello World” app working, which stores a value in Parse, and then retrieves it via an ID later.

<script src=””></script&gt;
<script src=””></script&gt;
<script language=”javascript”>
Parse.initialize(“…..”, “…..”);
var TestObject = Parse.Object.extend(“TestObject”);
function init()
function save_click()
var testObject = new TestObject();{data: $(“#data”).val()}, {
success: function(object) {
alert(“stored as ” +;
function load_click()
var reference = $(“#reference”).val();
var query = new Parse.Query(TestObject);
query.get(reference, {
success: function(obj) {
error: function(object, error) {
// The object was not retrieved successfully.
// error is a Parse.Error with an error code and description.
<input type=”text” name=”data” id=”data” Value=”hello world”><br>
<input type=”button” value=”save” id=”save”><br>
<input type=”text” name=”reference” id=”reference” Value=””><br>
<input type=”button” value=”load” id=”load”><br>

Here, I initialise the Parse Library, then tie up events via JQuery, the Save and Load buttons to functions save_click and load_click. Save_click then stores a JSON object with property “data” and value as typed into the data text box, and sends this to Parse, all going well, an id is returned and displayed in the “reference” box. Load_click then requests this object again from Parse, using the ID previously provided, and displays the data property into the data text box.


Categories: Uncategorized

The package version in your .bar manifest file for New Bundle must be greater than the previous version

When updating an App for BlackBerry 10 on the ISV portal, a new error appeared when trying to submit my updated BAR file,

The package version in your .bar manifest file for New Bundle must be greater than the previous version, but lower than any the next release version added to the vendor portal. . Your .bar manifest file package version must be greater than 4.0. Correct your .bar manifest file and try again to continue.

After a bit of research, I realised that the version number is composed of two values:

The version number in the Widget tag of the Config.xml;

<widget xmlns=”; xmlns:rim=”; version=”″>

Combined with the buildId that is passed into the BBWP tool.

The combined version number must be unique, and as per this new requirement greater than the app version as published in the ISV portal.


Categories: Uncategorized
%d bloggers like this: