Building ChromiumOS - Google API keys are missing

592 views
Skip to first unread message

Антон Лебедев

unread,
Jul 19, 2020, 4:56:23 PM7/19/20
to Chromium OS Development
Hello, guys!
I have some troubles with API keys.
After installation of my custom build I got this error (https://sun9-47.userapi.com/c856524/v856524120/1d9683/yRqTXg3f1Uo.jpg).

I tried to do everything according to docs, but my attempts have no effect.
So, I did i the following:

1. Create ".googleapikeys" file in the user root folder with content like this (I've changed real values due to privacy):

google_api_key = "my_api_key"
google_default_client_id = "my_client_id"
google_default_client_secret = "my_client_secret"

2. Then a second time I've changed the format according to advice in this topic https://groups.google.com/u/2/a/chromium.org/g/chromium-os-dev/c/IEbmZImPEg8/m/1dkQRZ6XAQAJ

'google_api_key': ' my_api_key',
'google_default_client_id': ' my_client_id',
'google_default_client_secret': ' my_client_secret',

and build new image.


I deleted old ".googleapikeys" file inside chroot, so the second time I've got INFO message about adding changed file, so I thought I was doing everything right.

I noticed that in this article http://www.chromium.org/developers/how-tos/api-keys  there are no words about ".googleapikeys" file. What about "args.gn" file - I have not found any information about using command "gn args out/your_out_dir_here". What means "your_out_dir_here"? Where should I run it? I don't know.

I've also tried to create "/etc/chrome_dev.conf" file in the "/etc" directory of the chroot and place my API keys there. And it also takes no effect after rebuild. Maybe I did something wrong.

So I have no idea why my API keys are missing.

I'd appreciate any help.

Mike Frysinger

unread,
Jul 25, 2020, 12:42:06 PM7/25/20
to Антон Лебедев, Chromium OS Development
once you've created the ~/.googleapikeys file, you have to rebuild Chrome.  you can force it with `emerge-$BOARD chromeos-chrome` -- build_packages by default won't work.  that will take care of passing the content to Chrome's gn for you.

then re-run build_image to include the change in the new image.
-mike

--
--
Chromium OS Developers mailing list: chromiu...@chromium.org
View archives, change email options, or unsubscribe:
https://groups.google.com/a/chromium.org/group/chromium-os-dev

Seongbin BAK

unread,
Jun 30, 2021, 12:46:00 PM6/30/21
to Chromium OS Development, Mike Frysinger, Chromium OS Development, dunl...@gmail.com
Mike.
When emerge Chrome for .googleapikeys, have to use local source with cros_workon? or just can download built Chrome package from server?
Reply all
Reply to author
Forward
0 new messages