Changes between Version 22 and Version 23 of BB10

Timestamp:

Jan 8, 2013, 3:32:12 PM (11 years ago)

Author:

Martin Kolman

Comment:

--

BB10

@@ -91 +91 @@
 
 === Packaging ===
+
+==== Getting the debug token ====
+To install correctly to the BB10 device, the package needs to be signed with a valid debug token.
+
+1. ''source'' the ''bbndk-env.sh'' script to your shell, so that you have the various BlackBerry utilities in your ''$PATH''
+{{{
+source bbndk-env.sh
+}}}
+
+2. fill in the online form for signing keys
+Note the PIN you've entered somewhere.
+
+3. generate a keypair
+'''NOTE: This step is very important, as it is completely omitted in the official BB10 documentation and without it the debug token generation will fail with a ''author.p12 file missing'' error'''
+
+'''NOTE2: use only lowercase letters and numbers in the store password as reportedly uppercase letters cause problems. '''
+
+{{{
+blackberry-keytool -genkeypair -storepass <new keystore password>3 -author <some string without spaces>
+}}}
+
+4. register the signing keys
+{{{
+blackberry-debugtokenrequest -register -csjpin <the pin you entered to the online form> -cskpass <probably also the pin you entered to the online form> client-RDK-*.csj
+}}}
+The following is probably only needed for the Playbook ?
+{{{
+blackberry-debugtokenrequest -register -csjpin <the pin you entered to the online form> -cskpass <probably also the pin you entered to the online form> client-PBDT-*.csj
+}}}
+
+6. find you device PIN
+Should be visible on-device in settings->About->Harware
+
+5. generate the debug token
+{{{
+blackberry-debugtokenrequest -storepass <the keystore password you've entered in step 3> -devicepin <device PIN> debug_token.bar
+}}}
+
+The debug_token.bar file now contains the debug token you can use to build packages (just for) your BB10 device. Plain and easy, not needlessly convoluted at all. :)
+
+==== Package contents ====
+
 The package needs to contain the application and any other libraries modRana needs to run. The libraries are stored in the folder the application gets installed into and are loaded by manipulating the ''PATH'' and ''LD_LIBRARY_PATH'' variables.