Welcome!

Welcome to the official BlackBerry Support Community Forums.

This is your resource to discuss support topics with your peers, and learn from each other.

inside custom component

Web and WebWorks Development

Reply
Developer
Posts: 144
Registered: ‎11-27-2012
My Device: Z10 LE,Dev Alpha C
My Carrier: China Mobile
Accepted Solution

Sign problem after upgraded to webworks 2.0

[ Edited ]

here's my problem:

 

I've tested and signed my app "Emoji" and now trying to upload to blackberry world,but it was rejected because of a different Package-ID

 

my new config.xml is:

 

<widget id="emoji" version="1.0.3.5" xmlns="http://www.w3.org/ns/widgets"
xmlns:cdv="http://cordova.apache.org/ns/1.0">

....

</widget>

 

and my former config.xml is :

 

<?xml version="1.0" encoding="utf-8"?>
<widget xmlns="http://www.w3.org/ns/widgets"
xmlns:rim="http://www.blackberry.com/ns/widgets"
version="1.0.3.3" id="emoji">

...

</widget>

 

you can see that the 2 id settings are same.

 

BUT!!

 

when build in release mode, I got this in MANIFEST.MF file:

Package-Name: emoji
Package-Id: gYABgJSuBKzV0sdItE9Yz4yhs

 

and the former build is :

Package-Name: emoji

Package-Id: gYABgLXdKS-gRXFiK_zGEPk3Q

 

it changes!!!

 

Please help me with this,thanks!!

 

 


 

Edit:

 

I think maybe the problem is because I switched to sign with blackberryid ?

webworks 2.0 requires blackberryid,right?

which is not supported in webworks 1.0,right?

BlackBerry Cascades / WebWorks developer, Vendor name: anpho
Retired
Posts: 1,382
Registered: ‎07-02-2009
My Device: BlackBerry Bold 9900
My Carrier: Bell

Re: Sign problem after upgraded to webworks 2.0

As you know WebWorks 2.0 uses the new token-based code signing method, which is associated with your BBID account.

 

To keep the package-id values the same (between an old and new build) in your application MANIFEST.MF file, you must link your old code signing keys with the new token. That way the signing server recognizes your signature and applies the correct one to the compiled BAR file.  This is done using the following cli command:

 

https://developer.blackberry.com/native/documentation/core/com.qnx.doc.native_sdk.devguide/com.qnx.d...

 

More:

http://devblog.blackberry.com/2013/08/code-signing-keys-be-gone-welcome-blackberry-id/

 

Follow me on Twitter: @n_adam_stanley
-------------------------------------------------------------------------------------------------------------------------
Your app doesn't work? Use BlackBerry remote web inspector to find out why.
Retired
Posts: 203
Registered: ‎12-18-2012
My Device: Z10, Q10, Q5, Z30, Z3
My Carrier: Bell

Re: Sign problem after upgraded to webworks 2.0

Also, the legacy signing keys are still supported in WebWorks 2.0. You are encouraged to upgrade your keys to get the benefits of the BBID signing system, but it is not a requirement.

Bryan Higgins
BlackBerry WebWorks
@bryanhiggins