Closed
Bug 1110119
Opened 10 years ago
Closed 9 years ago
When updating via OTA/FOTA, already installed third party apps are installed again
Categories
(Core Graveyard :: DOM: Apps, defect)
Tracking
(blocking-b2g:2.0+, firefox35 wontfix, firefox36 wontfix, firefox37 fixed, b2g-v2.0 fixed, b2g-v2.0M fixed, b2g-v2.1 fixed, b2g-v2.2 fixed)
People
(Reporter: amac, Assigned: amac, NeedInfo)
References
Details
(Keywords: verifyme)
Attachments
(4 files)
5.80 KB,
patch
|
fabrice
:
review+
bajaj
:
approval-mozilla-b2g32+
bajaj
:
approval-mozilla-b2g34+
|
Details | Diff | Splinter Review |
5.74 KB,
patch
|
Details | Diff | Splinter Review | |
8.18 MB,
video/mp4
|
Details | |
6.44 MB,
video/mp4
|
Details |
STR: * Install FirefoxOS 1.3 on a device. The build must include some preinstalled third party apps that doesn't have a custom origin. It doesn't really matter if the app is hosted or packaged. * Update to 2.x via OTA/FOTA. The new build must include preinstalled some of the same third party apps. EXPECTED * The apps already preinstalled by 1.3 are kept, and no changes are done to them. ACTUAL * The preinstalled apps shared between the 1.3 and 2.0 builds are duplicated. The apps don't show on the homescreen, but anytime there's an update the update will be offered twice, and on the App Manager will show the app twice also. Uninstalling the app will remove the icon from the homescreen, but it'll reappear after the phone is rebooted (since only one of the copies was actually uninstalled). The problem is that until 1.3 (or 1.4, I have the details slightly fuzzy by now) the build system kept the directory names that the preinstalled third party apps had on the local filesystem. So if I installed a third party app that was on the build tree on a directory called 'mythirdpartyapp' it would be copied into the device as app://mythirdpartyapp. From 2.0 onwards, all the non privileged third party apps, and privileged ones that don't specify an origin are given a uuid identifier and copied as app://{uuid-here}. Since the app id will then change between 1.3 and 2.0, the update process thinks it's a new application, and so installs it. What we should do at first boot time is check by manifestURL instead (so if an app that has the same manifestURL than the currently being processed one exists, we don't install it again).
Comment 1•10 years ago
|
||
[Blocking Requested - why for this release]: This is a very urgent issue blocking us on the OTA process for 2.0 release.
blocking-b2g: --- → 2.0?
Assignee | ||
Comment 2•10 years ago
|
||
This is quite straightforward. I have the patch ready for 2.0 also (actually I wrote it for 2.0 and then downlifted it :)).
Attachment #8535024 -
Flags: review?(fabrice)
Assignee | ||
Comment 3•10 years ago
|
||
Assignee | ||
Updated•10 years ago
|
Attachment #8535024 -
Attachment is patch: true
Comment 4•10 years ago
|
||
This appears to be a very similar to bug 979175. Also, this was fixed in bug 1073335.
Assignee | ||
Comment 5•10 years ago
|
||
Yep, it's the same. And nope, it wasn't fixed in bug 1073335 (are you sure you got the right bug number? that does seem to be related with formatting the internal storage, not initial app installation). In fact it doesn't seem to be fixed...
Assignee | ||
Updated•10 years ago
|
Assignee: nobody → amac.bug
Comment 7•10 years ago
|
||
Comment on attachment 8535024 [details] [diff] [review] V1. Keep track of preinstalled apps by manifestURL Review of attachment 8535024 [details] [diff] [review]: ----------------------------------------------------------------- Right. that would really be nice to have tests around this...
Attachment #8535024 -
Flags: review?(fabrice) → review+
Assignee | ||
Comment 8•10 years ago
|
||
Actually I opened a bug to implement the installation at boot tests some time ago. I haven't had any time for it though. Yet. I hope :)
Keywords: checkin-needed
Assignee | ||
Comment 9•10 years ago
|
||
Comment on attachment 8535024 [details] [diff] [review] V1. Keep track of preinstalled apps by manifestURL NOTE: Please see https://wiki.mozilla.org/Release_Management/B2G_Landing to better understand the B2G approval process and landings. [Approval Request Comment] Bug caused by (feature/regressing bug #): User impact if declined: during the OTA some apps will be duplicated. This is also a certification blocker. Testing completed: manually by the developer and the OEM. Risk to taking this patch (and alternatives if risky): pretty low String or UUID changes made by this patch:none
Attachment #8535024 -
Flags: approval-mozilla-b2g34?
Attachment #8535024 -
Flags: approval-mozilla-b2g32?
Assignee | ||
Comment 11•10 years ago
|
||
There you go: https://treeherder.mozilla.org/ui/#/jobs?repo=try&revision=882abced600a Tests should/will be done (some time...) in bug 1016889. Currently there are no tests for the initial load of apps at all, nor it would be easy nor quick to write them now. So... I would love to have tests for this (and Fabrice too, I'm sure) but I don't think it's feasible to have them in this bug (specially not in the time frame we have for the 1.3->2.0 OTAs which this blocks).
Assignee | ||
Comment 12•10 years ago
|
||
Try run is mostly green, re-requesting checkin
Keywords: checkin-needed
Comment 13•10 years ago
|
||
https://hg.mozilla.org/integration/mozilla-inbound/rev/d4640dc77563
Flags: in-testsuite?
Keywords: checkin-needed
Comment 14•10 years ago
|
||
https://hg.mozilla.org/mozilla-central/rev/d4640dc77563
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla37
Updated•10 years ago
|
blocking-b2g: 2.0? → 2.0+
Comment 15•10 years ago
|
||
Comment on attachment 8535024 [details] [diff] [review] V1. Keep track of preinstalled apps by manifestURL :amac, can you please help with manual testing once this lands on branches. The update code really scares me and the lack of tests here given how complex they are demands more manual testing here. I'll also in parallel try to get Mozilla QA to verify if they can
Attachment #8535024 -
Flags: approval-mozilla-b2g34?
Attachment #8535024 -
Flags: approval-mozilla-b2g34+
Attachment #8535024 -
Flags: approval-mozilla-b2g32?
Attachment #8535024 -
Flags: approval-mozilla-b2g32+
Assignee | ||
Comment 16•10 years ago
|
||
Sure thing, we can take care of testing this. Actually, we kinda already did this for the 2.0 branch at least.
Flags: needinfo?(amac.bug) → needinfo?(mbarone976)
Comment 17•10 years ago
|
||
https://hg.mozilla.org/releases/mozilla-b2g34_v2_1/rev/39eaa987093b https://hg.mozilla.org/releases/mozilla-b2g32_v2_0/rev/11f45a1d3bf8
status-b2g-v2.0:
--- → fixed
status-b2g-v2.0M:
--- → affected
status-b2g-v2.1:
--- → fixed
status-b2g-v2.2:
--- → fixed
status-firefox35:
--- → wontfix
status-firefox36:
--- → wontfix
status-firefox37:
--- → fixed
Comment 19•10 years ago
|
||
Hi All, This bug has been successfully verified on Flame v2.0&2.1&2.2 after OTA (Base image:v18D). See attachment: verified_v2.1.MP4. Reproduce rate: 0/2 Flame 2.2 user build Gaia-Rev bdedbaf9f18a43c091ede770407d68d38582fe29 Gecko-Rev https://hg.mozilla.org/mozilla-central/rev/6d5a1e68f248 Build-ID 20141228160203 Version 37.0a1 After OTA: Gaia-Rev 322ef5116a5827a30c9a3cd9b842449a9c66a5b3 Gecko-Rev https://hg.mozilla.org/mozilla-central/rev/2c0ef7315830 Build-ID 20141229160214 Version 37.0a1 ---------------------------------------------------------------------------- Flame 2.1 user build: Gaia-Rev 17c7ad2e4919a994f0844239b483116090412dee Gecko-Rev https://hg.mozilla.org/releases/mozilla-b2g34_v2_1/rev/39dfb662c82a Build-ID 20141222161203 Version 34.0 After OTA: Gaia-Rev 73be51f998031f06db0cd660c0e388fa621c9f4c Gecko-Rev https://hg.mozilla.org/releases/mozilla-b2g34_v2_1/rev/ea426e47bfc4 Build-ID 20141229161203 Version 34.0 ---------------------------------------------------------------------------- Flame 2.0 user build: Gaia-Rev ce83ea7b8e3fa2d1c3fd771fc22b654c18b3c381 Gecko-Rev https://hg.mozilla.org/releases/mozilla-b2g32_v2_0/rev/4dd6d9b58f42 Build-ID 20141222160204 Version 32.0 After OTA: Gaia-Rev 01c32dcdc08b3c8fc8b3082870439fa2c1089f4f Gecko-Rev https://hg.mozilla.org/releases/mozilla-b2g32_v2_0/rev/b4ea79d5c1b2 Build-ID 20141229160215 Version 32.0
Comment 20•10 years ago
|
||
Comment 22•9 years ago
|
||
Hi Sahlly, Please verify again as you need to check the version of 3rd party app still the same. Bug 1125034 is complaining about pre-installed 3rd party app version been downgraded. Thanks.
Updated•9 years ago
|
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Updated•9 years ago
|
Flags: needinfo?(lixia)
Comment 23•9 years ago
|
||
Hi Josh, This bug has been successfully verified on Flame v2.0&2.1&2.2 after OTA (Base image:v18D),and the pre-installed 3rd party app version is the same. See attachment: new_verified_ota_v2.1.MP4. Reproduce rate: 0/4(Flame v2.0),0/2(v2.1),0/2(v2.2). STR: 1.Flash user build. 2.Download some 3rd party apps from Marketplace and note their versions. 3.Install OTA. 4.After OTA,check these 3rd party apps and their versions. **All 3rd party apps show on the homescreen and their versions are the same.(such as "LINE:v1.7.0","Candy Crush:v0.2.1","Loqui IM:v0.4.0") --------------------------------------------------------------- Flame 2.0 user build: Build ID 20150304160234 Gaia Revision 8eaa7ab64bc2c6fa882d6e16766f27ed89c86f34 Gaia Date 2015-03-04 16:10:52 Gecko Revision https://hg.mozilla.org/releases/mozilla-b2g32_v2_0/rev/cec3b489ef2c Gecko Version 32.0 Device Name flame Firmware(Release) 4.4.2 Firmware(Incremental) eng.cltbld.20150304.191831 Firmware Date Wed Mar 4 19:18:40 EST 2015 Bootloader L1TC000118D0 After OTA: Build ID 20150305160227 Gaia Revision 8463d1c9142f32c8ea175048dac52e41620443ce Gaia Date 2015-03-05 16:28:56 Gecko Revision https://hg.mozilla.org/releases/mozilla-b2g32_v2_0/rev/765674521c35 Gecko Version 32.0 ------------------------------------- Flame 2.1 user build: Build ID 20150304161203 Gaia Revision 89db88a76ae8363cd7f8e7a07d35ae24058aec36 Gaia Date 2015-03-04 16:11:03 Gecko Revision https://hg.mozilla.org/releases/mozilla-b2g34_v2_1/rev/b64b3a28d459 Gecko Version 34.0 Device Name flame Firmware(Release) 4.4.2 Firmware(Incremental) eng.cltbld.20150304.194211 Firmware Date Wed Mar 4 19:42:22 EST 2015 Bootloader L1TC000118D0 After OTA: Build ID 20150305161203 Gaia Revision ea97a87048a4c1e2a479bbea1d75e0a182b2c4c9 Gaia Date 2015-03-05 16:30:05 Gecko Revision https://hg.mozilla.org/releases/mozilla-b2g34_v2_1/rev/871071010b5b Gecko Version 34.0 ------------------------------------- Flame 2.2 user build: Build ID 20150304162536 Gaia Revision 89af288bad6751248ff84504fa898206fee127fe Gaia Date 2015-03-04 18:00:05 Gecko Revision https://hg.mozilla.org/releases/mozilla-b2g37_v2_2/rev/c7737301ad14 Gecko Version 37.0 Device Name flame Firmware(Release) 4.4.2 Firmware(Incremental) eng.cltbld.20150304.195555 Firmware Date Wed Mar 4 19:56:06 EST 2015 Bootloader L1TC000118D0 After OTA: Build ID 20150305162505 Gaia Revision eb86137e247224e86d17ed1a0a133b2a318dce3c Gaia Date 2015-03-05 16:51:07 Gecko Revision https://hg.mozilla.org/releases/mozilla-b2g37_v2_2/rev/e9d29a3b94e5 Gecko Version 37.0 ---------------------------------------------------------------- I can't do FOTA in our side,leaving "verifyme".
Flags: needinfo?(lixia)
Comment 24•9 years ago
|
||
Comment 25•9 years ago
|
||
(In reply to Shally from comment #23) > Hi Josh, > > This bug has been successfully verified on Flame v2.0&2.1&2.2 after OTA > (Base image:v18D),and the pre-installed 3rd party app version is the same. > See attachment: new_verified_ota_v2.1.MP4. > Reproduce rate: 0/4(Flame v2.0),0/2(v2.1),0/2(v2.2). > > STR: > 1.Flash user build. > 2.Download some 3rd party apps from Marketplace and note their versions. > 3.Install OTA. > 4.After OTA,check these 3rd party apps and their versions. > **All 3rd party apps show on the homescreen and their versions are the > same.(such as "LINE:v1.7.0","Candy Crush:v0.2.1","Loqui IM:v0.4.0") > I do not think above steps are correct to reproduce the issue reported in this bug and described in comment 0: >The build must include some preinstalled third party apps that doesn't have a custom origin. It doesn't >really matter if the app is hosted or packaged. The issue here is about how preinstalled apps are modified after the OTA process. Apps downloaded from Marketplace are a different scenario. Shally, if you need more information about the scenario, lets ask the reporter in bug 125034.
Flags: needinfo?(lixia)
Comment 26•9 years ago
|
||
Hi Reporter, Per Comment 25, could you help to confirm the "preinstalled apps" in Comment 0? Thank you very much.
Flags: needinfo?(lixia) → needinfo?(ecmel)
Comment 27•9 years ago
|
||
mm I think you wanted to ask some body else. Please reporter help Mozilla to check the issue by describing the scenario for testing.
Flags: needinfo?(liuyongming)
Comment 28•9 years ago
|
||
(In reply to Shally from comment #26) > Hi Reporter, > > Per Comment 25, could you help to confirm the "preinstalled apps" in > Comment 0? > > Thank you very much. Hi, 'preinstalled' apps are but not limited to 'Firefox Hello', 'Latch', 'Pinterest'. Actually the issue can be reproduced with any 'preinstalled' app with a newer version of it in marketplace and user manually update it before FOTA. Please refer to https://bugzilla.mozilla.org/show_bug.cgi?id=1125034#c10 for more details. Thanks.
Flags: needinfo?(liuyongming)
Comment 29•9 years ago
|
||
Dear Wesly: It's urgent issue for TEF FireE2.0 SW. Please help to fix it asap. Thanks.
Updated•9 years ago
|
QA Whiteboard: [MGSEI-Triage+]
Comment 30•9 years ago
|
||
Started from comment#21 we were actually talking about 1125034, which was set to dup this one. However after discussion with EPM we think they might be related but not the same, hence here I would like to separate these 2 again to avoid further mix/confusion. (there was some in comment#23~#27 already) This one will be set to previous status (fixed), and let 1125034 handle what it need to do. Thanks.
Status: REOPENED → RESOLVED
Closed: 10 years ago → 9 years ago
Resolution: --- → FIXED
Updated•9 years ago
|
Flags: needinfo?(mbarone976)
Updated•7 years ago
|
Product: Core → Core Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•