Skip to content

[NoQA] [Insights] Move the Account button to the top bar - #100705

Merged
cristipaval merged 23 commits into
Expensify:mainfrom
software-mansion-labs:insights/move-account-tab
Sep 16, 2026
Merged

cristipaval merged 23 commits into
Expensify:mainfrom
software-mansion-labs:insights/move-account-tab

Conversation

@mhawryluk

@mhawryluk mhawryluk commented Sep 9, 2026 •

Copy link
Copy Markdown
Member

Explanation of Change

Moves the Account tab button from the navigation tab bar to the top bar on narrow layouts. Extends TopBar and HeaderWithBackButton components to render the button, similar to how Concierge Anywhere is currently implemented. TopBar always renders it, HeaderWithBackButton is opt-in as it has a wide variety of usages, most of which do not need the button. Also adds an educational tooltip attached to the button being moved. All gated by the insightsPage beta.

Fixed Issues

$ #100651
PROPOSAL: N/A

Tests

  1. Verify the Account tab icon looks the same as before with no beta enabled.
  2. Enable the 'insightPage' beta.
  3. Verify the Account tab button is moved from the tab bar to the top bar on narrow layout, but not moved on wide.
  4. Verify clicking on it navigates to the Account tab and there the icon is selected.
  5. Verify the button shows being a copilot the same as before.
  6. Verify the button shows emojis the same as before.
  7. Verify there is an educational tooltip attached to the Account button in the top bar and clicking on it/on the x button dismisses it forever (Onyx.merge('nvp_dismissedProductTraining', {accountMovedToTopBar: null}) to show again)

Offline tests

N/A

QA Steps

No tests.

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 followed proper code patterns (see Reviewing the code)
    • 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 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)
  • 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)
  • 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.
  • 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
Nagranie.z.ekranu.2026-09-9.o.14.59.55.mov
Android: mWeb Chrome
iOS: Native
Simulator.Screen.Recording.-.iPhone.17.-.2026-09-10.at.16.31.46.mov
Simulator.Screen.Recording.-.iPhone.17.-.2026-09-10.at.16.33.13.mov
iOS: mWeb Safari
MacOS: Chrome / Safari
Nagranie.z.ekranu.2026-09-15.o.10.50.58.mov

@melvin-bot

melvin-bot Bot commented Sep 9, 2026

Copy link
Copy Markdown

Hey, I noticed you changed src/languages/en.ts in a PR from a fork. For security reasons, translations are not generated automatically for PRs from forks.

If you want to automatically generate translations for other locales, an Expensify employee will have to:

  1. Look at the code and make sure there are no malicious changes.
  2. Run the Generate static translations GitHub workflow. If you have write access and the K2 extension, you can simply click: [this button]

Alternatively, if you are an external contributor, you can run the translation script locally with your own OpenAI API key. To learn more, try running:

npx bun ./scripts/generateTranslations.ts --help

Typically, you'd want to translate only what you changed by running npx bun ./scripts/generateTranslations.ts --compare-ref main

@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 8a9bea44..8d58e53c 100644
--- a/src/languages/de.ts
+++ b/src/languages/de.ts
@@ -10900,6 +10900,7 @@ Fügen Sie weitere Ausgabelimits hinzu, um den Cashflow Ihres Unternehmens zu sc
         gpsTooltip: '<tooltip>GPS-Tracking läuft! Wenn du fertig bist, stoppe die Aufzeichnung unten.</tooltip>',
         hasFilterNegation: '<tooltip>Suchen Sie nach Ausgaben ohne Belege mit <strong>-has:receipt</strong>.</tooltip>',
         mileageRateAutoUpdated: '<tooltip>Wir haben den Kurs basierend auf Ihrem Reisedatum aktualisiert.</tooltip>',
