From 0cb62406b54c513f24e73775ae86fd3561a7d512 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?M=C3=A6hdi=20MOKHTARI?= Date: Tue, 9 Jun 2026 15:51:35 +0200 Subject: [PATCH] fix(salvium): report node connect result in sync status updateNode() had the ConnectedSyncStatus and FailedSyncStatus calls commented out, so a failed daemon connection only got logged and the wallet stayed stuck on "Connecting..." forever instead of showing "unable to sync". This uncomments them so connect success and failure are both reflected in the sync status, matching how lib_monero_wallet already behaves. Both status classes are defined in this same file so it compiles as is. --- lib/wallets/wallet/intermediate/lib_salvium_wallet.dart | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/lib/wallets/wallet/intermediate/lib_salvium_wallet.dart b/lib/wallets/wallet/intermediate/lib_salvium_wallet.dart index 4517f1498..03e11f74c 100644 --- a/lib/wallets/wallet/intermediate/lib_salvium_wallet.dart +++ b/lib/wallets/wallet/intermediate/lib_salvium_wallet.dart @@ -532,9 +532,9 @@ abstract class LibSalviumWallet csSalvium.startListeners(wallet!); csSalvium.startAutoSaving(wallet!); - // _setSyncStatus(ConnectedSyncStatus()); + _setSyncStatus(ConnectedSyncStatus()); } catch (e, s) { - // _setSyncStatus(FailedSyncStatus()); + _setSyncStatus(FailedSyncStatus()); Logging.instance.e( "Exception caught in $runtimeType.updateNode(): ", error: e,