7c380f97d0
|
||
|---|---|---|
| dist | ||
| extension | ||
| .gitignore | ||
| CODE_OF_CONDUCT.md | ||
| LICENSE | ||
| Makefile | ||
| README.md | ||
| template-update.json | ||
README.md
ADB Extension
This is a Firefox extension that supports remote debugging in Firefox DevTools. It provides ADB binaries used by DevTools to connect to Firefox/GeckoView products on Android devices via USB.
Releases
-
Update the value of the
VERSIONvariable in theMakefile(and commit the change) -
Run
make package. The following files should have been generated in thedist/folder:$ tree dist ├── linux │ ├── adb-extension-0.0.7.0-linux.xpi │ └── update.json ├── linux64 │ ├── adb-extension-0.0.7.1-linux64.xpi │ └── update.json ├── mac64 │ ├── adb-extension-0.0.7.2-mac64.xpi │ └── update.json └── win32 ├── adb-extension-0.0.7.3-win32.xpi └── update.json -
Upload the different XPI files to AMO as unlisted versions. You MUST respect the order of the versions, i.e. start with
linux(because its version is0.0.7.0), thenlinux64(because its version is0.0.7.1), etc. -
Download the signed XPI files. Note that AMO changes the name of the signed XPIs so you have to rename each file individually. For example, uploading
adb-extension-0.0.7.0-linux.xpiwill produce a signed file named27a75f558d3c46da8dcd-0.0.7.0.xpi, which you'll need to rename toadb-extension-0.0.7.0-linux.xpi. -
Upload the signed XPI files and their
update.jsonfiles to the FTP server. Note that we'll want to upload the versioned XPIs (e.g.adb-extension-0.0.7.3-win32.xpi) as well as "latest" copies (e.g.adb-extension-latest-win32.xpi). You should have the following files to be added to the FTP server:# IMPORTANT: all the XPI files here are signed. They are not the same as above in Step 2. # The `update.json` files are coming from the Step 2, though. $ tree adb-0.0.7 ├── linux │ ├── adb-extension-0.0.7.0-linux.xpi │ ├── adb-extension-latest-linux.xpi │ └── update.json ├── linux64 │ ├── adb-extension-0.0.7.1-linux64.xpi │ ├── adb-extension-latest-linux64.xpi │ └── update.json ├── mac64 │ ├── adb-extension-0.0.7.2-mac64.xpi │ ├── adb-extension-latest-mac64.xpi │ └── update.json └── win32 ├── adb-extension-0.0.7.3-win32.xpi ├── adb-extension-latest-win32.xpi └── update.json # For each "arch", the "latest" XPI should be the same as the versioned one. $ sha256sum */*.xpi fb53093a114d074b44fae57b6c1333d2c05a16490de61851d9f9c68584c5131e linux/adb-extension-0.0.7.0-linux.xpi fb53093a114d074b44fae57b6c1333d2c05a16490de61851d9f9c68584c5131e linux/adb-extension-latest-linux.xpi 9f94434cc0aff1dc24afd10b3dce80429a287cfb82ab8dcee454c2f0210e98d6 linux64/adb-extension-0.0.7.1-linux64.xpi 9f94434cc0aff1dc24afd10b3dce80429a287cfb82ab8dcee454c2f0210e98d6 linux64/adb-extension-latest-linux64.xpi 4777e776d7d33e8998f2121168541f23a4d351e4cd526a945d1ea438ee25f478 mac64/adb-extension-0.0.7.2-mac64.xpi 4777e776d7d33e8998f2121168541f23a4d351e4cd526a945d1ea438ee25f478 mac64/adb-extension-latest-mac64.xpi 4ed47f030b24abb6de904b25e7cdff8d5475d7e1a6b0bbc581162bc3bc35826b win32/adb-extension-0.0.7.3-win32.xpi 4ed47f030b24abb6de904b25e7cdff8d5475d7e1a6b0bbc581162bc3bc35826b win32/adb-extension-latest-win32.xpi
Discussion
For questions and issues specific to this extension, you can use the GitHub issue tracker.
For more general questions about remote debugging in DevTools or DevTools in general, you can: