Status Update
No update yet.
Comments
sy...@google.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 ?
sy...@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!
lb...@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!
ch...@gmail.com
sy...@google.com
Bugjuggler: wait 8w -> hugobenichi
lb...@gmail.com
lb...@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.
sy...@google.com
sy...@google.com
al...@android.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.
Description
compile 'com.android.support:recyclerview-v7:23.1.1'
compile 'com.android.support:appcompat-v7:23.1.1'
Version used:
Theme used:
default when created new project.
Devices/Android versions reproduced on:
Nexus 5 with Android 6.0.1
- Relevant code to trigger the issue.
<RelativeLayout
xmlns:android="
xmlns:tools="
android:layout_width="match_parent"
android:layout_height="match_parent">
<android.support.v7.widget.RecyclerView
android:id="@+id/recyclerView"
android:layout_width="match_parent"
android:layout_height="match_parent"
android:nestedScrollingEnabled="false"
/>
</RelativeLayout>
- A screenrecord or screenshots showing the issue (if UI related).
not needed. it crashes.
Weird thing is that it doesn't crash in case I do this in code:
RecyclerView recyclerView = (RecyclerView) findViewById(R.id.recyclerView);
recyclerView.setNestedScrollingEnabled(false);
Attached a sample project to show the issue.
Also attached a crash log.
btw, it doesn't matter if the RecyclerView is inside a NestedScrollView or not.