+        accountMovedToTopBar: '<tooltip>Greifen Sie auf Ihr Konto und Ihre persönlichen Einstellungen zu.</tooltip>',
     },
     discardChangesConfirmation: {
         title: 'Änderungen verwerfen?',
diff --git a/src/languages/el.ts b/src/languages/el.ts
index 770d8319..2c358317 100644
--- a/src/languages/el.ts
+++ b/src/languages/el.ts
@@ -11092,6 +11092,7 @@ ${reportName}`,
         gpsTooltip: '<tooltip>Η παρακολούθηση GPS βρίσκεται σε εξέλιξη! Όταν τελειώσετε, διακόψτε την παρακολούθηση παρακάτω.</tooltip>',
         hasFilterNegation: '<tooltip>Αναζητήστε δαπάνες χωρίς αποδείξεις χρησιμοποιώντας το <strong>-has:receipt</strong>.</tooltip>',
         mileageRateAutoUpdated: '<tooltip>Ενημερώσαμε την τιμή με βάση την ημερομηνία του ταξιδιού σας.</tooltip>',
+        accountMovedToTopBar: '<tooltip>Αποκτήστε πρόσβαση στον λογαριασμό και τις προσωπικές σας ρυθμίσεις.</tooltip>',
     },
     discardChangesConfirmation: {
         title: 'Απόρριψη αλλαγών;',
diff --git a/src/languages/es.ts b/src/languages/es.ts
index 2135f39b..4f54981a 100644
--- a/src/languages/es.ts
+++ b/src/languages/es.ts
@@ -11104,6 +11104,7 @@ ${reportName}`,
         gpsTooltip: '<tooltip>¡Seguimiento por GPS en curso! Cuando termines, detén el seguimiento a continuación.</tooltip>',
         hasFilterNegation: '<tooltip>Busca gastos sin recibos usando <strong>-has:receipt</strong>.</tooltip>',
         mileageRateAutoUpdated: '<tooltip>Hemos actualizado la tasa según tu fecha de viaje.</tooltip>',
+        accountMovedToTopBar: '<tooltip>Accede a tu cuenta y a tu configuración personal.</tooltip>',
     },
     discardChangesConfirmation: {
         title: '¿Descartar cambios?',
diff --git a/src/languages/fr.ts b/src/languages/fr.ts
index 54614b92..6ac29e93 100644
--- a/src/languages/fr.ts
+++ b/src/languages/fr.ts
@@ -10921,6 +10921,7 @@ Ajoutez davantage de règles de dépenses pour protéger la trésorerie de l’e
         gpsTooltip: '<tooltip>Suivi GPS en cours ! Lorsque vous avez terminé, arrêtez le suivi ci-dessous.</tooltip>',
         hasFilterNegation: '<tooltip>Recherchez les dépenses sans reçus à l’aide de <strong>-has:receipt</strong>.</tooltip>',
         mileageRateAutoUpdated: '<tooltip>Nous avons mis à jour le taux en fonction de votre date de voyage.</tooltip>',
+        accountMovedToTopBar: '<tooltip>Accédez à votre compte et à vos paramètres personnels.</tooltip>',
     },
     discardChangesConfirmation: {
         title: 'Ignorer les modifications ?',
diff --git a/src/languages/it.ts b/src/languages/it.ts
index 23ae5c1f..1b223164 100644
--- a/src/languages/it.ts
+++ b/src/languages/it.ts
@@ -10854,6 +10854,7 @@ Aggiungi altre regole di spesa per proteggere il flusso di cassa aziendale.`,
         gpsTooltip: '<tooltip>Tracciamento GPS in corso! Quando hai finito, interrompi il tracciamento qui sotto.</tooltip>',
         hasFilterNegation: '<tooltip>Cerca le spese senza ricevute usando <strong>-has:receipt</strong>.</tooltip>',
         mileageRateAutoUpdated: '<tooltip>Abbiamo aggiornato il tasso in base alla tua data di viaggio.</tooltip>',
+        accountMovedToTopBar: '<tooltip>Accedi al tuo account e alle impostazioni personali.</tooltip>',
     },
     discardChangesConfirmation: {
         title: 'Scartare le modifiche?',
diff --git a/src/languages/ja.ts b/src/languages/ja.ts
index 52f9476c..5c3533f4 100644
--- a/src/languages/ja.ts
+++ b/src/languages/ja.ts
@@ -10708,6 +10708,7 @@ ${reportName}`,
         gpsTooltip: '<tooltip>GPS追跡を実行中です!完了したら、下で追跡を停止してください。</tooltip>',
         hasFilterNegation: '<tooltip><strong>-has:receipt</strong> を使って、レシートのない経費を検索します。</tooltip>',
         mileageRateAutoUpdated: '<tooltip>出張日にもとづいてレートを更新しました。</tooltip>',
+        accountMovedToTopBar: '<tooltip>アカウントと個人設定にアクセスします。</tooltip>',
     },
     discardChangesConfirmation: {
         title: '変更を破棄しますか?',
diff --git a/src/languages/nl.ts b/src/languages/nl.ts
index eb530a0e..b4a407eb 100644
--- a/src/languages/nl.ts
+++ b/src/languages/nl.ts
@@ -10820,6 +10820,7 @@ er bestedingsregels toe om de kasstroom van het bedrijf te beschermen.`,
         gpsTooltip: '<tooltip>GPS-tracking bezig! Als je klaar bent, stop dan hieronder met bijhouden.</tooltip>',
         hasFilterNegation: '<tooltip>Zoek naar uitgaven zonder bonnen met <strong>-has:receipt</strong>.</tooltip>',
         mileageRateAutoUpdated: '<tooltip>We hebben het tarief bijgewerkt op basis van je reisdatum.</tooltip>',
+        accountMovedToTopBar: '<tooltip>Ga naar je account en persoonlijke instellingen.</tooltip>',
     },
     discardChangesConfirmation: {
         title: 'Wijzigingen negeren?',
diff --git a/src/languages/pl.ts b/src/languages/pl.ts
index de72057d..d5114b33 100644
--- a/src/languages/pl.ts
+++ b/src/languages/pl.ts
@@ -10842,6 +10842,7 @@ Dodaj więcej zasad wydatków, żeby chronić płynność finansową firmy.`,
         gpsTooltip: '<tooltip>Śledzenie GPS w toku! Gdy skończysz, zatrzymaj śledzenie poniżej.</tooltip>',
         hasFilterNegation: '<tooltip>Wyszukaj wydatki bez paragonów za pomocą <strong>-has:receipt</strong>.</tooltip>',
         mileageRateAutoUpdated: '<tooltip>Zaktualizowaliśmy stawkę na podstawie daty twojej podróży.</tooltip>',
+        accountMovedToTopBar: '<tooltip>Uzyskaj dostęp do swojego konta i ustawień osobistych.</tooltip>',
     },
     discardChangesConfirmation: {
         title: 'Odrzucić zmiany?',
diff --git a/src/languages/pt-BR.ts b/src/languages/pt-BR.ts
index 26383837..0d9e0631 100644
--- a/src/languages/pt-BR.ts
+++ b/src/languages/pt-BR.ts
@@ -10815,6 +10815,7 @@ Adicione mais regras de gasto para proteger o fluxo de caixa da empresa.`,
         gpsTooltip: '<tooltip>Rastreamento por GPS em andamento! Quando terminar, pare o rastreamento abaixo.</tooltip>',
         hasFilterNegation: '<tooltip>Pesquise despesas sem recibos usando <strong>-has:receipt</strong>.</tooltip>',
         mileageRateAutoUpdated: '<tooltip>Nós atualizamos a taxa com base na sua data de viagem.</tooltip>',
+        accountMovedToTopBar: '<tooltip>Acesse sua conta e configurações pessoais.</tooltip>',
     },
     discardChangesConfirmation: {
         title: 'Descartar alterações?',
diff --git a/src/languages/zh-hans.ts b/src/languages/zh-hans.ts
index 2459b6c6..3d92258f 100644
--- a/src/languages/zh-hans.ts
+++ b/src/languages/zh-hans.ts
@@ -10440,6 +10440,7 @@ ${reportName}`,
         gpsTooltip: '<tooltip>正在进行 GPS 跟踪!完成后,请在下方停止跟踪。</tooltip>',
         hasFilterNegation: '<tooltip>使用 <strong>-has:receipt</strong> 搜索没有收据的报销。</tooltip>',
         mileageRateAutoUpdated: '<tooltip>我们已根据您的出行日期更新了汇率。</tooltip>',
+        accountMovedToTopBar: '<tooltip>访问你的账户和个人设置。</tooltip>',
     },
     discardChangesConfirmation: {
         title: '放弃更改?',

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 Sep 10, 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/index.ts 91.52% <ø> (ø)
src/components/Avatar/AccountNavigationAvatar.tsx 100.00% <100.00%> (ø)
src/components/HeaderWithBackButton/index.tsx 84.00% <100.00%> (+0.32%) ⬆️
...c/components/Navigation/NavigationTabBar/index.tsx 72.72% <100.00%> (-0.61%) ⬇️
src/components/Navigation/TopBar.tsx 100.00% <100.00%> (ø)
src/pages/domain/DomainInitialPage.tsx 0.00% <ø> (ø)
src/pages/inbox/sidebar/NavigationTabBarAvatar.tsx 100.00% <100.00%> (+8.69%) ⬆️
...pages/inbox/sidebar/ProfileAvatarWithIndicator.tsx 100.00% <100.00%> (ø)
src/pages/workspace/WorkspaceInitialPage.tsx 85.41% <ø> (ø)
src/styles/index.ts 63.86% <ø> (ø)
... and 7 more
... and 106 files with indirect coverage changes

@sumo-slonik sumo-slonik left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM 🚀

@mhawryluk
mhawryluk marked this pull request as ready for review September 10, 2026 15:00
@mhawryluk
mhawryluk requested review from a team as code owners September 10, 2026 15:00
@melvin-bot
melvin-bot Bot requested a review from bernhardoj September 10, 2026 15:00
@melvin-bot

melvin-bot Bot commented Sep 10, 2026

Copy link
Copy Markdown

@bernhardoj 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]

