https://bugs.kde.org/show_bug.cgi?id=504040

--- Comment #1 from jshand2...@gmail.com ---
Product: Akonadi
Component: Resources
Version: (select the correct version, or “git” for latest)
Platform: openSUSE Tumbleweed (or your distribution)
OS: Linux

Title:
Duplicate Google Account Resource Initialization Occurs in Production

Description:
In both test and production environments, Akonadi appears to initialize a
googleContactsResource without checking for existing instances. This leads to
the unintended creation of duplicate Google account resources when using
Akonadi with Google integration.

Steps to Reproduce:
Set up Akonadi with Google integration.

Add a Google account for calendar or contacts.

Observe Akonadi behavior after restart or during syncs.

Note that duplicate resources or accounts may be created, even if one already
exists.

Actual Result:
Multiple googleContactsResource instances are created. There is no apparent
check to prevent duplication, which leads to redundant account listings,
duplicated contact syncing, and sync conflicts in some cases.

Example from source file akonadi/autotests/akonadifakedata.cpp:

cpp
Copy
Edit
AgentType googleContactsResource;
googleContactsResource.exec =
QStringLiteral("akonadi_googlecontacts_resource");
googleContactsResource.mimeTypes = QStringList() <<
QStringLiteral("application/x-vnd.akonadi.contact");
googleContactsResource.capabilities = QStringList() <<
QStringLiteral("Resource") << QStringLiteral("Autostart");
This pattern appears unguarded in both test and runtime behaviors.

Expected Result:
Akonadi should detect and reuse an existing Google account/resource.

Duplicate instances should be prevented unless explicitly requested.

Production behavior should avoid duplicate syncing and redundant entries.

Version Info:
Akonadi Source: Git master (or specify version/commit)

Distribution: openSUSE Tumbleweed (or your OS)

Behavior Confirmed: In both test and production environments

Compiler: GCC or Clang (if applicable)

Impact:
User confusion from multiple Google entries.

Redundant data syncing.

Potential for calendar/contact duplication.

Unstable or inefficient Google integration.

-- 
You are receiving this mail because:
You are watching all bug changes.

Reply via email to