[Affected versions]:

• Firefox Unbranded 72.0.2 - Build ID: 20200109172031
• Firefox Nightly 73.0a1 - Build ID: 20191231213920
• Firefox Nightly 74.0a1 - Build ID: 20200112214546

[Affected Platforms]:

• Windows 10 x64
• Mac 10.15.2
• Ubuntu 18.04 x64

[Prerequisites]:

• Have a new Firefox profile.
• Have the following prefs in the “about:config” page:
  • user_pref("security.content.signature.root_hash",
    "DB:74:CE:58:E4:F9:D0:9E:E0:42:36:BE:6C:C5:C4:F6:6A:E7:74
    :7D:C0:21:42:7A:03:BC:2F:57:0C:8B:9B:90");
  • user_pref("app.normandy.api_url", "https://stage.normandy.nonprod.cloudops.mozgcp.net/api/v1");
  • user_pref("app.normandy.dev_mode", true);
  • user_pref("app.normandy.logging.level", 0);
  • user_pref("services.settings.server", "https://settings.stage.mozaws.net/v1");
  • user_pref("ppop-MSP", true);
  • user_pref("xpinstall.signatures.dev-root", true);

[Steps to reproduce]:

1. Open the browser with the profile from prerequisites.
2. Open the “Browser Console” (Ctrl+Shift+J).
3. Click the “Console Settings” button from the upper right corner of the web console and select “Show Content Messages” option.
4. Restart browser and observe the “Browser Console”.

[Expected result]:

• The user is correctly enrolled in the study.

[Actual result]:

• The user is enrolled in the study but is unenrolled after a few seconds due to a “CAUGHT_ERROR” reason.
  Cannot send function call result: other side closed connection (call data: ({path:"normandyAddonStudy.endStudy", args:["CAUGHT_ERROR"]}))

[Notes]:

• This issue is not reproducible on the "control" branch of the experiment.
• The unenrollment ping is also displayed in the “about:telemetry” page under the “Events” section.

@Robert, could you include the full error messages that preceded the unenrollment? Especially the error message with "Invalid telemetry payload" that includes an Object with "validationResult". We need to see that to understand what validation error was encountered.

(The study add-on is designed to unenrollment on unexpected errors, and in this case the gif shows "Error: Invalid telemetry payload". Keeping users enrolled that send invalid telemetry could compromise the validity of the study results.)

Hey @fwollsen. You can find the error in the attached file named "Invalid Telemetry payload".

You can also find the console output here.

:vng - could you take a look at this, please?

This due to : https://github.com/mozilla/messaging-system-personalization-experiment-1-addon/issues/21

I'm working on it.

[Tracking Requested - why for this release]:

Looks like this is a bug in the experiment addon, not tracking for 72.

Marking this issue as verified as the fix in this case was to no longer launch the experiment. See QA-438 for more info.