Closed Bug 978696 Opened 11 years ago Closed 11 years ago

[Sora][Contacts] The vCard exported from Soul 3.5 FF can not be imported into Android devices.

Categories

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

defect

Tracking

(blocking-b2g:1.3+, b2g-v1.3 fixed, b2g-v1.3T fixed, b2g-v1.4 fixed, b2g-v2.0 verified)

VERIFIED FIXED
1.4 S5 (11apr)
blocking-b2g 1.3+
Tracking Status
b2g-v1.3 --- fixed
b2g-v1.3T --- fixed
b2g-v1.4 --- fixed
b2g-v2.0 --- verified

People

(Reporter: sync-1, Assigned: sergi)

References

()

Details

Attachments

(3 files)

the latest id: Mozilla build ID: 20140208004002 FFOS: 1.3 DEFECT DESCRIPTION: The vCard exported from FFOS can not be imported into Android devices. REPRODUCING PROCEDURES: Precondition: There are several contacts in the list 1. Idle -> Contacts -> Tap "Settings" icon -> Export contacts 2. Put the vCard exported from FFOS into Android devices 3. Try to import the vCard into Android devices -> The vCard exported from FFOS can not be imported into Android devices-> (K.O) EXPECTED BEHAVIOUR: The vCard exported from FFOS can be imported into Android devices. ASSOCIATE SPECIFICATION: TEST PLAN REFERENCE: TOOLS AND PLATFORMS USED: USER IMPACT: REPRODUCING RATE: 100%
Can you provide an example vcard that was exported from FxOS here that cannot be imported in an Android device?
Flags: needinfo?(sync-1)
Created an attachment (id=654142) the vcard file exported from FxOS that cannot be imported in an Android device
Created an attachment (id=654142) the vcard file exported from FxOS that cannot be imported in an Android device
Created an attachment (id=654142) the vcard file exported from FxOS that cannot be imported in an Android device
Francisco - Do you know why Android is failing to import the vcard format generated from FxOS here?
Flags: needinfo?(sync-1) → needinfo?(francisco.jordano)
Hi, This is looking weird. Cannot read it with android 4.4, but can do from iOS and other Mac software (like Outlook and Contacts mac app), also when installing software from the marketplace in android I can read the file as well. I'm starting to think that perhaps is a problem with the aosp implementation. Flaging Sergi that created the parsers to check if he has more insights.
Flags: needinfo?(francisco.jordano) → needinfo?(sergi.mansilla)
(In reply to Francisco Jordano [:arcturus] from comment #7) > Hi, > > This is looking weird. Cannot read it with android 4.4, but can do from iOS > and other Mac software (like Outlook and Contacts mac app), also when > installing software from the marketplace in android I can read the file as > well. May I know which app you install from the Android marketplace to read the file?
Flags: needinfo?(francisco.jordano)
(In reply to 童玮 from comment #8) > (In reply to Francisco Jordano [:arcturus] from comment #7) > > Hi, > > > > This is looking weird. Cannot read it with android 4.4, but can do from iOS > > and other Mac software (like Outlook and Contacts mac app), also when > > installing software from the marketplace in android I can read the file as > > well. > > May I know which app you install from the Android marketplace to read the > file? Hi! I used this one: https://play.google.com/store/apps/details?id=com.wigball.android.vcard.demo Cheers!
Flags: needinfo?(francisco.jordano)
blocking-b2g: --- → 1.3?
I'll try to test that file with the vcf parser and see. Cheers!
Flags: needinfo?(sergi.mansilla)
blocking-b2g: 1.3? → 1.3+
(In reply to Sergi Mansilla from comment #10) > I'll try to test that file with the vcf parser and see. Cheers! Sergi, Any updates on the resolution or an eta here ?
Flags: needinfo?(sergi.mansilla)
Looking into it right now.
Flags: needinfo?(sergi.mansilla)
Assignee: nobody → sergi.mansilla
Attached file 3.vcf
After doing some tests, I believe that Android 4.4 can't import vCard 4.0 format. The test has been done with the attached file, which is the absolute minimal VCF file that could exist, and it still can't parse it (attached). When switching the version to 3.0 there is no problem to import it. Trying with the vCard files in Wikipedia, the same can be observed. vCard 4.0 is not supported in Android...which is crazy if that's the case.
Target Milestone: --- → 1.4 S4 (28mar)
Last week we spoke about making a new issue reflecting the vcard export change from 4.0 to 3.0 and close this one with `WONTFIX`. Should we do that or just continue work in this current issue?
Flags: needinfo?(jcheng)
(In reply to Sergi Mansilla from comment #14) > Last week we spoke about making a new issue reflecting the vcard export > change from 4.0 to 3.0 and close this one with `WONTFIX`. Should we do that > or just continue work in this current issue? I don't think that makes this bug a WONTFIX. Instead, we should use this bug to track switching over to vcard 3.0 to be able to allow exported contacts from Firefox OS to work on Android. How much work is required to implement the 3.0 support? Is it non-trivial & risky?
(In reply to Jason Smith [:jsmith] from comment #15) > (In reply to Sergi Mansilla from comment #14) > > Last week we spoke about making a new issue reflecting the vcard export > > change from 4.0 to 3.0 and close this one with `WONTFIX`. Should we do that > > or just continue work in this current issue? > > I don't think that makes this bug a WONTFIX. Instead, we should use this bug > to track switching over to vcard 3.0 to be able to allow exported contacts > from Firefox OS to work on Android. > > How much work is required to implement the 3.0 support? Is it non-trivial & > risky? I am working on it right now, I am at 70%. It is not hard and not very risky. I will add extra-tests to make sure, though.
agree with comment 15
Flags: needinfo?(jcheng)
Attached file Github Pull Request
This patch changes the export format from vcard 4.0 to 3.0. It changes the least amount of code to make it work properly. Adjusted unit tests and tested import in Android 4.4, works fine but Android doesn't seem to import pictures from vCard, on purpose. Other systems have no problem seeing the pictures (tested on OSX and in-browser data-uris). I will create a new issue for potential fixes to encoding and quoting (not relevant to this issue because if any, they will be present in previous code as well).
Attachment #8397820 - Flags: review?(francisco.jordano)
Comment on attachment 8397820 [details] [review] Github Pull Request Codewise looking good to me. Tried on the phone and working fine, still have that weird feeling about this is going to bite us later, not cause of our code but the different android implementations. Thanks a lot Sergi, merge once travis is green.
Attachment #8397820 - Flags: review?(francisco.jordano) → review+
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
Asking for VERIFYME before asking for the approval to 1.3, so we are sure we uplift safely
Please request approval-gaia-v1.3 on this patch if it's ready for uplift to v1.3.
Target Milestone: 1.4 S4 (28mar) → 1.4 S5 (11apr)
Comment on attachment 8397820 [details] [review] Github Pull Request 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 #): Nor regression, we have been asked to downgrade generation of vcard from 4.0 to 3.0 to be more compatible with androids, since it's the most extended version. [User impact] if declined: No possible interaction of our contacts db with android phones [Testing completed]: asked for verifyme [Risk to taking this patch] (and alternatives if risky): [String changes made]:
Attachment #8397820 - Flags: approval-gaia-v1.3?
Attachment #8397820 - Flags: approval-gaia-v1.3? → approval-gaia-v1.3?(fabrice)
Attachment #8397820 - Flags: approval-gaia-v1.3?(fabrice) → approval-gaia-v1.3?(release-mgmt)
(In reply to Francisco Jordano [:arcturus] from comment #23) > Comment on attachment 8397820 [details] [review] > Github Pull Request > > 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 #): > Nor regression, we have been asked to downgrade generation of vcard from 4.0 > to 3.0 to be more compatible with androids, since it's the most extended > version. > [User impact] if declined: > No possible interaction of our contacts db with android phones > [Testing completed]: > asked for verifyme > [Risk to taking this patch] (and alternatives if risky): > [String changes made]: can you help understand the risk here ? Do we have unit/integration or automation coverage in this area ? Refer to guidelines : https://wiki.mozilla.org/Release_Management/Uplift_rules#Guidelines_on_approval_comments to see what we are looking for. Thanks !
Flags: needinfo?(francisco.jordano)
We do have unit tests for this change passing, also flagged as VERIFYME to land it more confident.
Flags: needinfo?(francisco.jordano)
(In reply to Francisco Jordano [:arcturus] from comment #25) > We do have unit tests for this change passing, also flagged as VERIFYME to > land it more confident. thanks! I'll wait to approve on 1.3 till we get verification,How about the risk here ?
Not pretty risky since the downgrade is basically text formatting pretty similar and basically turning lots of strings to upper case.
Creating a contact on a FFOS device, I used a Buri on the latest v1.5 build. I successfully exported a contact as a vCard to the memory card. Transferring the memory card to the Android device I successfully imported the FFOS created contact. Verified as fixed Master Buri build v1.5: v1.5 4/3 Environmental Variables: Device: Buri 1.5 MOZ RIL BuildID: 20140403040201 Gaia: 0e974ff33ba47f3d1e59df1e0ad534f1bbe3ef8a Gecko: 91be2828f17e Version: 31.0a1 Firmware Version: V1.2-device.cfg - 1) Verified against Master Buri build v1.5, changing status to verified.
Status: RESOLVED → VERIFIED
Keywords: verifyme
Attachment #8397820 - Flags: approval-gaia-v1.3?(release-mgmt) → approval-gaia-v1.3+
Flags: in-moztrap?
Flags: in-moztrap? → in-moztrap+
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: