Closed Bug 1146126 Opened 9 years ago Closed 9 years ago

[collections] Can't add smart collections to homescreen, device says there is no internet connection

Categories

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

ARM
Gonk (Firefox OS)
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED DUPLICATE of bug 1144557

People

(Reporter: aryx, Unassigned)

Details

B2G 3.0 20150320015602 on Keon

Long tapping the home screen and tapping the menu option to add smart collections tells me there is no internet connection, but I can access the Internet e.g. from the browser. This works as expected with the latest B2G 2.2 on the Flame.
Naoki, can you reproduce?
Flags: needinfo?(nhirata.bugzilla)
Keywords: qawanted
No I can't reproduce on today's Keon build.  Note, there's some issues with the keon build and their flash script.  I had to manually type in to flash in fastboot.

Looking at the description, it sounds like the server wasn't reachable.  At least that's one possible explanation.

Aryx, can you see if you're still experiencing this issue?
Flags: needinfo?(nhirata.bugzilla) → needinfo?(archaeopteryx)
Note: it might be because I'm pulling up WWE and he might be getting another content due to geo location difference.

If you are still getting blank, I think what we need is the gaia debug turned on and the console logging turned on in the developer options and a logcat to help see how/why you're getting the issue.
I can still reproduce the issue (latest Keon nightly is still 20150320). everythingme.api.url is https://api.everything.me/partners/1.0/{resource}/

Remote debugging Main Process, Homescreen, Smart Collections and System didn't show any network requests (Main Process showed only local ones).
Flags: needinfo?(archaeopteryx)
This is a dupe of bug 1144557.
QA Whiteboard: [QAnalyst-Triage?]
Flags: needinfo?(ktucker)
Keywords: qawanted
Status: NEW → RESOLVED
Closed: 9 years ago
QA Whiteboard: [QAnalyst-Triage?] → [QAnalyst-Triage+]
Flags: needinfo?(ktucker)
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.