718395 - J-PAKE code is never displayed

Status: VERIFIED WORKSFORME

(Firefox for Android Graveyard :: Android Sync, defect)

Description

[Cristian Nicolae (:xti)]

Attachment: J-PAKE setup screenshot

Mozilla/5.0 (Android;Linux armv7l;rv:12.0a1)Gecko/20120116
Firefox/12.0a1 Fennec/12.0a1
Devices: Samsung Galaxy S, HTC Desire Z
OS: Android 2.2, Android 2.3.3

Steps to reproduce:
1. Install the latest Nightly build
2. Open Firefox Sync App

Expected result:
J-PAKE code is displayed

Actual result:
J-PAKE code is missing as you can see in the attached screenshot.

Comment 1

[Richard Newman [:rnewman]]

(In reply to Cristian Nicolae (:xti) from comment #0)

> Devices: Samsung Galaxy S, HTC Desire Z
> OS: Android 2.2, Android 2.3.3

My guess is that this is Bug 717691. Can you get an adb log from when you launch setup?

Thanks for the report!

Comment 2

[Cristian Nicolae (:xti)]

Attachment: log

Comment 3

[Cristian Nicolae (:xti)]

(In reply to Richard Newman [:rnewman] from comment #1)
> (In reply to Cristian Nicolae (:xti) from comment #0)
> 
> > Devices: Samsung Galaxy S, HTC Desire Z
> > OS: Android 2.2, Android 2.3.3
> 
> My guess is that this is Bug 717691. Can you get an adb log from when you
> launch setup?
> 
> Thanks for the report!

I attached the log file. I hope that it will be useful.

This occurs mostly on Android 2.2, so as you said, it might be related to bug 717691.

Comment 4

[Richard Newman [:rnewman]]

Well, that's strange; no stand-out error in the log. Humph.

Comment 5

[Tony Chung [:tchung]]

(In reply to Cristian Nicolae (:xti) from comment #0)
> Created attachment 588844 [details]
> J-PAKE setup screenshot
> 
> Mozilla/5.0 (Android;Linux armv7l;rv:12.0a1)Gecko/20120116
> Firefox/12.0a1 Fennec/12.0a1
> Devices: Samsung Galaxy S, HTC Desire Z
> OS: Android 2.2, Android 2.3.3
> 
> Steps to reproduce:
> 1. Install the latest Nightly build
> 2. Open Firefox Sync App
> 
> Expected result:
> J-PAKE code is displayed
> 
> Actual result:
> J-PAKE code is missing as you can see in the attached screenshot.

Nicolae, does the code ever show up?   can you confirm if other devices are seeing this problem?   Possibly eliminating flaky wifi networks

Comment 6

[Cristian Nicolae (:xti)]

(In reply to Tony Chung [:tchung] from comment #5)
> 
> Nicolae, does the code ever show up?   can you confirm if other devices are
> seeing this problem?   Possibly eliminating flaky wifi networks

No, the code is never displayed. This issue occurs only for Froyo devices. I cannot reproduce it anymore on Gingerbread phones. 

Also I can confirm that wifi network works fine.

Comment 7

[Tony Chung [:tchung]]

(In reply to Cristian Nicolae (:xti) from comment #6)
> (In reply to Tony Chung [:tchung] from comment #5)
> > 
> > Nicolae, does the code ever show up?   can you confirm if other devices are
> > seeing this problem?   Possibly eliminating flaky wifi networks
> 
> No, the code is never displayed. This issue occurs only for Froyo devices. I
> cannot reproduce it anymore on Gingerbread phones. 

needs testing on another froyo device.  Looks like the attached log isnt retrieving the jpake code:

01-17 11:37:27.422: D/JPakeRequest(15752): new URI: https://setup.services.mozilla.com/new_channel
01-17 11:37:27.422: I/BaseResource(15752): HTTP GET https://setup.services.mozilla.com/new_channel
01-17 11:37:27.445: D/class ch.boye.httpclientandroidlib.impl.conn.DefaultClientConnection(15752): Connection shut down

Comment 8

[Cristian Nicolae (:xti)]

Attachment: log_htc_desire

I tried to get the J-Pake code twice as you can see in the attached log, but there is the same actual result.

--
Mozilla/5.0 (Android;Linux armv7l;rv:12.0a1)Gecko/20120119
Firefox/12.0a1 Fennec/12.0a1
Device: HTC Desire
OS: Android 2.2

Comment 9

[Richard Newman [:rnewman]]

The absence of logging between the "GET" line and the "Connection shut down" line makes me suspect a runtime exception somewhere; a quick look suggests that all of the success and failure paths for that request should log.

My continued hypothesis is that this is the same as Bug 717691, with some missing chunk of crypto code. Let's see if we can fix that and make forward progress on this, too.

Until then we can put the lower bound for compatibility with Sync at 2.3.x.

Comment 10

[Richard Newman [:rnewman]]

Does this work with current Nightly?

Comment 11

[Andreea Pod]

Verified worksforme on build: Mozilla /5.0 (Android;Linux armv7l;rv:12.0a1) Gecko/20120131 Firefox/12.0a1 Fennec/12.0a1
Device: Samsung Galaxy S