Simplify manifestPlaceholders in build variants
Categories
(Firefox for Android :: General, task, P1)
Tracking
()
| Tracking | Status | |
|---|---|---|
| firefox115 | --- | verified |
People
(Reporter: jonalmeida, Assigned: jonalmeida)
Details
(Whiteboard: [geckoview:m115])
Attachments
(1 file)
We have attributes in the manifestPlaceholders that need to be changed depending on the build variant.
In our current configuration, we re-set the default values in every variant rather than setting on the changes - this is error prone.
We should make this better because we have added more manifestPlaceholders and we will probably add more in the future, so we should limit the chance of making mistakes.
Fenix defaults: https://searchfox.org/mozilla-mobile/rev/a494670a2dc9b9ecd8341e07886b5af1a2f0209a/firefox-android/fenix/app/build.gradle#80-84
Focus defaults: Do not exist. Should be added here.
| Assignee | ||
Updated•2 years ago
|
| Assignee | ||
Updated•2 years ago
|
Comment 1•2 years ago
|
||
| Assignee | ||
Updated•2 years ago
|
Comment 2•2 years ago
|
||
Authored by https://github.com/jonalmeida
https://github.com/mozilla-mobile/firefox-android/commit/f64caf62757cfd137bc48bba9fd133676792997e
[main] Bug 1827905 - Update manifestPlaceholders in variants instead of reinit
Comment 3•2 years ago
|
||
Hello Jonathan,
Is QA verification needed for this issue? If so, could you please provide us with some steps to reproduce (STR) or testing scenarios?
Thank you!
Updated•2 years ago
|
| Assignee | ||
Comment 4•2 years ago
|
||
Hi Adina, sorry, I forgot to add some STR!
This change should ensure that we haven't caused any regressions to our deep links.
STR:
- From the command line with your device connected, run the follow commands:
adb shell am start -W -a android.intent.action.VIEW -d "fenix-nightly://settings"adb shell am start -W -a android.intent.action.VIEW -d "fenix-dev://settings"adb shell am start -W -a android.intent.action.VIEW -d "fenix-beta://settings"adb shell am start -W -a android.intent.action.VIEW -d "fenix://settings"
Expected results:
- At step 2, we should open Fenix Nightly to the Settings page.
- At step 3, we should NOT open Fenix Nightly to the Settings page (if you have another builds installed, those might be opened).
- At step 4, we should NOT open Fenix Nightly to the Settings page (if you have another builds installed, those might be opened).
- At step 5, we should NOT open Fenix Nightly to the Settings page (if you have another builds installed, those might be opened).
Comment 5•2 years ago
|
||
Thank you Jonathan!
Verified as fixed on the latest Nightly version 115.0a1 - 11.05.2023 using Motorola Moto G9 plus (Android 11) device and following the aforementioned steps.
Updated•2 years ago
|
Updated•2 years ago
|
Description
•