Skip to content

[HOLD][Bulk Sign Out] Sign out on all devices from Device management - #106679

Open
roryabraham wants to merge 6 commits into
mainfrom
rory/revoke-all-sessions-702815
Open

roryabraham wants to merge 6 commits into
mainfrom
rory/revoke-all-sessions-702815

Conversation

@roryabraham

@roryabraham roryabraham commented Nov 12, 2026 •

Copy link
Copy Markdown
Contributor

Explanation of Change

Lets people sign out on all devices from Account > Security > Device management. A confirmation explains that the current device is included, supports retry after an error, and returns the user to sign-in with a success message when the request succeeds. Deploy after the API endpoint and its published Auth dependency.

Fixed Issues

$ https://github.com/Expensify/Expensify/issues/702815

Tests

  1. Open the app and sign in to a test account: Account A, Session 1.

  2. Sign in to the same account in a second, separate browser, incognito tab, or device: Account A, Session 2.

  3. Sign in to a different account in a third profile or device: Account B, Session 1.

  4. In Account A, Session 1, open Settings > Security > Device management.

  5. Verify that "Sign out on all devices" appears at the bottom and existing controls for individual devices are still available.

  6. Select Sign out on all devices and verify that the confirmation includes this device and offers Sign out on all devices and Cancel.

  7. Select Cancel and verify that the confirmation closes, the account stays signed in, and no success message appears.

  8. Reload Account A, Session 2 and verify that it is still signed in.

  9. For the web error test, use Google Chrome for Account A, Session 1. Keep Chrome DevTools > Network set to Online, with request blocking and response overrides disabled. While on Device management, open Chrome DevTools > Console and paste the following snippet. It replaces fetch for this page only and holds matching calls before any HTTP request or session revocation occurs. All other requests continue normally. Do not reload this page until the interception is restored.

    (() => {
      if (window.__signOutTest) throw new Error('Run __signOutTest.restore() first');
      const original = window.fetch, pending = new Set();
      let count = 0, failed = false;
      const failure = () => new Response(JSON.stringify({jsonCode: 400}), {
        status: 200, headers: {'Content-Type': 'application/json'}
      });
    
      function intercepted(input, init) {
        const url = typeof input === 'string' || input instanceof URL ? input : input.url;
        if (!new URL(url, location.href).pathname.endsWith('/api/RevokeAllSessions')) {
          return original.call(window, input, init);
        }
        count++;
        if (failed) return Promise.resolve(failure());
        return new Promise((resolve, reject) => {
          const signal = init?.signal ?? input?.signal;
          const finish = error => {
            signal?.removeEventListener('abort', abort);
            pending.delete(release);
            error ? reject(error) : resolve(failure());
          };
          const release = () => finish();
          const abort = () => finish(signal.reason ?? new DOMException('Aborted', 'AbortError'));
          pending.add(release);
          signal?.addEventListener('abort', abort, {once: true});
          if (signal?.aborted) abort();
        });
      }
    
      window.fetch = intercepted;
      window.__signOutTest = {
        get count() { return count; },
        get pending() { return pending.size; },
        fail() { failed = true; [...pending].forEach(release => release()); },
        restore() {
          try { this.fail(); }
          finally {
            if (window.fetch === intercepted) window.fetch = original;
            delete window.__signOutTest;
          }
        }
      };
    })();
  10. In Account A, Session 1, open the confirmation again and confirm. Verify that the button shows a pending state. Attempt repeated confirmation clicks, then run ({count: __signOutTest.count, pending: __signOutTest.pending}) in the Console and verify that it returns {count: 1, pending: 1}. These intercepted calls do not appear in the Network panel because no HTTP request is sent; use these counters to check duplicate submissions.

  11. In the same Console, run __signOutTest.fail() to release the held call with HTTP 200 and JSON {"jsonCode":400}, without contacting the server. In Account A, Session 1, verify that the confirmation stays open with We couldn’t sign you out on all devices. Please try again., allows retry or Cancel, and shows no success message. Verify that ({count: __signOutTest.count, pending: __signOutTest.pending}) now returns {count: 1, pending: 0}.

  12. Reload Account A, Session 2 and verify that it remains signed in. Back in Account A, Session 1's Console, run __signOutTest.restore() before retrying. This restores normal requests; the next confirmation will really revoke the account's sessions. If stopping this test early, run window.__signOutTest?.restore() to release any held calls as failures and restore normal requests without forwarding those held calls.

  13. In Account A, Session 1, retry the confirmation and verify that it returns to sign-in, displays the success message at the bottom of the page, and shows no JavaScript error popup.

  14. Reload or relaunch Account A, Session 2 and verify that it requires fresh sign-in.

  15. Reload Account B, Session 1 and verify that it remains signed in and can open Device management.

  16. Sign in again to Account A, Session 1, reload or relaunch it, and verify that the new session remains usable.

  17. Repeat the cancellation and successful sign-out steps with iOS and Android as the initiating device.

  18. Verify that the flow introduces no JavaScript console errors.

  19. Sign in again to Account A, Session 1, open My settings, select the ordinary Sign out action, and verify that sign-in opens without a navigation reset error.

