Note: First make the script executable:
chmod +x tool/build_extension.sh
./tool/build_extension.sh
/dev_build/web
directory../tool/build_extension.sh prod
/prod_build
directory.extension_key.txt
file:extension_key.txt
file at the root of /debug_extension
. Paste in the value of one of the whitelisted developer keys into this txt file. IMPORTANT: DO NOT COMMIT THE KEY. It will be copied into the manifest.json
when you build the extension.dev_build/web
web/manifest.json
, pubspec.yaml
, and in the CHANGELOG
.*At this point, you should manually verify that everything is working by following the steps in Local Development, except load the extension from the
prod_build
directory. You will need to add an extension key to themanifest.json
file inprod_build
to test locally.
prod_build
directory (NOT dev_build/web
). Remove the Googler extension key that was added by the builder to the manifest.json
file.version_XX.XX.XX.zip
(eg, version_1.24.0.zip
) and add it to the go/dart-debug-extension-zips folderYou must be a Googler to do this. Ask for help if not.
If you don’t see dart-bat as an option, you will need someone on the Dart team to add you to the dart-bat Google group.
The first time you do this, you will be asked to pay a $5 registration fee. The registration fee can be expensed.
The Chrome Web Store Developer Dashboard does not support rollbacks. Instead you must re-publish an earlier version. This means that the extension will still have to go through the review process, which can take anywhere from a few hours (most common) to a few days.
You must be a Googler to do this. Ask for help if not.
manifest.json
edit the version number to be the next sequential version after the current “bad” version (eg, the bad version is 1.28.0
and you are rolling back to version 1.27.0
. Therefore you change 1.27.0
to 1.29.0
).