@melvin-bot
melvin-bot Bot requested review from heyjennahay and removed request for a team September 10, 2026 15:00
@mhawryluk

mhawryluk commented Sep 10, 2026 •

Copy link
Copy Markdown
Member Author

cc: @Expensify/design

my reasoning as to on which pages to show the button was: if we show the navigation tab bar there, we show the Account button in the top bar, if not then we don't. please let me know if that's not the desired behavior

also this is what it looks like selected:
Zrzut ekranu 2026-09-10 o 17 00 03

and on hover:
Zrzut ekranu 2026-09-10 o 17 00 16

I also replaced the Concierge Anywhere button under beta only, let me know if you'd like it to change already for all users

@JmillsExpensify
JmillsExpensify requested review from JmillsExpensify and removed request for heyjennahay September 10, 2026 15:36
@JmillsExpensify

Copy link
Copy Markdown
Contributor

cc: @Expensify/design

my reasoning as to on which pages to show the button was: if we show the navigation tab bar there, we show the Account button in the top bar, if not then we don't. please let me know if that's not the desired behavior

also this is what it looks like selected: Zrzut ekranu 2026-09-10 o 17 00 03

and on hover: Zrzut ekranu 2026-09-10 o 17 00 16

I also replaced the Concierge Anywhere button under beta only, let me know if you'd like it to change already for all users

