Unable to sign into Chromium

[cyberrufus]

Unable to sign into Chromium (either my builds or snapshots) since  142.0.7405.0 (1513409). Keys are loaded at runtime and I'm consistently receiving an bad client ID error in sign-in internals. Used a new client ID with the same results. Any assistance would be appreciated. 

[cyberrufus]

Receiving different sign-in internals errors with an existing profile and a clean one, but this is consistent in both:

Missing authorization code due to OAuth outage in Dice.

[Pavel Ferst]

Same here in 142.0.7421.0. Also login to gmail impossible - 5 seconds after loging it logs out spontaneously. Didn't do it in self-compiled 141.0.7379.0.
Interestingly it is possible log in to and work in gmail in Incognito window :-D (?!?!)
(
Messages are mostly
  ... OnGetTokenFailure: Service responded with error: 'bad client id: ...'        (the same id works well on another computer with the previous build, see above)
sometimes preceded by:
  "Missing ID token on refresh token fetch respons."
)

[Alex Ilin]

If you aren't already aware, signing in to Chromium is restricted: https://www.chromium.org/developers/how-tos/api-keys/#signing-in-to-chromium-is-restricted, so it's expected that you see these errors.

--
--
Chromium Developers mailing list: chromi...@chromium.org
View archives, change email options, or unsubscribe:
http://groups.google.com/a/chromium.org/group/chromium-dev
---
You received this message because you are subscribed to the Google Groups "Chromium-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to chromium-dev...@chromium.org.
To view this discussion visit https://groups.google.com/a/chromium.org/d/msgid/chromium-dev/78b9b798-b540-4bbb-abca-00def047264an%40chromium.org.

[Pavel Ferst]

Yes, buth shouldn´t it be possible, if you have in "My Groups" the   google-browser-si...@chromium.org ?

ср, 24 сент. 2025 г. в 12:16, Alex Ilin <alex...@chromium.org>:

[Pavel Ferst]

Moreover, it worked well all the years until the build 141.x.y.z but no more works in self-compiled builds 142.0.7419.0 and 142.0.7433.0. 
Is there a change of policy, or some small gap in the refactoring of the OAuth in these new builds?
(
And yes, I have  google-browser-si...@chromium.org  in "My Groups"
and I have enabled "Chrome Sync API" in the google console for my account ...
)

[Alex Ilin]

Since the issue doesn't reproduce in Chrome builds, could you try to find a bad revision using https://www.chromium.org/developers/bisect-builds-py/ ?

On Thu, Sep 25, 2025 at 12:52 AM Pavel Ferst <fer...@gmail.com> wrote:

Could this "sign in - automatic sign out 'loop' - with the refresh token problem in log" problem
be some side affect of this fix attempt (from 10.9.) for a strange problem 432427059 :

https://chromium.googlesource.com/chromium/src/+/6203e134542cec44883533765b1e146ffb502d41%5E%21/
(??)

ср, 24 сент. 2025 г. в 22:49, Pavel Ferst <fer...@gmail.com>:

I have looked at the history of my build and can say that for me the problem must have come somewhere between 29.8.2025, build 141.0.7383 and 17.9.2025 build 142.0.7419.0.
Hope it can help to localize it.

ср, 24 сент. 2025 г. в 20:47, cyberrufus <joe...@gmail.com>:

Receiving that error message pretty consistently. Able to sign into Chromium successfully on this build with code changes, but the issue remains on my own builds and snapshots.  I have filed a bug report.

[Pavel Ferst]

Could this "sign in - automatic sign out 'loop' - with the refresh token problem in log" problem
be some side affect of this fix attempt (from 10.9.) for a strange problem 432427059 :

https://chromium.googlesource.com/chromium/src/+/6203e134542cec44883533765b1e146ffb502d41%5E%21/
(??)

ср, 24 сент. 2025 г. в 22:49, Pavel Ferst <fer...@gmail.com>:

I have looked at the history of my build and can say that for me the problem must have come somewhere between 29.8.2025, build 141.0.7383 and 17.9.2025 build 142.0.7419.0.
Hope it can help to localize it.

ср, 24 сент. 2025 г. в 20:47, cyberrufus <joe...@gmail.com>:

