Contacts Deletion via Web Interface Not Syncing with CardDAV [385918167]

Assigned

Bug

Status Update

No update yet.

Description

wi...@gmail.com

created issue #1

Dec 26, 2024 11:58AM

Summary

When using Google Calendar CardDAV for syncing with local apps (e.g., macOS Contacts.app, Mozilla Thunderbird) or devices (e.g., iOS Contacts.app), contacts deleted via the Google Contacts web interface do not sync properly and remain visible locally. Over time, deleted contacts accumulate in local apps and devices, creating inconsistencies.

Other actions, such as updating or modifying contact details online, sync correctly. However, deletions performed via the web interface are not propagated to connected devices or apps.

Steps to Reproduce

1.	Set up CardDAV syncing for Google Contacts on a macOS device, iOS device, or Mozilla Thunderbird.
2.	Use the Google Contacts web interface to delete a contact.
3.	Sync the device or app and observe that the deleted contact remains visible locally.

Expected Behavior

Contacts deleted via the Google Contacts web interface should be removed from all connected local apps or devices after syncing, ensuring data consistency across platforms.

Actual Behavior

Contacts deleted via the Google Contacts web interface persist in local apps or devices (e.g., macOS/iOS Contacts.app, Mozilla Thunderbird). This leads to data desynchronization between Google Contacts and the local instances.

References and Further Discussion

https://forums.macrumors.com/threads/ios-address-book-contacts-app-deleted-google-contacts-do-not-sync.2445647/

https://forums.macrumors.com/threads/google-contacts-synchronization-with-ios-contacts-app-issues.2440037/

This issue has been widely reported and discussed by users, indicating it is not an isolated problem.

Comments

bl...@google.com <bl...@google.com> #2Dec 26, 2024 12:11PM

Assigned to jp...@google.com.

The weird thing is, i tested this on a fully resetted samsung s23 with Android 14, no way to reproduce the crash that other users and testers were experiencing.

Then i updated to One UI 6.0, and now i can consistently reproduce the IndexOutOfBoundsException.

jp...@google.com <jp...@google.com> #3Dec 26, 2024 04:10PM

I'm seeing this exact crash in production too.
Not limited to Samsung tho, we also have OnePlus and Sony users affected.

EDIT: I'm using version 2.9.0-alpha04 of the navigation library. But this crash goes way back.
The stacktrace is from 2.9.0-alpha04 tho.

Fatal Exception: java.lang.IndexOutOfBoundsException: Index -1 out of bounds for length 1
at jdk.internal.util.Preconditions.outOfBounds(Preconditions.java:64)
at jdk.internal.util.Preconditions.outOfBoundsCheckIndex(Preconditions.java:70)
at jdk.internal.util.Preconditions.checkIndex(Preconditions.java:266)
at java.util.Objects.checkIndex(Objects.java:359)
at java.util.ArrayList.get(ArrayList.java:434)
at androidx.navigation.compose.NavHostKt$NavHost$28$1.invokeSuspend(NavHost.kt:620)
at kotlin.coroutines.jvm.internal.BaseContinuationImpl.resumeWith(ContinuationImpl.kt:33)
at kotlinx.coroutines.DispatchedTask.run(DispatchedTask.kt:101)
at androidx.compose.ui.platform.AndroidUiDispatcher.performTrampolineDispatch(AndroidUiDispatcher.android.kt:79)
at androidx.compose.ui.platform.AndroidUiDispatcher.access$performTrampolineDispatch(AndroidUiDispatcher.android.kt:41)
at androidx.compose.ui.platform.AndroidUiDispatcher$dispatchCallback$1.run(AndroidUiDispatcher.android.kt:57)
at android.os.Handler.handleCallback(Handler.java:958)
at android.os.Handler.dispatchMessage(Handler.java:99)
at android.os.Looper.loopOnce(Looper.java:230)
at android.os.Looper.loop(Looper.java:319)
at android.app.ActivityThread.main(ActivityThread.java:9063)
at java.lang.reflect.Method.invoke(Method.java)
at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:588)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1103)

mi...@mikemccollister.com <mi...@mikemccollister.com> #4Jan 16, 2025 02:55PM

The same issue with me. Please fix it

tc...@gmail.com <tc...@gmail.com> #5Jan 30, 2025 03:52PM

Seeing this pop up again for us on some Samsung Galaxy S24 running Android 14.

navigation-compose 2.8.5

Fatal Exception: java.lang.IndexOutOfBoundsException: Index -1 out of bounds for length 1
       at jdk.internal.util.Preconditions.outOfBounds(Preconditions.java:64)
       at jdk.internal.util.Preconditions.outOfBoundsCheckIndex(Preconditions.java:70)
       at jdk.internal.util.Preconditions.checkIndex(Preconditions.java:266)
       at java.util.Objects.checkIndex(Objects.java:359)
       at java.util.ArrayList.get(ArrayList.java:434)
       at androidx.navigation.compose.NavHostKt$NavHost$28$1.invokeSuspend(NavHost.kt:620)
       at kotlin.coroutines.jvm.internal.BaseContinuationImpl.resumeWith(ContinuationImpl.kt:33)
       at kotlinx.coroutines.DispatchedTask.run(DispatchedTask.kt:101)
       at androidx.compose.ui.platform.AndroidUiDispatcher.performTrampolineDispatch(AndroidUiDispatcher.android.kt:81)
       at androidx.compose.ui.platform.AndroidUiDispatcher.access$performTrampolineDispatch(AndroidUiDispatcher.android.kt:41)
       at androidx.compose.ui.platform.AndroidUiDispatcher$dispatchCallback$1.run(AndroidUiDispatcher.android.kt:57)
       at android.os.Handler.handleCallback(Handler.java:958)
       at android.os.Handler.dispatchMessage(Handler.java:99)
       at android.os.Looper.loopOnce(Looper.java:230)
       at android.os.Looper.loop(Looper.java:319)
       at android.app.ActivityThread.main(ActivityThread.java:9063)
       at java.lang.reflect.Method.invoke(Method.java)
       at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:588)
       at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1103)

