Closed Bug 1515598 Opened 7 years ago Closed 7 years ago

Heartbeat telling me latest version of Firefox ESR (Tor Browser) is "critically out of date"

Categories

(Firefox :: Normandy Client, defect)

60 Branch
defect
Not set
normal

Tracking

()

RESOLVED INVALID

People

(Reporter: north.korea, Unassigned)

Details

User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.14; rv:64.0) Gecko/20100101 Firefox/64.0 Steps to reproduce: Nothing, presumably Heartbeat (https://support.mozilla.org/en-US/kb/rate-your-firefox-experience-heartbeat) was enabled through random sampling Actual results: It told me that Firefox (60.4.0esr)/Tor Browser (8.0.4) was "critically out of date" Expected results: Nothing
(The Tor Browser user agent is Mozilla/5.0 (Windows NT 6.1; rv:60.0) Gecko/20100101 Firefox/60.0.)
I am going to assign the "Firefox: Normandy Client" component for it.
Component: Untriaged → Normandy Client
Getting latest Tor version from https://www.torproject.org/dist/torbrowser/8.0.4/torbrowser-install-win64-8.0.4_en-US.exe, would list the version as 60.4.0esr and the Update channel as release. AFAIK, Normandy on Tor shouldn't work, since unified telemetry is dissabled. (toolkit.telemetry.enabled -false and locked). Presuming that unified telemetry was somehow enabled for Tor browser, hence the Normandy enabled, that means that the OutofDate notification you have seen is correct to be displayed (from a Firefox point of view). However, since it is displayed on Tor, this obviously is bad :), but I guess that this issue should be reported on Tor side, since it is not a Firefox issue.
Status: UNCONFIRMED → RESOLVED
Closed: 7 years ago
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.