Receiving that error message pretty consistently. Able to sign into Chromium successfully on this build with code changes, but the issue remains on my own builds and snapshots.  I have filed a bug report.

On Wednesday, September 24, 2025 at 11:50:32 AM UTC-4 Pavel Ferst wrote:

[Pavel Ferst]

I have looked at the history of my build and can say that for me the problem must have come somewhere between 29.8.2025, build 141.0.7383 and 17.9.2025 build 142.0.7419.0.
Hope it can help to localize it.

ср, 24 сент. 2025 г. в 20:47, cyberrufus <joe...@gmail.com>:

Receiving that error message pretty consistently. Able to sign into Chromium successfully on this build with code changes, but the issue remains on my own builds and snapshots.  I have filed a bug report.

On Wednesday, September 24, 2025 at 11:50:32 AM UTC-4 Pavel Ferst wrote:

[Pavel Ferst]

Could be in relation with these messages:

[104124:104141:0924/185127.814381:ERROR:google_apis/gcm/engine/registration_request.cc:292] Registration response error message: DEPRECATED_ENDPOINT
[104124:104124:0924/185135.493585:ERROR:google_apis/gaia/gaia_auth_fetcher.cc:70] Missing ID token on refresh token fetch response.

especially the second one, as the first one comes also with functioning browsers (older builds or Debian chromium).

[cyberrufus]

Receiving that error message pretty consistently. Able to sign into Chromium successfully on this build with code changes, but the issue remains on my own builds and snapshots.  I have filed a bug report.

On Wednesday, September 24, 2025 at 11:50:32 AM UTC-4 Pavel Ferst wrote:

[Alex Ilin]

Thanks a lot for running the bisect!

I see my change https://crrev.com/c/6888991 in this list, and it is likely the culprit. 

Although I expected my change to only affect testing bots, field trial testing configs also get applied by default to Chromium builds, according to https://chromium.googlesource.com/chromium/src/+/main/testing/variations/README.md.

Could you try running Chrome with a --disable-field-trial-config command line flag and check that the issue is fixed? 

On Fri, Sep 26, 2025 at 10:43 PM Pavel Ferst <fer...@gmail.com> wrote:

I did it.

(The google account authentication got mad from so many signing attempts and I had to authenticate in more and more tedious ways in the process :-D )

Below is the command line picture of the process, 
more about the changes which could cause the problem is probably under the link in the last lines there.

Summary of the result:

It must have happened between 142.0.7392.0 and 142.0.7393,0,

more precisely between revisions 1510204 and 1510220

----------------------------------------------------

pavfer@MySID:~/data/bisect$ python3 tools/bisect-builds.py -a linux64 -g 142.0.7391.0 -b 142.0.7405.0 --verify-range
Downloading list of known revisions. If the range is large, this can take several minutes...

