Closed Bug 785573 Opened 14 years ago Closed 13 years ago

"Persona requires cookies" error when logging in

Categories

(Core Graveyard :: Identity, defect)

ARM
Gonk (Firefox OS)
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED INCOMPLETE

People

(Reporter: st3fan, Unassigned)

Details

Attachments

(1 file)

Attached image Screenshot —
After clicking the Login/Register button I am redirected to Persona, which shows an 'Persona requires cookies. Please close this window, enable cookies and try again.' error. This is in the Marketplace application. Screenshot attached.
OS: Linux → Android
Hardware: x86_64 → ARM
Component: Web Apps → Consumer Pages
Product: Firefox for Android → Marketplace
QA Contact: aaron.train
Version: Firefox 17 → 1.0
Chris - Any ideas? Is this a marketplace bug?
(In reply to Jason Smith [:jsmith] from comment #1) > Chris - Any ideas? Is this a marketplace bug? I cannot reproduce.
Is this still reproducible?
I have not seen this unless you actually have cookies disabled, I think we should close it unless someone can reproduce it :)
I can reproduce this issue if I have private browsing enabled with accept cookies from sites I visited option. This is in iphone though.
Assuming no other reports, since this bug is B2G-specific, I'm going to mark this this invalid. Please reopen if you see problems.
Status: NEW → RESOLVED
Closed: 14 years ago
Resolution: --- → INVALID
I don't think this is B2G specific. I happened to me on Android. But, I am unable to reproduce it.
Also, this did not happen in private browsing mode. It happened after opening the Marketplace app from the home screen. I don't know how that runs, but I assume it runs a chromeless firefox instance. Maybe sandboxed in its own profile?
(In reply to Ben Adida [:benadida] from comment #6) > Assuming no other reports, since this bug is B2G-specific, I'm going to mark > this this invalid. Please reopen if you see problems. If it's a B2G bug also, then let's move the bug to the correct component (BootToGecko --> General). But I wouldn't mark this as invalid on that basis, though. So what is it then? - B2G bug? - Marketplace bug? - Persona bug?
Status: RESOLVED → REOPENED
Resolution: INVALID → ---
-> B2G then. I don't think there is anything we can do.
Component: Consumer Pages → General
Product: Marketplace → Boot2Gecko
Version: 1.0 → unspecified
blocking-basecamp: --- → ?
Component: General → Identity
Keywords: qawanted
OS: Android → Gonk (Firefox OS)
Product: Boot2Gecko → Core
Keywords: qawanted
(In reply to Wil Clouser [:clouserw] from comment #10) > -> B2G then. I don't think there is anything we can do. Wil and others: has anyone recreated this bug in the last 2-3 weeks? Can you provide STR?
Spoke with John on this one - we're in favor of killing this bug, as it's not being seen anymore on happy path scenarios, and the bug context has just plainly become confusing. If someone so happens to hit this bug again, we'll file a new bug about this with the right details (which identity intends to be heavily tested on b2g, so this will be looked at).
Status: REOPENED → RESOLVED
blocking-basecamp: ? → ---
Closed: 14 years ago → 13 years ago
Resolution: --- → INCOMPLETE
Not sure why this was moved to B2G. I reported this as a Fennec bug.
Product: Core → Core Graveyard
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: