Jeff Griffiths (:canuckistani) (:⚡︎) Reporter
	Description • 9 years ago

From uservoice: https://ffdevtools.uservoice.com/forums/246087-firefox-developer-tools-ideas/suggestions/8247039-wi-fi-debugging-on-windows-10

Windows 10 is coming in July, we should look into this soon.

	J. Ryan Stinnett [:jryans] (Use needinfo, replies may be slow)
	Comment 1 • 9 years ago

I just gave this a try on Windows 10 (Build 10130), and it worked for me the same as it does on Windows 8.1.

There is the firewall prompt to approve the first time you scan for WiFi devices, which was true with 8.1 as well.

We'll need to get more info from these users.  Can we contact them directly or only leave comments on user voice?

	Jeff Griffiths (:canuckistani) (:⚡︎) Reporter
	Comment 2 • 9 years ago

(In reply to J. Ryan Stinnett [:jryans] (use ni?) from comment #1)
> I just gave this a try on Windows 10 (Build 10130), and it worked for me the
> same as it does on Windows 8.1.
> 
> There is the firewall prompt to approve the first time you scan for WiFi
> devices, which was true with 8.1 as well.
> 
> We'll need to get more info from these users.  Can we contact them directly
> or only leave comments on user voice?

Default is to comment on the UV issue - I do have an email address in UV but I would prefer to try comments first.

	Caleb T
	Comment 3 • 9 years ago

I'm the original poster on Uservoice.  Fx Dev Edition can now find my Flame over WiFi on the Win10 tech preview (Build 10130), but the Flame does not activate its QR code scanner like it should.

Attempting to connect by clicking on the device in WebIDE will pull up a QR code on my PC and cause the Flame to ask to either "Scan" or "Scan and remember".  Tapping either of those dismisses the popup and nothing happens after that.  The phone does not switch on the camera to scan for the code.

A factory reset of the phone does not seem to do anything.

Let me know if you guys need more info.

	Caleb T
	Comment 4 • 9 years ago

Problem was fixed by the 6/15/2015 update.  Tested with base v18D updated via the 6/15 update on 2 FxOS devices with WebIDE on Fx Dev Edition on Windows 10 build 10130; everything works correctly now.

	J. Ryan Stinnett [:jryans] (Use needinfo, replies may be slow)
	Comment 5 • 9 years ago

(In reply to Cal from comment #4)
> Problem was fixed by the 6/15/2015 update.  Tested with base v18D updated
> via the 6/15 update on 2 FxOS devices with WebIDE on Fx Dev Edition on
> Windows 10 build 10130; everything works correctly now.

Hooray!  I suspect some kind of intermittent Gaia issue in that case.  If you have trouble again in the future, feel free to re-open the bug.

	Caleb T
	Comment 6 • 9 years ago

(In reply to J. Ryan Stinnett [:jryans] (use ni?) from comment #5)
> (In reply to Cal from comment #4)
> > Problem was fixed by the 6/15/2015 update.  Tested with base v18D updated
> > via the 6/15 update on 2 FxOS devices with WebIDE on Fx Dev Edition on
> > Windows 10 build 10130; everything works correctly now.
> 
> Hooray!  I suspect some kind of intermittent Gaia issue in that case.  If
> you have trouble again in the future, feel free to re-open the bug.

Agreed.  Thanks!