Unable to sign-in to Chromium build.
Reported by
dchau...@etouch.net,
Jul 11
|
|||||
Issue descriptionChrome Version: 69.0.3489.0 (Developer Build) (32-bit) Revision 6a928407d6a613a2eb3418a98643067c267e6fba-refs/heads/master@{#574109} OS: Mac(10.12.6, 10.13.1, 10.13.6, 10.14), Windows(7,8,8.1,10) and Linux(14.04). What steps will reproduce the problem? 1. Launch Chromium build and try to sign-in with valid credentials and observe. Actual: Unable to sign-in to Chromium build. Expected: Should be able to sign-in to Chromium build. This is a non-regression issue, seen from M-60 series. NOTE: 1. This issue is only reproducible on Chromium builds. 2. Issue is not reproducible on Chrome builds. Kindly review the attached screen-cast for reference. Thank you.
,
Jul 12
Have you configured API keys as explained here: https://www.chromium.org/developers/how-tos/api-keys ?
,
Jul 12
,
Jul 13
With response to comment #2 & 3: No, we have not configured API keys. We don't have permission to configure the API's as Chromium account is required to configure it. Thank you.
,
Jul 27
--Chrome Identity automated triaging-- This bug is Untriaged and has gone for two weeks without any activity, so it is being moved to Available. Please see https://goo.gl/78kbny for more details. Please remove the Services>SignIn or UI>Browser>Profiles components if this bug isn't related to Chrome Identity. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Jul 29
Marking as WontFix for now, since I believe this is just a matter of properly configuring API keys. |
|||||
►
Sign in to add a comment |
|||||
Comment 1 by nyerramilli@chromium.org
, Jul 11