From 29ca395d08a16ff2f32b252950cf4431da7ba63f Mon Sep 17 00:00:00 2001
From: David Baker <dbkr@users.noreply.github.com>
Date: Fri, 19 Jun 2026 13:50:51 +0100
Subject: [PATCH] Fix flaky device verification test (#33909)

This rejectToast was added erroneously: as the comment above states,
there should be no toast left after we verify (apart from our old
friend the notifications nag toast). This was probably flaking because
it was racing to reject the toast before it vanished.
---
 apps/web/playwright/e2e/crypto/device-verification.spec.ts | 1 -
 1 file changed, 1 deletion(-)

diff --git a/apps/web/playwright/e2e/crypto/device-verification.spec.ts b/apps/web/playwright/e2e/crypto/device-verification.spec.ts
index 2f992144c4..1500b5771d 100644
--- a/apps/web/playwright/e2e/crypto/device-verification.spec.ts
+++ b/apps/web/playwright/e2e/crypto/device-verification.spec.ts
@@ -121,7 +121,6 @@ test.describe("Device verification", { tag: "@no-webkit" }, () => {
         await infoDialog.getByRole("button", { name: "Got it" }).click();
 
         // There should be no toast (other than the notifications one)
-        await rejectToast(page, "Verify this device");
         await rejectToast(page, "Notifications");
         await assertNoToasts(page);