Mind explaining this one a bit more? The intention is to start with Accounting only being visible on the top-level pages. For example:

  • Always shows on Home, Inbox, Spend, Workspaces
  • If you're on Workspaces and choose a workspace, you don't see Account within the workspace editor
  • If you're on Inbox and click into a chat, you don't see Account

And so on and so forth.

@mhawryluk

Copy link
Copy Markdown
Member Author

Mind explaining this one a bit more? The intention is to start with Accounting only being visible on the top-level pages. For example:

  • Always shows on Home, Inbox, Spend, Workspaces
  • If you're on Workspaces and choose a workspace, you don't see Account within the workspace editor
  • If you're on Inbox and click into a chat, you don't see Account

And so on and so forth.

okay, thanks for clarifying, I'll make changes. that is the behavior for both the wide and narrow layouts?

@mhawryluk

Copy link
Copy Markdown
Member Author

oh, per design doc: "To free up a top-level slot, we move Account to the top bar on all desktop pages; on mobile we show the Account avatar on top-level pages (Home, Inbox, Spend, Insights, Workspaces)" so I guess that's only for mobile?

@luacmartins luacmartins left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@bernhardoj

bernhardoj commented Sep 16, 2026 •

Copy link
Copy Markdown
Contributor

Reviewer Checklist

  • I have verified the author checklist is complete (all boxes are checked off).
  • I verified the correct issue is linked in the ### Fixed Issues section above
  • I verified testing steps are clear and they cover the changes made in this PR
    • I verified the steps for local testing are in the Tests section
    • I verified the steps for Staging and/or Production testing are in the QA steps section
    • I verified the steps cover any possible 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 checked that screenshots or videos are included for tests on all platforms
  • I included screenshots or videos for tests on all platforms
  • I verified that the composer does not automatically focus or open the keyboard on mobile unless explicitly intended. This includes checking that returning the app from the background does not unexpectedly open the keyboard.
  • I verified tests pass on all platforms & I tested again on:
    • Android: HybridApp
    • Android: mWeb Chrome
    • iOS: HybridApp
    • iOS: mWeb Safari
    • MacOS: Chrome / Safari
  • If there are any errors in the console that are unrelated to this PR, I either fixed them (preferred) or linked to where I reported them in Slack
  • I verified proper code patterns were followed (see Reviewing the code)
    • 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 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)
  • If a new code pattern is added I verified it was agreed to be used by multiple Expensify engineers
  • I verified that this PR follows the guidelines as stated in the Review Guidelines
  • I verified other components that can be impacted by these changes have been tested, and I retested again (i.e. if the PR modifies a shared library or component like Avatar, I verified the components using Avatar have been tested & I retested again)
  • If a new component is created I verified that:
    • A similar component doesn't exist in the codebase
    • All props are defined accurately
    • The component has a clear name that is non-ambiguous and the purpose of the component can be inferred from the name alone
    • The only data being stored in the state is data necessary for rendering and nothing else
    • The component has the minimum amount of code necessary for its purpose, and it is broken down into smaller components in order to separate concerns and functions
  • 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 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.
  • For any bug fix or new feature in this PR, I verified that sufficient unit tests are included to prevent regressions in this 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.
  • I have checked off every checkbox in the PR reviewer checklist, including those that don't apply to this PR.

