Firefox builds can no longer switch back to the Prod collection after switching to the Nimbus Preview one
Categories
(Firefox for Android :: Experimentation and Telemetry, defect)
Tracking
()
People
(Reporter: cmuresan, Assigned: jhugman)
References
Details
Attachments
(2 files)
|
59 bytes,
text/x-github-pull-request
|
Details | Review | |
|
59 bytes,
text/x-github-pull-request
|
RyanVM
:
approval-mozilla-release+
|
Details | Review |
[Affected versions]:
- Firefox Beta 113.0b7 (Build #2015946547), 0cbbf39d7a+, GV: 113.0-20230423180101, AS: 97.4.1
- Firefox Release 112.2.0
- Firefox Release 111.1.1
[Affected Platforms]:
- Android 13 - Samsung Galaxy A32.
- Android 11 - OnePlus 6T
[Prerequisites]:
- Have Nimbus experiments available in Prod preview.
[Steps to reproduce]:
- Open the profile from the prerequisites.
- Tap the Kebab Menu > Settings > About Firefox.
- Tap 5 times on the Firefox logo.
- Tap the Back button.
- Scroll down to the “Secret Settings” option and tap on it.
- Toggle the Nimbus Preview option.
- Fully close and reopen the app.
- Repeat Steps 2 through 4 and navigate to the "Nimbus Experiments" option.
- Tap the option.
- Fully close and reopen the app.
- Repeat Steps 2 through 4 and navigate to the "Nimbus Experiments" option.
- Tap the option.
- Go back and scroll to the “Secret Settings” option and tap on it.
- Toggle the Nimbus Preview option.
- Fully close and reopen the app.
- Repeat Steps 2 through 4 and navigate to the "Nimbus Experiments" option and observe the list of items.
[Expected result]:
- A list of experiments that are available in the regular collection are displayed.
[Actual result]:
- The list of experiments that are available in the Preview collection are displayed.
[Notes]:
- This issue severely impacts QA as we use the Preview collection to test upcoming experiments.
- Attaching a screen recording of the issue here.
Comment 1•3 years ago
|
||
Comment 2•3 years ago
|
||
Authored by https://github.com/jhugman
https://github.com/mozilla-mobile/firefox-android/commit/22d398fe20df0b0d19fa3ca6de196ac74acb311c
[main] Bug 1830080 Add more careful handling of preview-collection in maybeFetchExperiments
Comment 3•3 years ago
|
||
Is this something we need to backport to v113?
| Reporter | ||
Comment 4•3 years ago
|
||
I have verified that the issue is no longer reproducible using a custom Nightly build made from the latest changes available in the main branch (114.0a1 (Build #2015948579), c3dda7c59c+, GV: 114.0a1-20230503214103, AS: 114.20230504050432). I verified that the app can switch back from the Preview collection on the following devices:
- Samsung Galaxy S9 - Android 9
- OnePlus 5 - Android 10
- OnePlus 6T - Android 11
- Samsung Galaxy A23 - Android 12
- Samsung Galaxy A32 - Android 13
@James, if still possible can we get this uplifted to 113? This would help QA with any Android experiments during the Fx 113 cycle.
Comment 5•3 years ago
|
||
| Assignee | ||
Comment 6•3 years ago
|
||
Comment on attachment 9331583 [details] [review]
[mozilla-mobile/firefox-android] Bug 1830080 Add more careful handling of preview-collection in maybeFetchExperiments (backport #1882) (#1902)
Beta/Release Uplift Approval Request
- User impact if declined: This makes it harder for QA to test off-train experiments.
- Is this code covered by automated tests?: Yes
- Has the fix been verified in Nightly?: Yes
- Needs manual test from QE?: No
- If yes, steps to reproduce:
- List of other uplifts needed: None
- Risk to taking this patch: Low
- Why is the change risky/not risky? (and alternatives if risky): The changes have been tested, and this only affects codepaths exercised by QAs.
- String changes made/needed:
- Is Android affected?: Yes
| Assignee | ||
Comment 7•3 years ago
|
||
:cmuresan ^^^ uplifted to v113.
Comment 8•3 years ago
|
||
Comment 9•3 years ago
|
||
Authored by https://github.com/jhugman
https://github.com/mozilla-mobile/firefox-android/commit/d360843eb14ae7b09ab089b5b5bd65f5d8112d64
[releases_v113] Bug 1830080 Add more careful handling of preview-collection in maybeFetchExperiments
| Reporter | ||
Comment 10•3 years ago
|
||
I have verified that the issue is not reproducible with the latest Firefox Release 113.0 build (link). I have used the following devices for verification:
- Samsung Galaxy S9 - Android 9
- OnePlus 5 - Android 10
- Samsung Galaxy A32 - Android 13
Thanks for this fix and uplift @James!
Description
•