ya...@wix.com <ya...@wix.com> #6Feb 6, 2025 04:51PM

I am using navigation-compose = "2.8.6" and the same error is thrown.

The majority of devices affected are:

samsung dm3q
samsung a52q
realme REE2ADL1
samsung b2q

Exception java.lang.IndexOutOfBoundsException: Index -1 out of bounds for length 1
  at jdk.internal.util.Preconditions.outOfBounds (Preconditions.java:64)
  at jdk.internal.util.Preconditions.outOfBoundsCheckIndex (Preconditions.java:70)
  at jdk.internal.util.Preconditions.checkIndex (Preconditions.java:266)
  at java.util.Objects.checkIndex (Objects.java:359)
  at java.util.ArrayList.get (ArrayList.java:434)
  at androidx.navigation.compose.NavHostKt$NavHost$28$1.invokeSuspend (NavHost.kt:620)
  at kotlin.coroutines.jvm.internal.BaseContinuationImpl.resumeWith (ContinuationImpl.kt:33)
  at kotlinx.coroutines.DispatchedTask.run (DispatchedTask.kt:104)
  at androidx.compose.ui.platform.AndroidUiDispatcher.performTrampolineDispatch (AndroidUiDispatcher.android.kt:79)
  at androidx.compose.ui.platform.AndroidUiDispatcher.access$performTrampolineDispatch (AndroidUiDispatcher.android.kt:41)
  at androidx.compose.ui.platform.AndroidUiDispatcher$dispatchCallback$1.run (AndroidUiDispatcher.android.kt:57)
  at android.os.Handler.handleCallback (Handler.java:958)
  at android.os.Handler.dispatchMessage (Handler.java:99)
  at android.os.Looper.loopOnce (Looper.java:230)
  at android.os.Looper.loop (Looper.java:319)
  at android.app.ActivityThread.main (ActivityThread.java:9063)
  at java.lang.reflect.Method.invoke
  at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run (RuntimeInit.java:588)
  at com.android.internal.os.ZygoteInit.main (ZygoteInit.java:1103)

Message last modified on Feb 6, 2025 04:51PM

wi...@gmail.com <wi...@gmail.com> #7Feb 16, 2025 04:25PM

Same issue:

Exception java.lang.IndexOutOfBoundsException: Index -1 out of bounds for length 1
	at jdk.internal.util.Preconditions.outOfBounds (Preconditions.java:64)
	at jdk.internal.util.Preconditions.outOfBoundsCheckIndex (Preconditions.java:70)
	at jdk.internal.util.Preconditions.checkIndex (Preconditions.java:266)
	at java.util.Objects.checkIndex (Objects.java:359)
	at java.util.ArrayList.get (ArrayList.java:434)
	at androidx.navigation.compose.NavHostKt$NavHost$28$1.invokeSuspend (NavHost.kt:620)
	at kotlin.coroutines.jvm.internal.BaseContinuationImpl.resumeWith (ContinuationImpl.kt:33)
	at kotlinx.coroutines.DispatchedTask.run (DispatchedTask.kt:100)
	at androidx.compose.ui.platform.AndroidUiDispatcher.performTrampolineDispatch (AndroidUiDispatcher.android.kt:81)
	at androidx.compose.ui.platform.AndroidUiDispatcher.access$performTrampolineDispatch (AndroidUiDispatcher.android.kt:41)
	at androidx.compose.ui.platform.AndroidUiDispatcher$dispatchCallback$1.run (AndroidUiDispatcher.android.kt:57)
	at android.os.Handler.handleCallback (Handler.java:958)
	at android.os.Handler.dispatchMessage (Handler.java:99)
	at android.os.Looper.loopOnce (Looper.java:230)
	at android.os.Looper.loop (Looper.java:319)
	at android.app.ActivityThread.main (ActivityThread.java:9063)
	at java.lang.reflect.Method.invoke
	at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run (RuntimeInit.java:588)
	at com.android.internal.os.ZygoteInit.main (ZygoteInit.java:1103)

ma...@gmail.com <ma...@gmail.com> #8Feb 28, 2025 05:53PM

I experience the same issue when calling popBackStack(), but not every time. There is no clear pattern to when the javaIndexOutOfBoundsException: Index -1 out of bounds for length 1 java error occurs. Sometimes it happens after one attempt, but other times it takes up to 20 attempts.

In version 2.8.7 of the library, the exception is simply caught and ignored? That doesn’t seem like a proper solution to me.