New error in Nightly 72.0a1 about cookies
Categories
(Core :: Networking: Cookies, defect)
Tracking
()
| Tracking | Status | |
|---|---|---|
| firefox72 | --- | affected |
People
(Reporter: kathleen.a.wilson, Unassigned)
Details
Attachments
(2 files)
Screen Shot 2019-10-22 at 11.38.39 AM.png
Nightly version: 72.0a1 (2019-10-22) (64-bit)
System: MacOS High Sierra (version 10.13.16)
Things were working fine until I updated nightly...
Error:
The page isn’t redirecting properly
An error occurred during a connection to ccadb.my.salesforce.com. {$errorMessage}
Error code:
This problem can sometimes be caused by disabling or refusing to accept cookies.
I've tried not blocking any cookies and turning of tracking protection.
I'll attach some screen shots.
I will switch to Beta for now, but let me know if you need any further info.
|
Reporter | |
Comment 1•6 years ago
|
||
In this screenshot, the left side shows what it looks like in 71.0b3, and the right side shows the error that I'm getting in 72.0a1 even though I have turned of tracking protection and cookie blocking.
|
|
Reporter | |
Comment 2•6 years ago
|
||
This screen shot shows how I turned off cookies. I also tried clearing all of my cookies and site data, but that didn't help either.
|
||
Comment 3•6 years ago
|
||
|
|
Reporter | |
Comment 4•6 years ago
|
||
(In reply to Kershaw Chang [:kershaw] from comment #3)
Could you try to use mozregression to find out which patch causes this issue?
I did the following and then gave up and just created a new Firefox profile which fixed my problem, so I will close this bug as wontfix.
brew install pyqt
brew cask install qt-creator
sudo ln -s /opt/homebrew-cask/Caskroom/qt-creator/3.4.0/Qt\ Creator.app/ /Applications/Qt\ Creator.app
opened up Qt Creator
Wasn't clear what to do from there, so gave up.
In case anyone else runs into similar problems...
I was updating Nightly frequently last week and things were working. Things stopped working as soon as Nightly changed from 71 to 72.
Creating a new profile (and importing my important data from my old profile) has resolved the problem.
Description
•