Closed Bug 1937598 Opened 2 months ago Closed 2 months ago

[Experiment][Android] The “Survey Modal” cannot be triggered using the English locale

Categories

(Fenix :: Experimentation and Telemetry, defect)

All
Android
defect

Tracking

(firefox133 verified)

VERIFIED FIXED
Tracking Status
firefox133 --- verified

People

(Reporter: vbandac, Unassigned)

References

(Blocks 1 open bug)

Details

[Notes]:

  • This issue is caused by the fact that the English locale does not have a specific correlated region in the Experiment targeting.
  • Only the "USER_EN-US_SPEAKER": "locale == 'en-US'" is present in the message targeting, therefore for the other regions the Survey cannot be triggered using the English locale.

[Affected versions]:

  • Firefox Release 133.0.3 (Build #2016060959), hg-7ed49fe90e84+, GV: 133.0.3-20241209150345, AS: 133.0

[Affected Platforms]:

  • Pixel 8 - Android 14.

[Prerequisites]:

  • Have the latest Firefox Release 133.0.3.
  • Have the latest version of nimbus-cli installed.
  • Have the mobile device connected to a computer using adb.
  • Have the English language with any of the regions from the Experimenter page (Belgium, Czechia, France, Germany, Italy, Netherlands, Poland, Romania, Spain, Sweden).

[Steps to reproduce]:

  1. Run the following command in a terminal: ”nimbus-cli --app fenix --channel release enroll preview/android-dma-post-choice-in-product-survey-h2-2024 --branch survey”.
  2. Dismiss the Onboarding tour.
  3. Close the app.
  4. Open again the Firefox app.
  5. Observe the behavior.

[Expected result]:

  • The User Survey is successfully displayed on the screen.

[Actual result]:

  • The User Survey is NOT displayed on the screen.

[Additional Notes]:

  • A screen recording of the issue can be found here.

Please try this again, having edited to "USER_EN_SPEAKER": "'en' in locale" and "USER_EN_SPEAKER" in the trigger

The issue was fixed by updating the targeting message from the recipe. Thank you!

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