fix(lite): drop the 15 s startup overlay and a TLS connection per refresh
- The refresh-model mapper marks the encryption state known when the backend reports it. The wallet tabs wait for that, so every Lite launch sat behind the loading overlay until the 15 s "assume unencrypted" fallback. - Each 2 s refresh skips the backend's `info` (a fresh TLS connection and GetLightdInfo, only a fallback for the chat tip, which the explicit height call already provides) and the gateway's `height` (replaced by that explicit call, which runs after the sync commands so it sees the newest block). Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This commit is contained in:
@@ -6840,6 +6840,15 @@ void testLiteWalletControllerEncryption()
|
||||
applyLiteRefreshModelToWalletState(model, state);
|
||||
EXPECT_TRUE(state.isEncrypted());
|
||||
EXPECT_TRUE(state.isLocked());
|
||||
// ...and marks it known: the wallet tabs wait for that (lite used to sit behind the loading
|
||||
// overlay until the 15 s "assume unencrypted" fallback).
|
||||
EXPECT_TRUE(state.encryption_state_known);
|
||||
|
||||
LiteWalletAppRefreshModel syncOnly;
|
||||
syncOnly.hasSyncStatus = true;
|
||||
dragonx::WalletState untouched;
|
||||
applyLiteRefreshModelToWalletState(syncOnly, untouched);
|
||||
EXPECT_FALSE(untouched.encryption_state_known);
|
||||
}
|
||||
}
|
||||
|
||||
|
||||
Reference in New Issue
Block a user