Offline tests

  1. Sign in to the same test account in two separate sessions, Account A, Session 1 and Account A, Session 2, and open Device management in Account A, Session 1 while online.
  2. Disconnect Account A, Session 1 using the browser's offline network setting or a device network control that actually prevents backend requests.
  3. In Account A, Session 1, select Sign out on all devices and verify that the offline dialog appears with Got it and no success message.
  4. In Account A, Session 1, close the offline dialog, reconnect, and open the sign-out confirmation again.
  5. Disconnect Account A, Session 1 while the confirmation is open and verify that the confirm button becomes disabled and an offline explanation appears.
  6. In Account A, Session 1, select Cancel, reconnect, and verify that the account remains signed in without a delayed sign-out or success message.
  7. Reload Account A, Session 2 and verify that it remains signed in.

QA Steps

Same as tests and offline tests.

Additional provider coverage for QA; Google and Apple sign-in have not been verified locally:

  1. Use a test account with Google sign-in enabled and sign in with Google in two separate browser profiles or devices: Account G, Session 1 and Account G, Session 2.
  2. In Account G, Session 1, open My settings > Security > Device management, select Sign out on all devices, and confirm.
  3. Verify that Account G, Session 1 returns to sign-in with the success message, then reload or relaunch Account G, Session 2 and verify that it requires fresh sign-in rather than silently restoring its Expensify session.
  4. Sign in with Google again to Account G, Session 1, reload or relaunch the app, and verify that the new session works and any configured account security requirements still apply.
  5. Repeat the preceding Google steps with Apple sign-in as Account P, Session 1 and Account P, Session 2, using the same Apple identity for both sessions, and verify that both existing Expensify sessions are invalidated and a fresh Apple sign-in works.
  6. For an account that supports both email and a provider login, sign in with email as Account M, Session 1 and Google or Apple as Account M, Session 2, confirming that both show the same Expensify account email before continuing. Keep an unrelated account signed in as Account B, Session 1.
  7. Use Account M, Session 1 to sign out on all devices, then reload or relaunch Account M, Session 2 and verify that both sessions require fresh sign-in.
  8. Sign in to Account M, Session 1 with email and Account M, Session 2 with its provider again, repeat the sign-out from Account M, Session 2, and verify that Account M, Session 1 is also invalidated.
  9. Repeat the mixed email/provider steps for the other provider when that login is supported, retaining the Account M, Session 1 / Account M, Session 2 labels, and verify that Account B, Session 1 remains signed in throughout.

