570491 - Update 0.4 docs regarding the auto-generation of the cryptographic keypair

Status: RESOLVED FIXED

(Add-on SDK Graveyard :: General, defect)

Description

[Hernán Rodriguez Colmeiro (:peregrino)]

User-Agent:       Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv:1.9.2.3) Gecko/20100401 Firefox/3.6.3
Build Identifier: 

The docs say that the key-pair is auto-generated when you create the XPI, but they are created when you run the module with "cfx run -a firefox".

Reproducible: Always

Comment 1

[Hernán Rodriguez Colmeiro (:peregrino)]

Another mention about this is on the "XPI Generation" page, under The Program ID:

"Each jetpack-based program (including add-on) gets a unique identifier string, based upon a cryptographic keypair generated the first time you run cfx xpi."

Comment 2

[Brian Warner [:warner :bwarner]]

Attachment: docs change to mention 'cfx run' too

does this docs update seem to explain the situtation well enough?

Comment 3

[Hernán Rodriguez Colmeiro (:peregrino)]

(In reply to comment #2)
> does this docs update seem to explain the situtation well enough?

I think it mostly does, but in line 174 I would replace "When you run `cfx xpi`" by "When you run `cfx xpi` or `cfx run`". I don't know if that's redundant, but if you feel so ignore my comment.

Also what I ment was regarding the file programs.md, line 87. There it says that if you run it with 'firefox -a run' it will run and o it's magic. But it doesn't say anything about that if you don't have the program id present, the same as with `cfx xpi` will happen. This can disorient people, as what you get is not what the documentation say will happen.

Comment 4

[Myk Melez [:myk] [@mykmelez]]

The Add-on SDK is no longer a Mozilla Labs experiment and has become a big enough project to warrant its own Bugzilla product, so the "Add-on SDK" product has been created for it, and I am moving its bugs to that product.

To filter bugmail related to this change, filter on the word "looptid".

Comment 5

[Myk Melez [:myk] [@mykmelez]]

This appears to have been fixed!