search

blackberry / bbUI.js

BlackBerry UI look and feel JavaScript toolkit for WebWorks
Apache License 2.0
312 stars 192 forks source link

thx for non working playbook config #942

Closed BallRockReaper closed 11 years ago

BallRockReaper commented 11 years ago

Months ago I made an app for Z10 and with launch of Q10/Q5 I made it working on them, too and loaded all up to Vendor Portal. In a testversion I made it running on PlayBook, too, but did not upload it to Vendor Portal. Everything was fine. Today I decided to make an update und during that I decided to make an official PlayBook version, too. I loaded new bbui.js sample files and started working. At first: I did not change the config file in PlayBook version and hey, it runs perfect on my PlayBooks, but I can not upload it to Vendor Portal. So, I took a deeper look into the new PlayBook config file here and wow, a new config. But that is the problem: this config does not work on PlayBook and thx for no information about new files... With the old config file I can not upload the PlayBook version into Vendor Portal to the 2 allready existent bar files. With the new config file this app does not load... So what to do? Getting angry again and burn the PlayBook?

tneil commented 11 years ago

Not sure I understand your issue.. if I use the config file from the bb10 samples my application works both on PlayBook and BB10

thtro commented 11 years ago

just be sure to have the same aplication id in both config.xml files. initially for PlayBook there was no id necessary in config.xml but for BB10 it was. That id that is present in the config.xml is part of the bigger id that is assigned to each app. To add a PlayBook version to portal your app needs to have the same id as the app you initially uploaded (the BB10 version) and the exact same in config.xml.

BallRockReaper commented 11 years ago

Example: in BB10 config.xml you have to make an id="xx" AND

xxy

in PlayBook config.xml you only have to make

xxy

That's what I did all the time before, but this problem occured:

Z10 app: id="xx" ... xxy Q10/Q5 app: id="xx" .. xxy PlayBook app: xxy Reply from vendor portal: Z10 upload successfull Q10/Q5 upload: successfull PlayBook upload denied, because not having the same name

So I took a look into bbui.js here on github and saw: new files Okay, no problem, took them, changed everything and than I found in new PlayBook config.xml:

id=".." ... ..

The problem is: with the new config.xml the PlayBook app does not work. With the old version I can not upload that app into vendor portal. I make sure that names are in all 3 three cases the same (copy and paste the string).

tneil commented 11 years ago

So it sounds like this isn't a bbUI related issue. It's a difference in the WebWorks SDK for the PlayBook OS vs the BB10 OS and what is expected by BlackBerry World.

There are some differences/rules in the config.xml files for WebWorks on BBOS/PlayBook/BB10 outlined in the WebWorks documentation.

thtro commented 11 years ago

this is not related to bbui, the issue should be closed. post your complete config files in the webworks forums, someone will take a look at them.

BallRockReaper commented 11 years ago

Did some one of you take a closer look into your samples? I really know the difference between the config files because it's not the first time I am writing apps. So why should an issue be closed when I see an issue in posted samples?

And this is sample again of not understanding or not well done explaining.

tneil commented 11 years ago

The sample config file is working and tested when sideloaded onto a PlayBook or BB10 device. It hasn't been designed to be a single config file that will work with BlackBerry World submissions for a production application trying to use the same product ID for both a PlayBook and BB10 application.

It is simply a sample to show the application working on a PlayBook or BB10 device