Status Update
No update yet.
Comments
he...@gmail.com
Chrome Diagnostics Report of following results:
The DNS diagnostic test in Chrome Diagnostics Report is known to have some issues in some configuration. Internal bug id is
Here the diagnostic failure could indicate a real problem. Jason, Jie, what m126 bugs could this report be a duplicate of ?
st...@google.com
what m126 bugs could this report be a duplicate of ?
Not anything off the top of my head now (maybe Jason knows other). Since the device is not enterprise-enrolled according to the information in #1, I assume it should not hit the diagnostic DNS issue in
But I assume the reporter also encountered the issue of "no connection to gateway" in the diagnostic app, which is partially fixed on M128 in
Re #1,
Thanks for reporting the issue and sorry for the late reply here. A few questions to help us understanding the issue bettter:
- Are you still experiencing this issue? If so, could you file a feedback report (alt-shift-i, and put "
b/360530624 - Does it only happen on a certain WiFi network? If it's the case, do you by chance have other devices (not Chromebook) to see if they work on the same network?
Thanks!
he...@gmail.com
This might be a dup of the internal bug of
As Jie mentioned, if this is still reproducible, a feedback report would help debug the issue further. Thank you!
na...@gmail.com
nk...@gmail.com
Bugjuggler: wait 8w -> hugobenichi
zh...@gmail.com
jr...@gmail.com
It is still happening, so I will report the next instance with the requested text. It doesn't happen on a specific network, but all networks I am connecting to. It's not repeatable on other non ChromeOS devices in at least two of those, but is repeatable on the exact same device of another owner. I can ask them to also report with the reference number if that is helpful. Let me know if I can provide any additional information or troubleshooting.
I am out of the office for a few days this weekend, but should be able to repeat issue by eod Monday.
ju...@gmail.com
ay...@gmail.com
I looked at 2 reports, in both case we see that the WiFi network service state is eventually changed to "failure".
Rerouting to WiFi component to take an initial look if this is a WiFi issue.
ri...@gmail.com
The client device disconnected from wifi_psk_6 due to "no remaining endpoints", and disconnected from wifi_psk_8 due to reconnect timeout. The connection to wifi_psk_36 was unstable, link monitor failure occurred and PREV_AUTH_NOT_VALID error observed during reconnection.
do...@gmail.com
<tirage> Kevin to take a look, figure out if it is L2 or L3 issue.
Description
(Note: It is the build when sending this report. For exact build reference, please see the attached bugreport.)
What type of Android issue is this? Other issue
When did this happen?
Apr 12, 2023 7:20 PM GMT-06:00
What steps would let us observe this issue?
1. Try to unlock with fingerprint
What did you expect to happen?
Unlock the phone
What actually happened?
Error and ask for the pin
How often has this happened?
Occasionally
What was the effect of this issue on your device usage, such as lost time or work?
High
Debugging information
Servicios de Google Play
com.google.android.gms
Version 231354044 (23.13.54 (190400-520938292))
System App (Updated)
Android System WebView
com.google.android.webview
Version 567202444 (113.0.5672.24)
System App (Updated)
Network operator: Not available
SIM operator: TELCEL
Filed by Android Beta Feedback. Version (Updated): 2.33-betterbug.external_20230301_RC01 (DOGFOOD)
To learn more about our feedback process, please visit