Closed
Bug 1117831
Opened 9 years ago
Closed 8 years ago
QA to verify single locale updates
Categories
(Firefox for Android Graveyard :: Locale switching and selection, defect)
Firefox for Android Graveyard
Locale switching and selection
ARM
Android
Tracking
(Not tracked)
RESOLVED
WONTFIX
People
(Reporter: kmoir, Unassigned)
References
Details
Single locale updates have been enabled for Android in bug 1019724. I'd like someone from QA to verify them so we can move forward and close this bug. I cc'ed kbrosnan on the bug but perhaps another person is responsible for this area so this is why I opened a specific Firefox for Android bug.
Updated•9 years ago
|
Flags: needinfo?(aaron.train)
OS: Mac OS X → Android
Hardware: x86 → ARM
Reporter | ||
Comment 2•9 years ago
|
||
Okay who in QA would be qualified to verify them? I have been asking but everyone says they don't know anything about it, or is not qualified to verify them.
Comment 3•9 years ago
|
||
Anyone should be able to verify this. 1. Install a single-locale build from FTP. 2. Wait for an update to be available. 3. Install the update. 4. Verify that the app is still in the right locale.
Comment 4•9 years ago
|
||
As far as I know this is blocked on bug 792992.
Comment 5•9 years ago
|
||
That is correct. bug 1019724 comment 137 uses custom update channels for this, bug 792992 is an old bug about Firefox for Android not supporting app.update.url.override. It looks like there is some traction there. Else we would need to test this on the live beta channel. Risk to existing users is minimal assuming that the -multi build is excluded.
Reporter | ||
Comment 6•9 years ago
|
||
kbrosnan: thanks for the update, glad there is traction in bug 792992. Yes the multi build is excluded in the balrog channel for these updates.
Reporter | ||
Comment 7•9 years ago
|
||
So bug 792992 has been fixed, could QA revisit testing this on beta?
Comment 8•9 years ago
|
||
I am not having any luck with getting the updates. Used build http://ftp.mozilla.org/pub/mozilla.org/mobile/releases/37.0b4/android-api-11/en-US/fennec-37.0b4.en-US.android-arm.apk channels: beta-localtest or beta-cdntest Tried setting several settings in about:config - app.update.channel set to either string does not work - app.update.url.android replacing %CHANNEL% with either string did not work - app.update.url.override with the app.update.url.android modified string did not work To check for updates I visited about:firefox and tapped the check for updates button. Clarification on the exact preference to use and its value is needed to progress.
Reporter | ||
Comment 9•9 years ago
|
||
bhearsum: If I look at https://aus4-admin.mozilla.org/rules#fennec%20beta It looks like the rules are defined correctly to point to https://aus4-admin.mozilla.org/releases#Fennec-37.0b4 for android-api-11 Am I missing something?
Flags: needinfo?(bhearsum)
Comment 10•9 years ago
|
||
(In reply to Kim Moir [:kmoir] from comment #9) > bhearsum: > > If I look at > https://aus4-admin.mozilla.org/rules#fennec%20beta > > It looks like the rules are defined correctly to point to > https://aus4-admin.mozilla.org/releases#Fennec-37.0b4 > > for android-api-11 > > Am I missing something? URLs like https://aus4.mozilla.org/update/4/Fennec/32.0/20140728123855/Android_arm-eabi-gcc3/eo/beta-localtest/4.4.2/default/default/32.0/update.xml are returning an update. Is there some way to dump out what actual android builds are using for their update URL? It's almost impossible to debug without knowing the URL they're using.
Flags: needinfo?(bhearsum)
Reporter | ||
Comment 11•9 years ago
|
||
I think you need to manually enter an update url and that is what QA was doing. kbrosnan: Can you post the actual urls you tried?
Flags: needinfo?(kbrosnan)
Comment 12•9 years ago
|
||
(In reply to Kim Moir [:kmoir] from comment #11) > I think you need to manually enter an update url and that is what QA was > doing. > > kbrosnan: Can you post the actual urls you tried? I wouldn't recommend overriding the URL completely, otherwise you don't end up testing the %PRODUCT% and other substitutions that happen in the wild. Typically, we override channel when testing. Sometimes we set app.update.url.override to change the update server, but leave the substitutions. In any case, seeing the actual testing URLs will help here.
Reporter | ||
Comment 13•8 years ago
|
||
I don't think this bug is relevant anymore
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → WONTFIX
Updated•7 years ago
|
Flags: needinfo?(kbrosnan)
Updated•3 years ago
|
Product: Firefox for Android → Firefox for Android Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•