Bug 325037 - Does not sync Google contacts from Google Apps domain
Summary: Does not sync Google contacts from Google Apps domain
Status: RESOLVED UNMAINTAINED
Alias: None
Product: Akonadi
Classification: Frameworks and Libraries
Component: GoogleData Resource (show other bugs)
Version: unspecified
Platform: Debian unstable Linux
: NOR normal
Target Milestone: ---
Assignee: Adenilson Cavalcanti
URL: http://bugs.debian.org/cgi-bin/bugrep...
Keywords:
Depends on:
Blocks:
 
Reported: 2013-09-18 08:15 UTC by Johannes Rohr
Modified: 2013-09-18 09:42 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Johannes Rohr 2013-09-18 08:15:56 UTC
I have two Google Contacts sources configured. One is from a regular GMail account and here, addressbook syncing works just fine. The other is from a 
GApps account (which also implies that the E-Mail address is not something@gmail.com. Here, the KDE addressbook remains empty, although there are 
several hundred addresses in this account.

Calendar sycning with this account works, though.

Reproducible: Always

Steps to Reproduce:
1. Set up Google contact resource for an account on a Google Apps domain and one for a regular GMail account
2. Open the address book
3. Watch what happens
Actual Results:  
Regular GMail contact resource is populated with entries, the GApps address book remains empty.

Expected Results:  
Both should behave the same.
Comment 1 Daniel Vrátil 2013-09-18 09:17:23 UTC
Are you really using the GData resource, or the new Google resources that are shipped with KDE 4.11 by default?

In the latter case, do you see the "my@email.xyz" root addressbook in KAdressbook with several subfolders?
Comment 2 Daniel Vrátil 2013-09-18 09:42:36 UTC
I assume this is the same case - please use the "Google Contacts" resource shipped with KDE PIM (kdepim-runtime) by default since KDE 4.10 (if available).

The GData resource is not maintained anymore (see bug 325040).