When building Chromium on Chromium OS, there are (at least) 3 environments for building that are relevant.
The mechanism for compiling API keys into the Chromium binary itself under Chromium OS uses copy-propagation between the layers.
The enter chroot functionality takes care of propagating the keys. If the file
To reset these the easiest way to update the chroot is simply:
and then the next time something enters the chroot, your native credentials will be copied in. If the keys are not working, try taking a look at the file to see if the format of your keys outside the chroot confused the propagation.
If you want your chroot to build something non-default or non-shared, you can enter the chroot and change the
The chromeos-base/chromeos-chrome ebuild takes care of respecting the keys in the chroots
Chromium OS > How Tos and Troubleshooting > Building Chromium for Chromium OS (simple chrome) >