Closed Bug 1013642 Opened 11 years ago Closed 11 years ago

[B2G][Contacts]User is unable to link contacts to Facebook friends

Categories

(Firefox OS Graveyard :: Gaia::Contacts, defect)

ARM
Gonk (Firefox OS)
defect
Not set
normal

Tracking

(blocking-b2g:2.0+, b2g-v1.4 unaffected, b2g-v2.0 affected)

RESOLVED WORKSFORME
blocking-b2g 2.0+
Tracking Status
b2g-v1.4 --- unaffected
b2g-v2.0 --- affected

People

(Reporter: astole, Unassigned)

Details

(Keywords: regression, smoketest)

Attachments

(3 files)

Attached file logcat
Linking Contact to Facebook friend gets stuck on the linking screen. Only way to return to Contacts is to kill the app. Repro Steps: 1) Update a Open_C to BuildID: 20140520040203 2) Have a contact created as well as a Facebook contact imported 3) Select contact 4) Select "Link contact" and select Facebook contact Actual: Device gets stuck on linking screen Expected: Contacts can be linked to Facebook friends 2.0 Environmental Variables: Device: Open_C 2.0 MOZ BuildID: 20140520040203 Gaia: 8a2352d5b7be27ec4b1ea18c680ebcd0b6d34348 Gecko: cb9f34f73ebe Version: 32.0a1 Firmware Version: P821A10v1.0.0B06_LOG_DL Repro frequency: 3/3, 100% See attached: Screenshot, logcat
This issue also occurs on 2.0 on Buri. 2.0 Environmental Variables: Device: Buri 2.0 MOZ BuildID: 20140520040203 Gaia: 8a2352d5b7be27ec4b1ea18c680ebcd0b6d34348 Gecko: cb9f34f73ebe Version: 32.0a1 Firmware Version: V1.2-device.cfg This issue does not occur on the latest 1.4 1.4 Environmental Variables: Device: Open_C 1.4 MOZ BuildID: 20140520000201 Gaia: 17b102ee8d9a724b62285547cc5f1c5d30bfb01c Gecko: 95be84248033 Version: 30.0 Firmware Version: P821A10v1.0.0B03_LOG_DL
blocking-b2g: --- → 2.0?
Keywords: qaurgent
Attached image Screenshot
Attaching screenshot
QA Contact: jmitchell
B2G Inbound Regression Window: Last Working: Environmental Variables: Device: Open_C 2.0 BuildID: 20140517113002 Gaia: d364c473012b7731688fe0ef4bca92358cee18c5 Gecko: f913ad39fa23 Version: 32.0a1 Firmware Version: P821A10V1.0.0B06_LOG_DL First Broken: Environmental Variables: Device: Open_C 2.0 BuildID: 20140519053002 Gaia: 8a2352d5b7be27ec4b1ea18c680ebcd0b6d34348 Gecko: 8508ab79921f Version: 32.0a1 Firmware Version: P821A10V1.0.0B06_LOG_DL Last Working Gaia First Broken Gecko: Issue does NOT reproduce Gaia: d364c473012b7731688fe0ef4bca92358cee18c5 Gecko: 8508ab79921f First Broken Gaia Last Working Gecko: Issue DOES reproduce Gaia: 8a2352d5b7be27ec4b1ea18c680ebcd0b6d34348 Gecko: f913ad39fa23 Gaia pushlog: https://github.com/mozilla-b2g/gaia/compare/d364c473012b7731688fe0ef4bca92358cee18c5...8a2352d5b7be27ec4b1ea18c680ebcd0b6d34348
Assignee: nobody → jmcf
Status: NEW → ASSIGNED
This is not a reduced regression window - the window above is spanning two days. Please get this window reduced.
(In reply to Jason Smith [:jsmith] from comment #4) > This is not a reduced regression window - the window above is spanning two > days. Please get this window reduced. In B2G-Inbound there are no builds available between the last build on 5-17 and the first build on 5-19. No builds were produced on 5-18. Instead I've redone the window in Mozilla Inbound which has more builds available in this date range and resulted in a date-range of only a few hours separation. Mozilla-Inbound Regression Window: Last Working: Environmental Variables: Device: Open_C BuildID: 20140519073022 Gaia: 101c500903a2477f9de1ea5ce523b9e0be4d45d0 Gecko: 26b869be49cc Version: 32.0a1 Firmware Version: P821A10V1.0.0B06_LOG_DL First Broken: Environmental Variables: Device: Open_C BuildID: 20140519163003 Gaia: 8a2352d5b7be27ec4b1ea18c680ebcd0b6d34348 Gecko: 74f812525f7d Version: 32.0a1 Firmware Version: P821A10V1.0.0B06_LOG_DL Gaia pushlog: https://github.com/mozilla-b2g/gaia/compare/101c500903a2477f9de1ea5ce523b9e0be4d45d0...8a2352d5b7be27ec4b1ea18c680ebcd0b6d34348
blocking-b2g: 2.0? → 2.0+
In the latest master I cannot reproduce it. Probably these are problems related to the Open C builds you are using. Please check.
Assignee: jmcf → nobody
Status: ASSIGNED → NEW
Attached video VID_0002.3gp
The issue doesn't occur on today's (5/22) master build under the following scenario, please see the video attached: Device: Hamachi BuildId: 20140522070059 Gecko: 564e4e1 Gaia: a436da1 Platform version: 32.0a1
(In reply to Jose Manuel Cantera from comment #6) > In the latest master I cannot reproduce it. Probably these are problems > related to the Open C builds you are using. Please check. I think that's not right. Open C are hidpi based, where as Buri is not. You need to check this on a hidpi-based device.
The patches on bug 1010749 & bug 1010782 could be the cause here. Both of them are changing build logic with comms, which would explain the issue we are seeing here. I think I need clarification on how Jose is building to test here, as we need to make sure this was tested using a production build configuration.
Flags: needinfo?(jmcf)
I've checked it on Open_C trunk (regular, non-eng build that we use for manual smoketests) and the issue no longer repros - able to link local contact to a Facebook imported one. Open_C master m-c BuildID: 20140522040230 Gaia: ef66efa34ed8a559c8998bde688fae88eb943a7a Gecko: b40296602083 Version: 32.0a1 P821A10V1.0.0B06_LOG_DL
WFM?
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → WORKSFORME
Flags: needinfo?(jmcf)
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: