Closed
Bug 1944604
Opened 11 months ago
Closed 11 months ago
Login error when accessing chatgpt.com
Categories
(Web Compatibility :: Site Reports, defect, P2)
Tracking
(Webcompat Priority:P2, Webcompat Score:6, firefox134 affected, firefox135 unaffected, firefox136 affected)
RESOLVED
WORKSFORME
| Tracking | Status | |
|---|---|---|
| firefox134 | --- | affected |
| firefox135 | --- | unaffected |
| firefox136 | --- | affected |
People
(Reporter: vtamas, Unassigned)
References
()
Details
(Keywords: webcompat:needs-diagnosis, webcompat:site-report, Whiteboard: [webcompat:sightline])
User Story
platform:android impact:workflow-broken configuration:general affects:some branch:release diagnosis-team:webcompat user-impact-score:240
Attachments
(2 files)
ChatGPT.JPEG
Steps to reproduce:
- Navigate to https://chatgpt.com/
- Wait for the page to load.
Expected results
No error occurs.
Actual results
"Oops! We ran into an issue while signing you in, please take a break and try again soon." error is received.
Device information
- Firefox version: Firefox Nightly 136 (2025-01-28), Firefox 134.0.2
- Android device model: Samsung S24 Ultra
- Android OS version: Android 14
Additional notes
This issue was not encountered on Firefox RC 135.
|
||
Comment 1•11 months ago
|
||
This is working fine for me - is this still broken for you?
URL: https://chatgpt.com/
Severity: S2 → S4
User Story: (updated)
Webcompat Priority: --- → P2
Webcompat Score: --- → 6
Flags: needinfo?(vtamas)
Keywords: webcompat:needs-diagnosis,
webcompat:site-report
Priority: -- → P2
|
||
Updated•11 months ago
|
Whiteboard: [webcompat:sightline]
|
Reporter | |
Comment 2•11 months ago
|
||
This bug is no longer reproducible on Firefox Nightly 137 (2025-02-05), Firefox 136 beta 1 and Firefox 135. The error is not displayed and the site is loaded without issues.
I am closing this issue as WFM.
Flags: needinfo?(vtamas)
|
|
Reporter | |
Updated•11 months ago
|
Status: NEW → RESOLVED
Closed: 11 months ago
Resolution: --- → WORKSFORME
You need to log in
before you can comment on or make changes to this bug.
Description
•