From 234b5f5dbf766c8ab53ac4ce0ac7147f8d101b57 Mon Sep 17 00:00:00 2001 From: Tangem Date: Wed, 10 Jun 2026 20:22:55 +0200 Subject: [PATCH] Updated on 2026-08-14 --- .../androidTest/kotlin/com/tangem/scenarios/SendScenarios.kt | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/app/src/androidTest/kotlin/com/tangem/scenarios/SendScenarios.kt b/app/src/androidTest/kotlin/com/tangem/scenarios/SendScenarios.kt index 5517764ac8..c2298b7eb2 100644 --- a/app/src/androidTest/kotlin/com/tangem/scenarios/SendScenarios.kt +++ b/app/src/androidTest/kotlin/com/tangem/scenarios/SendScenarios.kt @@ -312,8 +312,9 @@ fun BaseTestCase.readNetworkFeeAmount(): String { } /** - * Wait until the network fee value stops changing across two checks — the send button is disabled - * (and the hold-to-confirm gesture swallowed) until the fee finishes loading. + * Wait until the network fee value stops changing across two checks — the send button stays disabled + * (and the hold-to-confirm gesture is swallowed) until the fee re-fetch settles. The hold button has + * no enabled/disabled semantics, so waiting on the fee value is the only reliable readiness signal. */ fun TestContext.waitUntilNetworkFeeIsStable(readFee: () -> String) { step("Wait for the network fee to finish loading") {