Loaded revisions 1509978-1513409 from /mnt/64ac556c-fa3c-4c66-a87c-a939116c8b46/bisect/tools/.bisect-builds-cache.json
Saved revisions 1509978-1513409 to /mnt/64ac556c-fa3c-4c66-a87c-a939116c8b46/bisect/tools/.bisect-builds-cache.json
Downloading revision 1509978...
Received 212197112 of 212197112 bytes, 100.00%
Trying revision 1509978: /tmp/tmp3zv8nx_1chrome-linux.zip in /tmp/bisect_tmpcal2q8jp
Revision 1509978 is [(g)ood/(b)ad/(r)etry/(u)nknown/(s)tdout/(q)uit]: g
Downloading revision 1513409...
Trying revision 1513409: /tmp/tmpk151keb8chrome-linux.zip in /tmp/bisect_tmp3b89w5ii
Revision 1513409 is [(g)ood/(b)ad/(r)etry/(u)nknown/(s)tdout/(q)uit]: b
You have 622 revisions with about 10 steps left.
Bisecting range [1513409 (bad), 1509978 (good)].
Downloading revision 1512048...
Received 212322883 of 212322883 bytes, 100.00%
Trying revision 1512048: /tmp/tmp9qw76lu9chrome-linux.zip in /tmp/bisect_tmp1jn7f47o
Revision 1512048 is [(g)ood/(b)ad/(r)etry/(u)nknown/(s)tdout/(q)uit]: b
You have 312 revisions with about 9 steps left.
Bisecting range [1512048 (bad), 1509978 (good)].
Downloading revision 1511047...
Trying revision 1511047: /tmp/tmpgblpqfjkchrome-linux.zip in /tmp/bisect_tmp3hdpvb6g
Revision 1511047 is [(g)ood/(b)ad/(r)etry/(u)nknown/(s)tdout/(q)uit]: b
You have 157 revisions with about 8 steps left.
Bisecting range [1511047 (bad), 1509978 (good)].
Downloading revision 1510580...
Trying revision 1510580: /tmp/tmp8pl844fschrome-linux.zip in /tmp/bisect_tmpqghpy38i
Revision 1510580 is [(g)ood/(b)ad/(r)etry/(u)nknown/(s)tdout/(q)uit]: b
You have 79 revisions with about 7 steps left.
Bisecting range [1510580 (bad), 1509978 (good)].
Downloading revision 1510144...
Trying revision 1510144: /tmp/tmplz41xltkchrome-linux.zip in /tmp/bisect_tmpdwuyf9g7
Revision 1510144 is [(g)ood/(b)ad/(r)etry/(u)nknown/(s)tdout/(q)uit]: g
You have 40 revisions with about 6 steps left.
Bisecting range [1510580 (bad), 1510144 (good)].
Downloading revision 1510347...
Trying revision 1510347: /tmp/tmp5l3ip1x8chrome-linux.zip in /tmp/bisect_tmpbv9df_rn
Revision 1510347 is [(g)ood/(b)ad/(r)etry/(u)nknown/(s)tdout/(q)uit]: b
You have 21 revisions with about 5 steps left.
Bisecting range [1510347 (bad), 1510144 (good)](https://crrev.com/1510144..1510347).
Downloading revision 1510204...
Trying revision 1510204: /tmp/tmpohqgqkljchrome-linux.zip in /tmp/bisect_tmpyh9yxo1n
Revision 1510204 is [(g)ood/(b)ad/(r)etry/(u)nknown/(s)tdout/(q)uit]: g
You have 11 revisions with about 4 steps left.
Bisecting range [1510347 (bad), 1510204 (good)](https://crrev.com/1510204..1510347).
Downloading revision 1510287...
Trying revision 1510287: /tmp/tmpibeqqyxpchrome-linux.zip in /tmp/bisect_tmpbpvv1y7y
Revision 1510287 is [(g)ood/(b)ad/(r)etry/(u)nknown/(s)tdout/(q)uit]: b
You have 6 revisions with about 3 steps left.
Bisecting range [1510287 (bad), 1510204 (good)](https://crrev.com/1510204..1510287).
Downloading revision 1510241...
Trying revision 1510241: /tmp/tmp_wcl25v5chrome-linux.zip in /tmp/bisect_tmp4h8foxrc
Revision 1510241 is [(g)ood/(b)ad/(r)etry/(u)nknown/(s)tdout/(q)uit]: b
You have 4 revisions with about 2 steps left.
Bisecting range [1510241 (bad), 1510204 (good)](https://crrev.com/1510204..1510241).
Downloading revision 1510230...
Trying revision 1510230: /tmp/tmpseioawwqchrome-linux.zip in /tmp/bisect_tmp9aynvk_x
Revision 1510230 is [(g)ood/(b)ad/(r)etry/(u)nknown/(s)tdout/(q)uit]: b
You have 3 revisions with about 1 steps left.
Bisecting range [1510230 (bad), 1510204 (good)](https://crrev.com/1510204..1510230).
Downloading revision 1510220...
Trying revision 1510220: /tmp/tmpibas77ipchrome-linux.zip in /tmp/bisect_tmp6m80sk1f
Revision 1510220 is [(g)ood/(b)ad/(r)etry/(u)nknown/(s)tdout/(q)uit]: b
You are probably looking for a change made after 1510204 (known good), but no later than 1510220 (first known bad).
CHANGELOG URL:
https://chromium.googlesource.com/chromium/src/+log/ae6f735343fc2802ea8c89c60a6b3797f08d895d..2f3d0d172df2d42a87af38b6298235e26c65292a
pavfer@MySID:~/data/bisect$