From 610774bd368f7be4c9727b268093c5b0c012da3d Mon Sep 17 00:00:00 2001 From: Alva Swanson Date: Thu, 6 Mar 2025 15:30:51 +0000 Subject: [PATCH] BisqExecutable: Fix startApplication() threading issue The startApplication method is only called on the user thread if the user didn't downgrade his app. The readAllPersisted method calls startApplication on the user thread. However, the code path handling downgrades doesn't call startApplication on the user thread. --- core/src/main/java/bisq/core/app/BisqExecutable.java | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/core/src/main/java/bisq/core/app/BisqExecutable.java b/core/src/main/java/bisq/core/app/BisqExecutable.java index 6db7f8f631d..ee0c456a021 100644 --- a/core/src/main/java/bisq/core/app/BisqExecutable.java +++ b/core/src/main/java/bisq/core/app/BisqExecutable.java @@ -150,7 +150,7 @@ protected void onApplicationLaunched() { // If user tried to downgrade we do not read the persisted data to avoid data corruption // We call startApplication to enable UI to show popup. We prevent in BisqSetup to go further // in the process and require a shut down. - startApplication(); + UserThread.execute(this::startApplication); } else { readAllPersisted(this::startApplication); }