You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Ethan Cheng edited this page May 2, 2024
·
3 revisions
Overview
Here we outline some common problems you might face during development.
Incorrect Extension ID
Note that for Post-login PWA and local development, we use the gogonhoemckpdpadfnjnpgbjpbjnodgc extension ID, generated from the key attribute in package.json. For the Shimless RMA usecase, we use the jmalcmbicpnakfkncbgbcmlmgpfkhdca extension ID, generated from signing the extension.
Incorrect Chrome version
Only newer chrome version supports certain APIs. Verify you are on the newest Chrome version.
Incorrect file permission
Ensure that files can be viewed by the chronos user. Incorrect file permission may lead to errors such as:
Not seeing the files in the file app
CRX Header Invalid log
Incorrect allowlisted origins
You should make sure the the origins in these three places are equivalent:
externally_connectable attribute in the extension manifest
Actual URL of the PWA or IWA
Allowlisted URL in Chrome
For PWA, you should override 3. with the OS flag --telemetry-extension-pwa-origin-override-for-testing=$ORIGIN.
For IWA, the app built by running npm run build_iwa should automatically be the correct origin.