New issue
Advanced search Search tips

Issue 851824 link

Starred by 1 user

Issue metadata

Status: WontFix
Owner: ----
Closed: Jun 2018
EstimatedDays: ----
NextAction: ----
OS: Linux , Windows , Mac
Pri: 2
Type: Bug



Sign in to add a comment

Google API keys are missing. Some functionality of Chromium will be disabled.

Reported by roven...@gmail.com, Jun 12 2018

Issue description

UserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/67.0.3396.79 Safari/537.36

Example URL:

Steps to reproduce the problem:
1. Open Chromium browser (ASUS NovaGo TP370QL windows on Qualcomm Snapdragon 835 soc)

2. Chromium will show "Google API keys are missing. Some functionality of Chromium will be disabled."
3. 

What is the expected behavior?
The browser will not show "Google API keys are missing. Some functionality of Chromium will be disabled."

What went wrong?
Chromium shows "Google API keys are missing. Some functionality of Chromium will be disabled."

Does it occur on multiple sites: N/A

Is it a problem with a plugin? N/A 

Did this work before? N/A 

Does this work in other browsers? N/A

Chrome version: 69.0.3455.0  Channel: stable
OS Version: 10.0
Flash Version:
 
ChromiumError.jpg
115 KB View Download
Labels: Needs-Triage-M69
Components: UI>Browser
Labels: -Type-Compat Triaged-ET M-69 Target-69 FoundIn-69 OS-Linux OS-Mac Type-Bug-Security
Status: Untriaged (was: Unconfirmed)
Able to reproduce the issue on Mac 10.13.3, Win-10 and Ubuntu 14.04 using chrome reported version #69.0.3455.0.
This is a non-regression issue as it is observed from M60 old builds. 

Hence, marking it as untriaged to get more inputs from dev team.

Thanks...!!

Comment 3 by wfh@chromium.org, Jun 18 2018

Components: -UI>Browser
Labels: -Type-Bug-Security Type-Bug
Status: WontFix (was: Untriaged)
This is working as intended. Chromium builds do not have Google API keys in them. If you want to use Google API with chromium build, create a cloud account and get your own keys then embed them.

Not sure why this was marked a security bug.

Sign in to add a comment