842669 - contacts are lost after installing an update

Status: RESOLVED WORKSFORME

(Firefox OS Graveyard :: Gaia::Contacts, defect)

Description

[Michelle Luna]

In the last two updates I have noticed the contacts are lost after I update my unagi (the update to Feb 16 build and then today's update from Feb 16 to Feb 19)

0. Import facebook contacts
1. Check for a new update and download & install it on unagi
2. Go into Contacts app
3. Only contacts through the letter E are included, the list only scrolls down to E (31 contacts in my case). This was exctly the same for the previous update, after I updated, only contacts through letter E were preserved.

Expected: to have all of my contacts available after an update, not just A-E.

Comment 1

[Michelle Luna]

I noticed that if I go into the Contact settings screen and select 'Order by Last name' I can see all of my contacts. Then, when I switch back to the default ordering, all of the contacts are available.

Comment 2

[Marcia Knous [:marcia]]

Michelle: Need to know which build you are using in order to investigate this further - are you using the dogfooding builds on the beta channel?

Comment 3

[Michelle Luna]

Hi Marcia,

Yes, I'm dogfooding unagi on the beta update channel. my current build ID is 20130214070203.

Thanks!

Comment 4

[Francisco Jordano [:arcturus] [:francisco]]

Adding qawanted to verify with QA that this is happening.

Comment 5

[Deepa Subramanian]

Issue does not repro anymore. All the contacts were available after an update and not just from A-E.

Unagi Build ID: 20130502070205
Kernel Date: Dec 5
Gecko: http://hg.mozilla.org/releases/mozilla-b2g18/rev/499c3627e89a
Gaia: 495c46489eb256be598a19ea54d7837ce4fc385b

Comment 6

[Dale Harvey (:daleharvey)]

Also on unagi beta channel

Unagi Build ID: 20130426070204

This happened to me last night

Comment 7

[Dale Harvey (:daleharvey)]

And nominating as losing contacts is a pretty major bug

Comment 8

[Daniel Coloma:dcoloma]

Is this happening on 1.0.1 or 1.1?
It would be good to test this with updates for commercial devices as the way in which update is done might affect the contacts.

Comment 9

[Lukas Blakk [:lsblakk] use ?needinfo]

Dale - were you on a 1.0.1 or 1.1 build?
Naoki - are we able to test updates for commercial device builds?

Comment 10

[Dale Harvey (:daleharvey)]

I think I was on v1.0.1, unfortunately was my dogfood device and needed to get it back to working before I could investigate properly

Comment 11

[Daniel Coloma:dcoloma]

Adding jaoo to the loop as he investigated this in the past for Keon devices, I think this might be related to how the udpate is generated.

Comment 12

[Naoki Hirata :nhirata (please use needinfo instead of cc)]

FYI, we switched OTA updates from 1.0.1 to 1.1 sometime around feb... so it's possible that the switch over may have caused some loss of data.

To note, we cannot OTA the commercial ril builds because of legal reasons.
Having said that, I am unsure if the ril would cause any loss of data... that's an unknown.

Anytime the database is updated this may cause a problem.  It's caused us some problems in ffx for android before, if I recall correctly.

Comment 13

[Naoki Hirata :nhirata (please use needinfo instead of cc)]

I may have mistaken something.  dcoloma, is there a way to test the devices to upgrade from one commercial build to another without reflashing?  I am not aware of any method to do this.

Comment 14

[Lukas Blakk [:lsblakk] use ?needinfo]

Comment 1 looks like this is a Gaia bug and not a dataloss issue, more of a display issue.  In either case Fabrice stated in an email thread that "We have schema upgrade code in place for all the chrome data stores like contacts, so upgrading should be fine." from the build/packaging perspective and we do not currently have infrastructure (or legal rights) to do inter-build updates of commercial builds so this cannot be a tef blocker.

Comment 15

[Francisco Jordano [:arcturus] [:francisco]]

(In reply to [e-mail] [:lsblakk] from comment #14)
> Comment 1 looks like this is a Gaia bug and not a dataloss issue, more of a
> display issue.  In either case Fabrice stated in an email thread that "We
> have schema upgrade code in place for all the chrome data stores like
> contacts, so upgrading should be fine." from the build/packaging perspective
> and we do not currently have infrastructure (or legal rights) to do
> inter-build updates of commercial builds so this cannot be a tef blocker.

Can we get a copy of the sqlite files in any of the corrupted examples.

We could try to realise if it's a Gaia issue or a problem with the migration, so far we don't have any log error to verify any of those two suppositions.