Screenshots/Videos

Android: HybridApp
android.mp4
Android: mWeb Chrome
android.mweb.mp4
iOS: HybridApp
ios.mp4
iOS: mWeb Safari
ios.mweb.mp4
MacOS: Chrome / Safari
web.mp4

@cristipaval
cristipaval merged commit a811d4a into Expensify:main Sep 16, 2026
39 of 45 checks passed
@github-actions

Copy link
Copy Markdown
Contributor

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

@OSBotify

Copy link
Copy Markdown
Contributor

✋ This PR was not deployed to staging yet because QA is ongoing. It will be automatically deployed to staging after the next production release.

@luacmartins luacmartins left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for working on this!

@OSBotify

Copy link
Copy Markdown
Contributor

🚀 Deployed to staging by https://github.com/cristipaval in version: 9.4.81-0 🚀

platform result
🕸 web 🕸 success ✅
🤖 android 🤖 success ✅
🍎 iOS 🍎 success ✅

@lanitochka17

Copy link
Copy Markdown

Deploy Blocker #101380 was identified to be related to this PR.

@jponikarchuk

Copy link
Copy Markdown

Deploy Blocker #101405 was identified to be related to this PR.

@OSBotify

Copy link
Copy Markdown
Contributor

🚀 Deployed to production by https://github.com/luacmartins in version: 9.4.81-1 🚀

platform result
🕸 web 🕸 success ✅
🤖 android 🤖 failure ❌
🍎 iOS 🍎 failure ❌

1 similar comment
@OSBotify

Copy link
Copy Markdown
Contributor

🚀 Deployed to production by https://github.com/luacmartins in version: 9.4.81-1 🚀

platform result
🕸 web 🕸 success ✅
🤖 android 🤖 failure ❌
🍎 iOS 🍎 failure ❌

@shawnborton

Copy link
Copy Markdown
Contributor

@mhawryluk can you do a quick follow up here and add a little bit of space between the Concierge icon and the account avatar, so all of the gaps look visually the same?

Before/Now:
CleanShot 2026-09-18 at 10 23 18@2x

After (add margin-right: 4px to Concierge):
CleanShot 2026-09-18 at 10 24 23@2x

@mhawryluk

Copy link
Copy Markdown
Member Author

sure, I have a bug fix PR coming up, so I'll include it there!

@nyomanjyotisa

Copy link
Copy Markdown
Member

#100705 moved the Account avatar into the top bar, where the Account screen freezes while Profile/Status is open. Clearing a status could leave the old emoji visible (#105198). Fixed by #105306, which keeps only the Account screen unfrozen.

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.