928520 - E.me search is failing to return results, even though a connection is established

Status: RESOLVED WORKSFORME

(Firefox OS Graveyard :: Gaia::Everything.me, defect)

Description

[Jason Smith [:jsmith]]

Migration of Teodosia's bug seen in bug 908381.

Prerequisites: 
Connect to wi-fi.

Steps to reproduce:
1. Restart b2g.
2. Tap the search field for e.me app in the homescreen.
3. Search for something ("twitter").
4. Wait for the results.

Expected:
The results are displayed.

Actual:
Most of the time the loading spinner is displayed and never stops loading and the results are never shown.

This is failing in our automated tests.
We use a 30 sec wait there and it's timing out often.

Build information: 
Gecko  http://hg.mozilla.org/releases/mozilla-aurora/rev/7ca5d1e81d37
Gaia  dbcc171eae6b4d9d168a48291d5ea54c7580561a
BuildID 20131017004001
Version 26.0a2

I'm seeing this as well on a Leo 1.2 10/18/2013 build.

Comment 1

[Jason Smith [:jsmith]]

This is a strange bug. I can reproduce on Leo, Teodosia can reproduce this Inari, John can't reproduce this on Helix. Can someone try to reproduce this on a Leo build?

Comment 2

[gbennett]

Unable to repro issue using Wifi (WPA, WPA2, WEP) and AT&T sim 2G. Tried searching twitter, facebook, and random letters and numbers, all which returned results in a timely manner.

Environmental Variables:
Device: Leo 1.1 mozRIL
BuildID: 20131016041201
Gaia: 680f3b86b1e4ff1411ece6ba397b8b0e56b4b31c
Gecko: 3cbd02abb840
Version: 18.0

Comment 3

[Jason Smith [:jsmith]]

Turns out for me I screwed up my build configuration which caused this.