1097602 - Unable to access Marketplace account details

Status: RESOLVED DUPLICATE of bug 1095709

(Firefox OS Graveyard :: Runtime, defect)

Description

[:gerard-majax]

Happened on my dogfooding Nexus S.

STR:
 0. Have a Firefox Accounts already configured on the device for Find My Device. In Settings -> Firefox Accounts, it says Marketplace is connected (it has always been like this). Account is "email+a@domain".
 1. Have a Marketplace account connected via Persona, "email+b@domain".
 2. Fire Marketplace app, it proposes to perform the migration to Firefox Accounts
 3. Accept, a form comes and proposes to create a new Firefox Accounts with "email+b@domain"
 4. Try to access your account details on Marketplace

Expected:
 I can access my account details.

Actual:
 Tappig on the wheel does nothing, except reloading the page.

Comment 1

[:gerard-majax]

Reproduces after rebooting the device also.

Comment 2

[Stuart Colville [:muffinresearch]]

Hi, would you be able to provide logs via 'adb logcat'. (Please remove any confidential content before attaching).

Could you also provide details of the build you're running?

Comment 3

[:gerard-majax]

(In reply to Stuart Colville [:scolville] [:muffinresearch] from comment #2)
> Hi, would you be able to provide logs via 'adb logcat'. (Please remove any
> confidential content before attaching).
> 
> Could you also provide details of the build you're running?

Master of now.

Comment 4

[:gerard-majax]

Attachment: marketplace.log

Comment 5

[Stuart Colville [:muffinresearch]]

This appears to be the only error:

11-12 13:30:51.547  1002  1002 W Marketplace: [JavaScript Error: "Error: TCPSocket does not have permission in this context.
11-12 13:30:51.547  1002  1002 W Marketplace: " {file: "jar:file:///system/b2g/omni.ja!/components/TCPSocket.js" line: 567}]

Comment 6

[Stuart Colville [:muffinresearch]]

Sounds like clicks on the "Settings" icon aren't firing - there's nothing in the logs to indicate navigation to /settings being initiated.

Comment 7

[:gerard-majax]

Reproducing on Xperia ZR running master, where I have no account used on Marketplace: I cannot access the account details.

Comment 8

[Stuart Colville [:muffinresearch]]

Interested to see if running non-master can reproduce? I can't repro on Flame with 2.1.

Comment 9

[Stuart Colville [:muffinresearch]]

Looks unrelated to FXA.

Comment 10

[:gerard-majax]

So:
 - Desire Z with a master build from november 9th => ok
 - Desire Z with a master build from november 12th => not ok

Comment 11

[Mark Striemer [:mstriemer]]

Attachment: settings-gear.mp4

I notice something similar on my Nexus 5 in Nightly. Tapping the gear icon selects Home instead. When I tap the Marketplace logo once I finally make it to settings then it selects the search bar.

Comment 12

[Mark Striemer [:mstriemer]]

My Nexus 5 in running Android KitKat, btw. Not Firefox OS.

Comment 13

[Stuart Colville [:muffinresearch]]

(In reply to Mark Striemer [:mstriemer] from comment #11)
> Created attachment 8521469 [details]
> settings-gear.mp4
> 
> I notice something similar on my Nexus 5 in Nightly. Tapping the gear icon
> selects Home instead. When I tap the Marketplace logo once I finally make it
> to settings then it selects the search bar.

That looks to be supported by the logs here too. Lots of navigating to / rather than /settings.

Comment 14

[:gerard-majax]

(In reply to Mark Striemer [:mstriemer] from comment #12)
> My Nexus 5 in running Android KitKat, btw. Not Firefox OS.

So this would be a more generic Gecko issue ?

Comment 15

[mac]

I can confirm the issue with 'gear' link that opens Home instead of Settings.

Alcatel One Touch Fire production (got from T-mobile Poland)
B2G version: 2.2.0.0-prerelease master
Platform version: 36.0a1
Build Identifier: 20141113160204 
Git commit info: 2014-11-13 17:43:24 c4f85f88

Comment 16

[Pi Wei Cheng [:piwei] (inactive)]

This looks like a dupe of bug 1095709

Comment 17

[Joshua Mitchell (Inactive)]

I agree with comment 16, same summary, same steps, same results. If anyone disagrees we can re-check this one after bug 1095709 is fixed.