Fenix v149 manifest: gecko-nimbus-validation.test-preference has both gecko-pref and default (now mutually exclusive)
Categories
(Firefox :: Nimbus Desktop Client, defect)
Tracking
()
People
(Reporter: jlockhart, Unassigned)
References
(Regression)
Details
(Keywords: regression)
Attachments
(1 file)
The Fenix v149.0.0 manifest defines gecko-nimbus-validation.test-preference with both default: '' and gecko-pref:
gecko-nimbus-validation:
description: Feature for validating Nimbus Gecko functionality
variables:
test-preference:
description: A test gecko preference
type: String
default: ''
gecko-pref:
pref: gecko.nimbus.test
branch: default
As of application-services build 150.20260321050323 (March 21, 2026), the FML now enforces that gecko-pref and default are mutually exclusive on feature variables (bug 2020683). When gecko-pref is set, the default comes from the Gecko preference system, so specifying default in the manifest is ambiguous.
This causes FmlClient to raise a ValidationError when parsing the v149.0.0 Fenix manifests, which currently crashes Experimenter with a 500 error when validating experiments targeting Fenix v149.
The fix is to remove default: '' from the test-preference variable definition in the Fenix manifest (mobile/android/fenix/app/nimbus.fml.yaml), since the default is provided by the gecko.nimbus.test preference.
This was found via the failing CI on https://github.com/mozilla/experimenter/pull/15002 (application-services version bump).
|
||
Comment 1•2 months ago
|
||
This was fixed as an uplift in bug 2012763
|
|
||
Comment 2•2 months ago
|
||
Well it turns out we need a temporary fix in A-S to allow us to ingest manifests until the uplift lands.
|
||
Comment 3•2 months ago
|
||
|
|
||
Comment 4•2 months ago
|
||
Authored by https://github.com/freshstrangemusic
https://github.com/mozilla/application-services/commit/ee2512db357747c2aefaa05ededde558003815c6
[main] Bug 2025587 - Re-allow simultaneous gecko-pref and default (#7291)
Description
•