Closed Bug 1840594 Opened 3 years ago Closed 3 years ago

[Experiment] A “validationFailed” event is received when trying to enroll in the "Pin to Taskbar/Set to default -Fox Doodle - Early day users" experiments on Firefox 113 version

Categories

(Firefox :: Messaging System, defect)

Firefox 113
Desktop
All
defect

Tracking

()

VERIFIED FIXED

People

(Reporter: cfat, Assigned: jprickett)

References

Details

[Affected versions]:

  • Firefox Release 113.0 - Build ID: 20230504192738

[Affected Platforms]:

  • Windows 10 x64
  • Linux Ubuntu 20.04 x64
  • macOS 12.6.1

[Prerequisites]:

  • Have the times.json and user.js files saved locally.
  • Have the Firefox 113 version installed.
  • Have a Firefox profile created, but not opened.
  • Paste the times.json and user.js files in the Profile Folder.

[Steps to reproduce]:

  1. Open the browser with the profile from the prerequisites.
  2. Navigate to the "about:telemetry” page and observe the events.

[Expected result]:

  • An “enrolled” event specific to the experiment is displayed.

[Actual result]:

  • A “validationFailed” event specific to the experiment is displayed, with the following reason: {"reason": "invalid-feature", "feature": "fxms-message-7"}.

[Notes]:

  • The following error is displayed in the Browser Console:
    Experiment fox-doodle-set-to-default-early-day-graphics has unknown featureId: fxms-message-7 4 RemoteSettingsExperimentLoader.sys.mjs:586:21 _validateBranches resource://nimbus/lib/RemoteSettingsExperimentLoader.sys.mjs:586 checkRecipe resource://nimbus/lib/RemoteSettingsExperimentLoader.sys.mjs:493

  • Here is a video of the issue: link.

This was due to an incorrect feature ID being used. I've reconfigured the experiment recipe and it seems to be working now.

Assignee: nobody → jprickett

We verified this issue and can confirm it's no longer reproducible. We managed to enroll successfully in the experiment using Firefox 113.0 (Build ID: 20230504192738) across OSes (Windows 10 x64, Linux Ubuntu 20.04 x64, and macOS 12.6.1). Considering this, I will mark the issue as Verified Fixed.

Status: NEW → RESOLVED
Closed: 3 years ago
Resolution: --- → FIXED
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.