From be7351d6833d86aae21fb00d13d536954fbcdacc Mon Sep 17 00:00:00 2001
From: "copilot-swe-agent[bot]" <198982749+Copilot@users.noreply.github.com>
Date: Mon, 15 Dec 2025 11:12:02 +0000
Subject: [PATCH] Add clarifying comments based on code review feedback

Co-authored-by: adbenitez <24558636+adbenitez@users.noreply.github.com>
---
 .../org/thoughtcrime/securesms/ApplicationContext.java     | 7 +++++--
 1 file changed, 5 insertions(+), 2 deletions(-)

diff --git a/src/main/java/org/thoughtcrime/securesms/ApplicationContext.java b/src/main/java/org/thoughtcrime/securesms/ApplicationContext.java
index 10ef9b27f..189e1b29b 100644
--- a/src/main/java/org/thoughtcrime/securesms/ApplicationContext.java
+++ b/src/main/java/org/thoughtcrime/securesms/ApplicationContext.java
@@ -133,8 +133,9 @@ public class ApplicationContext extends MultiDexApplication {
   }
 
   /**
-   * Set DcContext instance. This should only be called by AccountManager.
-   * This method is thread-safe.
+   * Set DcContext instance. This should only be called by AccountManager when switching accounts,
+   * which only happens after initial initialization is complete.
+   * This method is thread-safe but does NOT trigger initialization or notify waiting threads.
    */
   public void setDcContext(DcContext context) {
     synchronized (initLock) {
@@ -268,6 +269,8 @@ public class ApplicationContext extends MultiDexApplication {
         @Override
         public void onAvailable(@NonNull android.net.Network network) {
           Log.i("DeltaChat", "++++++++++++++++++ NetworkCallback.onAvailable() #" + debugOnAvailableCount++);
+          // getDcAccounts() will wait for initialization to complete before calling maybeNetwork()
+          // This is intentional - early network events should wait for proper initialization
           getDcAccounts().maybeNetwork();
         }