PR Author Checklist

  • I linked the correct issue in the ### Fixed Issues section above
  • I wrote clear testing steps that cover the changes made in this PR
    • I added steps for local testing in the Tests section
    • I added steps for the expected offline behavior in the Offline steps section
    • I added steps for Staging and/or Production testing in the QA steps section
    • I added steps to cover failure scenarios (i.e. verify an input displays the correct error message if the entered data is not correct)
    • I turned off my network connection and tested it while offline to ensure it matches the expected behavior (i.e. verify the default avatar icon is displayed if app is offline)
    • I tested this PR with a High Traffic account against the staging or production API to ensure there are no regressions (e.g. long loading states that impact usability).
  • I included screenshots or videos for tests on all platforms
  • I ran the tests on all platforms & verified they passed on:
    • Android: Native
    • Android: mWeb Chrome
    • iOS: Native
    • iOS: mWeb Safari
    • MacOS: Chrome / Safari
  • I verified there are no console errors (if there's a console error not related to the PR, report it or open an issue for it to be fixed)
  • I verified there are no new alerts related to the canBeMissing param for useOnyx
  • I followed proper code patterns (see Reviewing the code)
    • I verified that any callback methods that were added or modified are named for what the method does and never what callback they handle (i.e. toggleReport and not onIconClick)
    • I verified that comments were added to code that is not self explanatory
    • I verified that any new or modified comments were clear, correct English, and explained "why" the code was doing something instead of only explaining "what" the code was doing.
    • I verified any copy / text shown in the product is localized by adding it to src/languages/* files and using the translation method
      • If any non-english text was added/modified, I used JaimeGPT to get English > Spanish translation. I then posted it in #expensify-open-source and it was approved by an internal Expensify engineer. Link to Slack message:
    • I verified all numbers, amounts, dates and phone numbers shown in the product are using the localization methods
    • I verified any copy / text that was added to the app is grammatically correct in English. It adheres to proper capitalization guidelines (note: only the first word of header/labels should be capitalized), and is either coming verbatim from figma or has been approved by marketing (in order to get marketing approval, ask the Bug Zero team member to add the Waiting for copy label to the issue)
    • I verified proper file naming conventions were followed for any new files or renamed files. All non-platform specific files are named after what they export and are not named "index.js". All platform-specific files are named for the platform the code supports as outlined in the README.
    • I verified the JSDocs style guidelines (in STYLE.md) were followed
  • If a new code pattern is added I verified it was agreed to be used by multiple Expensify engineers
  • I followed the guidelines as stated in the Review Guidelines
  • I tested other components that can be impacted by my changes (i.e. if the PR modifies a shared library or component like Avatar, I verified the components using Avatar are working as expected)
  • I verified all code is DRY (the PR doesn't include any logic written more than once, with the exception of tests)
  • I verified any variables that can be defined as constants (ie. in CONST.ts or at the top of the file that uses the constant) are defined as such
  • I verified that if a function's arguments changed that all usages have also been updated correctly
  • If any new file was added I verified that:
    • The file has a description of what it does and/or why is needed at the top of the file if the code is not self explanatory
  • If a new CSS style is added I verified that:
    • A similar style doesn't already exist
    • The style can't be created with an existing StyleUtils function (i.e. StyleUtils.getBackgroundAndBorderStyle(theme.componentBG))
  • If new assets were added or existing ones were modified, I verified that:
    • The assets are optimized and compressed (for SVG files, run npm run compress-svg)
    • The assets load correctly across all supported platforms.
  • If the PR modifies code that runs when editing or sending messages, I tested and verified there is no unexpected behavior for all supported markdown - URLs, single line code, code blocks, quotes, headings, bold, strikethrough, and italic.
  • If the PR modifies a generic component, I tested and verified that those changes do not break usages of that component in the rest of the App (i.e. if a shared library or component like Avatar is modified, I verified that Avatar is working as expected in all cases)
  • If the PR modifies a component related to any of the existing Storybook stories, I tested and verified all stories for that component are still working as expected.
  • If the PR modifies a component or page that can be accessed by a direct deeplink, I verified that the code functions as expected when the deeplink is used - from a logged in and logged out account.
  • If the PR modifies the UI (e.g. new buttons, new UI components, changing the padding/spacing/sizing, moving components, etc) or modifies the form input styles:
    • I verified that all the inputs inside a form are aligned with each other.
    • I added Design label and/or tagged @Expensify/design so the design team can review the changes.
  • If a new page is added, I verified it's using the ScrollView component to make it scrollable when more elements are added to the page.
  • I added unit tests for any new feature or bug fix in this PR to help automatically prevent regressions in this user flow.
  • If the main branch was merged into this PR after a review, I tested again and verified the outcome was still expected according to the Test steps.

Screenshots/Videos

Android: Native

Verified cancellation, actual device disconnection, successful sign-out with the visible success message, a second session rejected with 407, an unrelated session still authorized with 200, and fresh sign-in surviving relaunch. This used three sessions and authenticated backend reads; the held-request failure scenario was verified on web.

Android sign-out button pinned to the page bottom Android confirmation including this device Android confirmation disabled while offline Android sign-in screen with the bottom success toast
Android: mWeb Chrome
iOS: Native
iOS: mWeb Safari
MacOS: Chrome / Safari

Playwright verification against the dev backend covered cancellation, offline handling, a held request, failure and retry, and successful revocation. Fresh server requests returned 407 for the second session and 200 for the unrelated account; fresh sign-in also returned 200.

Sign-out button pinned to the page bottom Sign-out confirmation Confirmation disabled while offline Failure with retry and Cancel available Sign-in screen with the bottom success toast

Require online confirmation and confirmed server success before clearing
local credentials. Keep failures retryable in the same confirmation.
@roryabraham roryabraham self-assigned this Nov 12, 2026
@roryabraham
roryabraham requested a review from a team November 12, 2026 08:13
@melvin-bot
melvin-bot Bot requested a review from shawnborton November 12, 2026 08:13
@OSBotify

Copy link
Copy Markdown
Contributor

🦜 Polyglot Parrot! 🦜

Squawk! Looks like you added some shiny new English strings. Allow me to parrot them back to you in other tongues:

View the translation diff
diff --git a/src/languages/de.ts b/src/languages/de.ts
index 2695ec73..4733321e 100644
--- a/src/languages/de.ts
+++ b/src/languages/de.ts
@@ -2676,7 +2676,7 @@ const translations: TranslationDeepObject<typeof en> = {
         revoke: 'Widerrufen',
         unknownDevice: 'Unbekanntes Gerät',
         signOutAllDevices: 'Auf allen Geräten abmelden',
-        signOutAllDevicesConfirmation: 'Sie werden auf allen Geräten abgemeldet, einschließlich diesem. Sie müssen sich erneut anmelden, um Expensify zu nutzen.',
+        signOutAllDevicesConfirmation: 'Sie werden auf allen Geräten, einschließlich diesem, abgemeldet. Sie müssen sich erneut anmelden, um Expensify zu nutzen.',
         signOutAllDevicesError: 'Wir konnten Sie nicht auf allen Geräten abmelden. Bitte versuchen Sie es erneut.',
         signOutAllDevicesSuccess: 'Sie wurden auf allen Geräten abgemeldet.',
     },
diff --git a/src/languages/el.ts b/src/languages/el.ts
index 4d820075..22874c9c 100644
--- a/src/languages/el.ts
+++ b/src/languages/el.ts
@@ -2732,9 +2732,9 @@ const translations: TranslationDeepObject<typeof en> = {
         revoke: 'Ανακαλέστε',
         unknownDevice: 'Άγνωστη συσκευή',
         signOutAllDevices: 'Αποσύνδεση από όλες τις συσκευές',
-        signOutAllDevicesConfirmation: 'Θα αποσυνδεθείτε από όλες τις συσκευές, συμπεριλαμβανομένης αυτής. Θα χρειαστεί να συνδεθείτε ξανά για να χρησιμοποιήσετε το Expensify.',
-        signOutAllDevicesError: 'Δεν μπορέσαμε να σας αποσυνδέσουμε από όλες τις συσκευές. Δοκιμάστε ξανά.',
-        signOutAllDevicesSuccess: 'Αποσυνδεθήκατε από όλες τις συσκευές.',
+        signOutAllDevicesConfirmation: 'Θα αποσυνδεθείτε από όλες τις συσκευές, συμπεριλαμβανομένης και αυτής. Θα χρειαστεί να συνδεθείτε ξανά για να χρησιμοποιήσετε το Expensify.',
+        signOutAllDevicesError: 'Δεν μπορέσαμε να σας αποσυνδέσουμε από όλες τις συσκευές. Παρακαλούμε δοκιμάστε ξανά.',
+        signOutAllDevicesSuccess: 'Έχετε αποσυνδεθεί από όλες τις συσκευές.',
     },
     twoFactorAuth: {
         headerTitle: 'Έλεγχος ταυτότητας δύο παραγόντων',
diff --git a/src/languages/es.ts b/src/languages/es.ts
index 579c2ff4..352a6c8c 100644
--- a/src/languages/es.ts
+++ b/src/languages/es.ts
@@ -2656,9 +2656,9 @@ const translations: TranslationDeepObject<typeof en> = {
         revoke: 'Revocar',
         unknownDevice: 'Dispositivo Desconocido',
         signOutAllDevices: 'Cerrar sesión en todos los dispositivos',
-        signOutAllDevicesConfirmation: 'Se cerrará tu sesión en todos los dispositivos, incluido este. Tendrás que volver a iniciar sesión para usar Expensify.',
-        signOutAllDevicesError: 'No pudimos cerrar tu sesión en todos los dispositivos. Inténtalo de nuevo.',
-        signOutAllDevicesSuccess: 'Se ha cerrado tu sesión en todos los dispositivos.',
+        signOutAllDevicesConfirmation: 'Se cerrará tu sesión en todos los dispositivos, incluido este. Tendrás que iniciar sesión de nuevo para usar Expensify.',
+        signOutAllDevicesError: 'No hemos podido cerrar tu sesión en todos los dispositivos. Por favor, inténtalo de nuevo.',
+        signOutAllDevicesSuccess: 'Has cerrado sesión en todos los dispositivos.',
     },
     twoFactorAuth: {
         headerTitle: 'Autenticación de dos factores',
diff --git a/src/languages/it.ts b/src/languages/it.ts
index 0d988be2..c4afef65 100644
--- a/src/languages/it.ts
+++ b/src/languages/it.ts
@@ -2666,10 +2666,10 @@ const translations: TranslationDeepObject<typeof en> = {
             'Gestisci tutti i dispositivi su cui hai effettuato l\'accesso con il tuo account Expensify. <a href="https://help.expensify.com/articles/new-expensify/settings/Manage-Logged-in-Devices">Scopri di più</a>.',
         revoke: 'Revoca',
         unknownDevice: 'Dispositivo Sconosciuto',
-        signOutAllDevices: 'Esci da tutti i dispositivi',
-        signOutAllDevicesConfirmation: 'Uscirai da tutti i dispositivi, incluso questo. Dovrai accedere di nuovo per usare Expensify.',
-        signOutAllDevicesError: 'Non è stato possibile disconnetterti da tutti i dispositivi. Riprova.',
-        signOutAllDevicesSuccess: 'Hai effettuato la disconnessione da tutti i dispositivi.',
+        signOutAllDevices: 'Disconnetti da tutti i dispositivi',
+        signOutAllDevicesConfirmation: 'Verrai disconnesso da tutti i dispositivi, incluso questo. Dovrai effettuare di nuovo l’accesso per usare Expensify.',
+        signOutAllDevicesError: 'Non siamo riusciti a disconnetterti da tutti i dispositivi. Riprova.',
+        signOutAllDevicesSuccess: 'Sei stato disconnesso da tutti i dispositivi.',
     },
     twoFactorAuth: {
         headerTitle: 'Autenticazione a due fattori',
diff --git a/src/languages/ja.ts b/src/languages/ja.ts
index c86cbdbe..e45a45a0 100644
--- a/src/languages/ja.ts
+++ b/src/languages/ja.ts
@@ -2648,10 +2648,10 @@ const translations: TranslationDeepObject<typeof en> = {
             'Expensify アカウントでログインしているすべてのデバイスを管理できます。<a href="https://help.expensify.com/articles/new-expensify/settings/Manage-Logged-in-Devices">詳しくはこちら</a>.',
         revoke: '取り消す',
         unknownDevice: '不明なデバイス',
-        signOutAllDevices: 'すべてのデバイスからログアウト',
-        signOutAllDevicesConfirmation: 'このデバイスを含むすべてのデバイスからログアウトします。Expensifyを使用するには、再度ログインする必要があります。',
-        signOutAllDevicesError: 'すべてのデバイスからログアウトできませんでした。もう一度お試しください。',
-        signOutAllDevicesSuccess: 'すべてのデバイスからログアウトしました。',
+        signOutAllDevices: 'すべての端末からサインアウト',
+        signOutAllDevicesConfirmation: 'この端末を含むすべてのデバイスからサインアウトされます。Expensify を利用するには、再度サインインする必要があります。',
+        signOutAllDevicesError: 'すべての端末からサインアウトできませんでした。もう一度お試しください。',
+        signOutAllDevicesSuccess: 'すべてのデバイスからサインアウトされました。',
     },
     twoFactorAuth: {
         headerTitle: '2要素認証',
diff --git a/src/languages/nl.ts b/src/languages/nl.ts
index 2f854a92..a30b50fa 100644
--- a/src/languages/nl.ts
+++ b/src/languages/nl.ts
@@ -2664,10 +2664,10 @@ const translations: TranslationDeepObject<typeof en> = {
             'Beheer alle apparaten waarop je bent ingelogd met je Expensify-account. <a href="https://help.expensify.com/articles/new-expensify/settings/Manage-Logged-in-Devices">Meer informatie</a>.',
         revoke: 'Intrekken',
         unknownDevice: 'Onbekend Apparaat',
-        signOutAllDevices: 'Uitloggen op alle apparaten',
-        signOutAllDevicesConfirmation: 'Je wordt uitgelogd op alle apparaten, inclusief dit apparaat. Je moet opnieuw inloggen om Expensify te gebruiken.',
-        signOutAllDevicesError: 'We konden je niet op alle apparaten uitloggen. Probeer het opnieuw.',
-        signOutAllDevicesSuccess: 'Je bent uitgelogd op alle apparaten.',
+        signOutAllDevices: 'Afmelden op alle apparaten',
+        signOutAllDevicesConfirmation: 'Je wordt op alle apparaten afgemeld, ook op dit apparaat. Je moet je opnieuw aanmelden om Expensify te gebruiken.',
+        signOutAllDevicesError: 'We konden je niet op alle apparaten afmelden. Probeer het opnieuw.',
+        signOutAllDevicesSuccess: 'Je bent op alle apparaten uitgelogd.',
     },
     twoFactorAuth: {
         headerTitle: 'Tweeledige verificatie',
diff --git a/src/languages/pl.ts b/src/languages/pl.ts
index 87c829a9..d14b6880 100644
--- a/src/languages/pl.ts
+++ b/src/languages/pl.ts
@@ -2711,10 +2711,10 @@ const translations: TranslationDeepObject<typeof en> = {
             'Zarządzaj wszystkimi urządzeniami, na które zalogowałeś(-aś) się za pomocą konta Expensify. <a href="https://help.expensify.com/articles/new-expensify/settings/Manage-Logged-in-Devices">Dowiedz się więcej</a>.',
         revoke: 'Cofnąć',
         unknownDevice: 'Nieznane Urządzenie',
-        signOutAllDevices: 'Wyloguj się ze wszystkich urządzeń',
-        signOutAllDevicesConfirmation: 'Wylogujesz się ze wszystkich urządzeń, w tym z tego. Aby korzystać z Expensify, trzeba będzie zalogować się ponownie.',
-        signOutAllDevicesError: 'Nie udało się wylogować Cię ze wszystkich urządzeń. Spróbuj ponownie.',
-        signOutAllDevicesSuccess: 'Wylogowano Cię ze wszystkich urządzeń.',
+        signOutAllDevices: 'Wyloguj się na wszystkich urządzeniach',
+        signOutAllDevicesConfirmation: 'Zostaniesz wylogowany ze wszystkich urządzeń, w tym z tego. Żeby dalej korzystać z Expensify, musisz zalogować się ponownie.',
+        signOutAllDevicesError: 'Nie udało się wylogować cię ze wszystkich urządzeń. Spróbuj ponownie.',
+        signOutAllDevicesSuccess: 'Zostałeś wylogowany ze wszystkich urządzeń.',
     },
     twoFactorAuth: {
         headerTitle: 'Uwierzytelnianie dwuskładnikowe',
diff --git a/src/languages/pt-BR.ts b/src/languages/pt-BR.ts
index 19e24668..c9d36873 100644
--- a/src/languages/pt-BR.ts
+++ b/src/languages/pt-BR.ts
@@ -2669,10 +2669,10 @@ const translations: TranslationDeepObject<typeof en> = {
             'Gerencie todos os dispositivos nos quais você fez login com sua conta Expensify. <a href="https://help.expensify.com/articles/new-expensify/settings/Manage-Logged-in-Devices">Saiba mais</a>.',
         revoke: 'Revogar',
         unknownDevice: 'Dispositivo Desconhecido',
-        signOutAllDevices: 'Sair em todos os dispositivos',
-        signOutAllDevicesConfirmation: 'Você sairá da sua conta em todos os dispositivos, incluindo este. Será necessário entrar novamente para usar o Expensify.',
-        signOutAllDevicesError: 'Não foi possível sair da sua conta em todos os dispositivos. Tente novamente.',
-        signOutAllDevicesSuccess: 'Você saiu da sua conta em todos os dispositivos.',
+        signOutAllDevices: 'Sair de todos os dispositivos',
+        signOutAllDevicesConfirmation: 'Você será desconectado de todos os dispositivos, incluindo este. Será preciso entrar novamente para usar o Expensify.',
+        signOutAllDevicesError: 'Não foi possível desconectá-lo de todos os dispositivos. Tente novamente.',
+        signOutAllDevicesSuccess: 'Você foi desconectado de todos os dispositivos.',
     },
     twoFactorAuth: {
         headerTitle: 'Autenticação de dois fatores',
diff --git a/src/languages/zh-hans.ts b/src/languages/zh-hans.ts
index 775eef7e..a1364ee6 100644
--- a/src/languages/zh-hans.ts
+++ b/src/languages/zh-hans.ts
@@ -2569,10 +2569,10 @@ const translations: TranslationDeepObject<typeof en> = {
         description: '管理所有已使用你的 Expensify 账户登录的设备。<a href="https://help.expensify.com/articles/new-expensify/settings/Manage-Logged-in-Devices">了解详情</a>.',
         revoke: '撤销',
         unknownDevice: '未知设备',
-        signOutAllDevices: '退出所有设备上的登录',
-        signOutAllDevicesConfirmation: '你将退出所有设备上的登录,包括此设备。你需要重新登录才能使用 Expensify。',
-        signOutAllDevicesError: '我们无法退出你在所有设备上的登录。请重试。',
-        signOutAllDevicesSuccess: '你已退出所有设备上的登录。',
+        signOutAllDevices: '在所有设备上退出',
+        signOutAllDevicesConfirmation: '您将在所有设备上退出登录(包括此设备)。您需要重新登录才能使用 Expensify。',
+        signOutAllDevicesError: '我们无法让你在所有设备上退出登录。请重试。',
+        signOutAllDevicesSuccess: '你已在所有设备上登出。',
     },
     twoFactorAuth: {
         headerTitle: '双重身份验证',

Note

You can apply these changes to your branch by copying the patch to your clipboard, then running pbpaste | git apply 😉

View workflow run

@codecov

codecov Bot commented Nov 12, 2026 •

Copy link
Copy Markdown

Codecov Report

❌ Looks like you've decreased code coverage for some files. Please write tests to increase, or at least maintain, the existing level of code coverage. See our documentation here for how to interpret this table.

Files with missing lines Coverage Δ
src/CONST/SENTRY_LABEL.ts 100.00% <ø> (ø)
src/components/ConfirmContent.tsx 98.86% <100.00%> (ø)
...cation/GrowlNotificationContainer/index.native.tsx 100.00% <100.00%> (+100.00%) ⬆️
...nts/GrowlNotification/GrowlNotificationContent.tsx 92.30% <100.00%> (+87.62%) ⬆️
...owlNotification/shouldUseExplicitBottomPosition.ts 100.00% <ø> (ø)
...ressable/GenericPressable/implementation/index.tsx 96.96% <100.00%> (+96.96%) ⬆️
src/libs/API/types.ts 100.00% <ø> (ø)
src/libs/actions/Session/index.ts 70.51% <100.00%> (+0.66%) ⬆️
...c/pages/settings/Security/DeviceManagementPage.tsx 95.83% <96.42%> (+95.83%) ⬆️
...rc/components/Modal/Global/ConfirmModalWrapper.tsx 97.26% <94.73%> (-2.74%) ⬇️
... and 291 files with indirect coverage changes

Honor explicit bottom placement on native with a full-screen containing
block and touch pass-through. Reset cleanup to the root registered by
both public and authenticated navigation.
@roryabraham roryabraham changed the title [Bulk Sign Out] Sign out on all devices from Device management [HOLD][Bulk Sign Out] Sign out on all devices from Device management Nov 12, 2026
@roryabraham

Copy link
Copy Markdown
Contributor Author

@codex review

@chatgpt-codex-connector

chatgpt-codex-connector Bot commented Nov 12, 2026 •

Copy link
Copy Markdown
Codex Review Summary: ✅ Completed

This comment shows the latest Codex review activity on this pull request.

Review Status Commit Review trigger
📝 Code Review ✅ Completed 2026-11-13T01:56:28.324394Z 37c26ed Draft marked ready
ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.

@chatgpt-codex-connector

Copy link
Copy Markdown

Codex Review: Didn't find any major issues. Nice work!

Reviewed commit: 9eeac1cf28

ℹ️ About Codex in GitHub

Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".

@github-actions

Copy link
Copy Markdown
Contributor

🚧 roryabraham has triggered a test Expensify/App build. You can view the workflow run here.

@roryabraham

Copy link
Copy Markdown
Contributor Author

This will be on HOLD for the backend pieces to go out, but I'm opening it up for review.

@roryabraham
roryabraham marked this pull request as ready for review November 13, 2026 01:49
@roryabraham
roryabraham requested a review from a team as a code owner November 13, 2026 01:49
@melvin-bot
melvin-bot Bot requested review from MonilBhavsar and flaviadefaria and removed request for a team November 13, 2026 01:50
@melvin-bot

melvin-bot Bot commented Nov 13, 2026

Copy link
Copy Markdown

@MonilBhavsar Please copy/paste the Reviewer Checklist from here into a new comment on this PR and complete it. If you have the K2 extension, you can simply click: [this button]

@github-actions

Copy link
Copy Markdown
Contributor

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants