Bug 1758645 Comment 0 Edit History

Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.

Original comment by
on 
**[Notes]:**
- We received a workaround for this issue, more exactly we need to enter the `XPCOMUtils.defineLazyPreferenceGetter(ChromeUtils.import("resource://services-settings/Utils.jsm").Utils, "SERVER_URL", "services.settings.server")` code in the "Browser Console" before changing the environment. However, this workaround does not help us in the case of first-run experiments where we need to change the environment before opening the browser.

**[Affected versions]:**
- Firefox Beta 99.0b1 - Build ID: 20220308094525

**[Affected Platforms]:**
- Windows 10 x64
- macOS 11.6.2
- Linux Mint 20.2 x64

**[Steps to reproduce]:**
1. Open a "Command Prompt" window ("Terminal" on macOS and Linux).
2. Enter the `set XPCSHELL_TEST_PROFILE_DIR=foo" variable ("export XPCSHELL_TEST_PROFILE_DIR=foo" on macOS and Linux) and press the "Enter" key.
3. Open the browser from the above "Command Prompt/Terminal".
4. Install the "[Remote Settings Devtools](https://github.com/mozilla-extensions/remote-settings-devtools/releases)" addon.
5. Click the "Remote Settings Devtools" toolbar button.
6. Select the "Stage" option from the "Environment" dropdown placed in the top-right part of the page.
7. Observe the behavior.

**[Expected result]:**
- The "Stage" environment is successfully selected.

**[Actual result]:**
- The "Prod" environment is still selected.

**[Additional Notes]:**
- Attached a screen recording of the issue:
Revision 1 by
on 
**[Notes]:**
- We received a workaround for this issue, more exactly we need to enter the `XPCOMUtils.defineLazyPreferenceGetter(ChromeUtils.import("resource://services-settings/Utils.jsm").Utils, "SERVER_URL", "services.settings.server")` code in the "Browser Console" before changing the environment. However, this workaround does not help us in the case of first-run experiments where we need to change the environment before opening the browser.

**[Affected versions]:**
- Firefox Beta 99.0b1 - Build ID: 20220308094525

**[Affected Platforms]:**
- Windows 10 x64
- macOS 11.6.2
- Linux Mint 20.2 x64

**[Steps to reproduce]:**
1. Open a "Command Prompt" window ("Terminal" on macOS and Linux).
2. Enter the `set XPCSHELL_TEST_PROFILE_DIR=foo" variable ("export XPCSHELL_TEST_PROFILE_DIR=foo" on macOS and Linux) and press the "Enter" key.
3. Open the browser from the above "Command Prompt/Terminal".
4. Install the "[Remote Settings Devtools](https://github.com/mozilla-extensions/remote-settings-devtools/releases)" addon.
5. Click the "Remote Settings Devtools" toolbar button.
6. Select the "Stage" option from the "Environment" dropdown placed in the top-right part of the page.
7. Observe the behavior.

**[Expected result]:**
- The "Stage" environment is successfully selected.

**[Actual result]:**
- The "Prod" environment is still selected.

**[Regression Window]:**
- According to Ed Lee it seems that bug 1272255 has caused this behavior.

**[Additional Notes]:**
- Attached a screen recording of the issue:

Back to Bug 1758645 Comment 0