Closed GoogleCodeExporter closed 9 years ago
Can you provide a list of steps that lead to the issue?
Just to clarify, prior to the issue you were able to successfully find all
devices, then you were unable to find any of them, then you could only see one
device, and now you can see all devices?
What firmware build are you currently using?
Original comment by jonathan...@google.com
on 11 Nov 2014 at 6:46
[deleted comment]
Which sender are you using?
If Android, what version of Google Play Services is there?
If iOS, what's the SDK version?
Original comment by jonathan...@google.com
on 11 Nov 2014 at 8:44
1.- Sorry I do not know how to reproduce it. While I have seen similar behavior
in the past (some Chromecast devices missing on the list when I know they are
online), I have never figured out what caused it. In this case I was trying to
test issue #428 so I went over to each of my Chromecast devices and tested
them, they all worked fine. On my way back upstairs from the basement is when I
got disconnected from the last one I was using and started having trouble
finding the devices. The problem continued long enough that I could hookup the
phone to my computer and collect logs. The reason I mentioned going upstairs
from the basement is because there is a good chance I switched APs while doing
that. I have 3 UniFi APs.
2.- Kinda answered above, but yes, I used all 4 just minutes before I was
unable to find them, then I could find one (the one labeled Gym I think), and
then eventually I could see all of them.
3.- I did not collect the version numbers at that time but later on the day
when dealing with issue #428 I noticed Gym was on 22062 while the rest were on
19084. They have all updated to 22062 now.
Original comment by car...@instantbits.com
on 11 Nov 2014 at 8:50
Using Android. The logs attached were from my Android device. Google Play
Services 6.1.88
Original comment by car...@instantbits.com
on 11 Nov 2014 at 8:51
We've been having some ongoing device discovery issues. Merging this with 314
Original comment by jonathan...@google.com
on 12 Nov 2014 at 7:15
Original issue reported on code.google.com by
car...@instantbits.com
on 10 Nov 2014 at 7:02Attachments: