Skip to content

[NoQA] [Insights] Add Compare to page controls - #102526

Merged
luacmartins merged 8 commits into
Expensify:mainfrom
software-mansion-labs:insights/add-compare-control
Sep 30, 2026
Merged

luacmartins merged 8 commits into
Expensify:mainfrom
software-mansion-labs:insights/add-compare-control

Conversation

@mhawryluk

@mhawryluk mhawryluk commented Sep 29, 2026 •

Copy link
Copy Markdown
Member

Explanation of Change

Adds a new filter to the Insights page for setting Compare mode (None vs Previous period vs Average). Doesn't change how the charts render yet, that will be implemented in the next issues.

Also updates the getInsights action, so that it sends all properties necessary for the backend to send the compare data: previousPeriodSnapshotHash, averageSnapshotHash, numberOfPeriods. The action is not called when changing the compare mode, backend sends data for all three modes together.

The compare filter is not yet persisted on the backend as it requires separating the mechanism out of GetInsights as we don't call this command when changing compare modes by design. It's fine for now, will be addressed in a follow-up issue.

The dropdown button is hidden behind the insightsCompare beta.

Fixed Issues

$ #100663
PROPOSAL: N/A

Tests

  1. Enable both the insightsPage and insightsCompare betas.
  2. Open the Insights page.
  3. Verify there is a Compare filter next to Date with two options: Previous period and Average, off by default, can be reset once set.
  4. Verify the filter is persisted when refreshing the page.
  5. Verify that GetInsights command is not called when switching the compare modes.
  6. Verify that when GetInsights command is called (when first opening the page or changing other filters), the payload includes the new hashes (previousPeriodSnapshotHash, averageSnapshotHash) and numberOfPeriods. And that the response returns data for comparison (3x as many snapshots as charts shown).

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

iOS: Native
Simulator.Screen.Recording.-.iPhone.17.Pro.-.2026-09-29.at.13.22.45.mov
MacOS: Chrome / Safari
Nagranie.z.ekranu.2026-09-29.o.13.11.41.mov

@melvin-bot

melvin-bot Bot commented Sep 29, 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

@trjExpensify

Copy link
Copy Markdown
Contributor

Running translations. 👍

@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 1b8f0e88..00eff929 100644
--- a/src/languages/de.ts
+++ b/src/languages/de.ts
@@ -1163,6 +1163,7 @@ const translations: TranslationDeepObject<typeof en> = {
         viewOnSpend: 'In Ausgaben anzeigen',
         emptyState: {title: 'Nichts anzuzeigen', subtitle: 'Versuchen Sie, Ihre Kriterien oben anzupassen'},
         noExpensesState: {title: 'Sehen Sie, wohin Ihr Geld fließt', subtitle: 'Sobald Sie Ausgaben haben, finden Sie Ausgabentrends, Top-Händler und mehr.'},
+        compare: {label: 'Vergleichen', previousPeriod: 'Vorheriger Zeitraum', average: 'Durchschnitt'},
     },
     allSettingsScreen: {
         subscription: 'Abonnement',
diff --git a/src/languages/el.ts b/src/languages/el.ts
index 150e5abc..3025336c 100644
--- a/src/languages/el.ts
+++ b/src/languages/el.ts
@@ -1208,6 +1208,7 @@ const translations: TranslationDeepObject<typeof en> = {
         viewOnSpend: 'Προβολή στο Spend',
         emptyState: {title: 'Τίποτα προς εμφάνιση', subtitle: 'Δοκιμάστε να προσαρμόσετε τα κριτήριά σας παραπάνω'},
         noExpensesState: {title: 'Δείτε πού πηγαίνουν τα χρήματά σας', subtitle: 'Μόλις έχετε δαπάνες, θα βλέπετε τάσεις δαπανών, κορυφαίους εμπόρους και άλλα.'},
+        compare: {label: 'Σύγκριση', previousPeriod: 'Προηγούμενη περίοδος', average: 'Μέσος όρος'},
     },
     allSettingsScreen: {
         subscription: 'Συνδρομή',
diff --git a/src/languages/es.ts b/src/languages/es.ts
index f8b9b288..365c0de6 100644
--- a/src/languages/es.ts
+++ b/src/languages/es.ts
@@ -1158,6 +1158,7 @@ const translations: TranslationDeepObject<typeof en> = {
         viewOnSpend: 'Ver en Gastos',
         emptyState: {title: 'Nada que mostrar', subtitle: 'Prueba a ajustar tus criterios de arriba'},
         noExpensesState: {title: 'Ve adónde va tu dinero', subtitle: 'Una vez que tengas gastos, encontrarás tendencias de gasto, principales comercios y mucho más.'},
+        compare: {label: 'Comparar', previousPeriod: 'Periodo anterior', average: 'Promedio'},
     },
     allSettingsScreen: {
         subscription: 'Suscripcion',
diff --git a/src/languages/fr.ts b/src/languages/fr.ts
index 25aa1b34..c6c82c29 100644
--- a/src/languages/fr.ts
+++ b/src/languages/fr.ts
@@ -1168,6 +1168,7 @@ const translations: TranslationDeepObject<typeof en> = {
             title: 'Voyez où va votre argent',
             subtitle: 'Une fois que vous aurez des dépenses, vous verrez des tendances de dépenses, les principaux marchands et plus encore.',
         },
+        compare: {label: 'Comparer', previousPeriod: 'Période précédente', average: 'Moyenne'},
     },
     allSettingsScreen: {
         subscription: 'Abonnement',
diff --git a/src/languages/it.ts b/src/languages/it.ts
index 6064e9b5..91fe9761 100644
--- a/src/languages/it.ts
+++ b/src/languages/it.ts
@@ -1163,6 +1163,7 @@ const translations: TranslationDeepObject<typeof en> = {
         viewOnSpend: 'Visualizza in Spese',
         emptyState: {title: 'Niente da mostrare', subtitle: 'Prova a modificare i criteri qui sopra'},
         noExpensesState: {title: 'Scopri dove va il tuo denaro', subtitle: 'Una volta che avrai delle spese, troverai tendenze di spesa, principali esercenti e altro ancora.'},
+        compare: {label: 'Confronta', previousPeriod: 'Periodo precedente', average: 'Media'},
     },
     allSettingsScreen: {
         subscription: 'Abbonamento',
diff --git a/src/languages/ja.ts b/src/languages/ja.ts
index 042a7c0d..3251881c 100644
--- a/src/languages/ja.ts
+++ b/src/languages/ja.ts
@@ -1150,6 +1150,7 @@ const translations: TranslationDeepObject<typeof en> = {
         viewOnSpend: '支出で表示',
         emptyState: {title: '表示するものはありません', subtitle: '上の条件を調整してみてください'},
         noExpensesState: {title: 'お金の使い道を確認する', subtitle: '経費が登録されると、支出の傾向や上位の加盟店など、さまざまな情報を確認できるようになります。'},
+        compare: {label: '比較', previousPeriod: '前の期間', average: '平均'},
     },
     allSettingsScreen: {
         subscription: 'サブスクリプション',
diff --git a/src/languages/nl.ts b/src/languages/nl.ts
index eae27830..9d264f93 100644
--- a/src/languages/nl.ts
+++ b/src/languages/nl.ts
@@ -1162,6 +1162,7 @@ const translations: TranslationDeepObject<typeof en> = {
         viewOnSpend: 'Bekijken in Uitgaven',
         emptyState: {title: 'Niets om weer te geven', subtitle: 'Probeer je criteria hierboven aan te passen'},
         noExpensesState: {title: 'Zie waar je geld naartoe gaat', subtitle: 'Zodra je uitgaven hebt, zie je bestedingspatronen, topverkopers en meer.'},
+        compare: {label: 'Vergelijken', previousPeriod: 'Vorige periode', average: 'Gemiddeld'},
     },
     allSettingsScreen: {
         subscription: 'Abonnement',
diff --git a/src/languages/pl.ts b/src/languages/pl.ts
index 482f1f88..6caf62af 100644
--- a/src/languages/pl.ts
+++ b/src/languages/pl.ts
@@ -1183,6 +1183,7 @@ const translations: TranslationDeepObject<typeof en> = {
         viewOnSpend: 'Zobacz w Wydatkach',
         emptyState: {title: 'Nic do wyświetlenia', subtitle: 'Spróbuj zmienić kryteria powyżej'},
         noExpensesState: {title: 'Zobacz, na co idą twoje pieniądze', subtitle: 'Gdy będziesz mieć wydatki, zobaczysz trendy w wydawaniu, najważniejszych sprzedawców i więcej.'},
+        compare: {label: 'Porównaj', previousPeriod: 'Poprzedni okres', average: 'Średnia'},
     },
     allSettingsScreen: {
         subscription: 'Subskrypcja',
diff --git a/src/languages/pt-BR.ts b/src/languages/pt-BR.ts
index ce56c5ca..07d04c73 100644
--- a/src/languages/pt-BR.ts
+++ b/src/languages/pt-BR.ts
@@ -1162,6 +1162,7 @@ const translations: TranslationDeepObject<typeof en> = {
         viewOnSpend: 'Ver em Gastos',
         emptyState: {title: 'Nada para mostrar', subtitle: 'Tente ajustar seus critérios acima'},
         noExpensesState: {title: 'Veja para onde vai o seu dinheiro', subtitle: 'Quando você tiver despesas, vai encontrar tendências de gastos, principais estabelecimentos e muito mais.'},
+        compare: {label: 'Comparar', previousPeriod: 'Período anterior', average: 'Média'},
     },
     allSettingsScreen: {
         subscription: 'Assinatura',
diff --git a/src/languages/zh-hans.ts b/src/languages/zh-hans.ts
index ba103eb5..370640de 100644
--- a/src/languages/zh-hans.ts
+++ b/src/languages/zh-hans.ts
@@ -1116,6 +1116,7 @@ const translations: TranslationDeepObject<typeof en> = {
         viewOnSpend: '在支出中查看',
         emptyState: {title: '没有可显示的内容', subtitle: '请尝试调整上面的条件'},
         noExpensesState: {title: '查看你的资金流向', subtitle: '添加报销后,您就能查看消费趋势、主要商家等更多信息。'},
+        compare: {label: '比较', previousPeriod: '上一期', average: '平均'},
     },
     allSettingsScreen: {
         subscription: '订阅',

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 29, 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 95.79% <ø> (ø)
src/pages/Insights/insightsFilterParsing.ts 100.00% <100.00%> (ø)
src/pages/Insights/insightsFilters.ts 100.00% <ø> (ø)
...c/pages/Insights/controls/InsightsPageControls.tsx 89.47% <66.66%> (-4.28%) ⬇️
src/pages/Insights/InsightsDashboard.tsx 0.00% <0.00%> (ø)
src/pages/Insights/insightsQueries.ts 92.30% <90.47%> (-3.99%) ⬇️
...pages/Insights/controls/InsightsCompareControl.tsx 0.00% <0.00%> (ø)
... and 247 files with indirect coverage changes

@mhawryluk
mhawryluk marked this pull request as ready for review September 29, 2026 12:45
@mhawryluk
mhawryluk requested review from a team as code owners September 29, 2026 12:45
@melvin-bot
melvin-bot Bot requested review from dylanexpensify and eVoloshchak and removed request for a team and dylanexpensify September 29, 2026 12:45
@melvin-bot

melvin-bot Bot commented Sep 29, 2026

Copy link
Copy Markdown

@eVoloshchak 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 removed the request for review from a team September 29, 2026 12:45
@mhawryluk

Copy link
Copy Markdown
Member Author

@daledah @bernhardoj @truph01 can one of you please review this PR? it's part of the Insights project

@truph01

truph01 commented Sep 29, 2026 •

Copy link
Copy Markdown
Contributor

I can review it, please assign me so it will be in my K2

@mhawryluk

Copy link
Copy Markdown
Member Author

@MelvinBot assign @truph01 and unassign @eVoloshchak on this PR

@mhawryluk

Copy link
Copy Markdown
Member Author

@MelvinBot review

@MelvinBot
MelvinBot requested review from truph01 and removed request for eVoloshchak September 29, 2026 13:02
@MelvinBot

Copy link
Copy Markdown
Contributor

Done. I removed eVoloshchak and added truph01 as the reviewer on this PR. eVoloshchak was a requested reviewer, not an assignee, so I changed the reviewer request. You're still the only assignee.


view run

@MelvinBot

Copy link
Copy Markdown
Contributor

Code review

I found no blocking bugs. The request logic is correct: compare stays out of the dashboard hash and the request, and each chart sends all three snapshot hashes. CI is green. Please check one possible issue before merging:

  1. Compare may reset after other filter changes. insightsQueries.ts:82 removes compare from inputQuery. The client keeps the selection only in its local nvp_searchFilters. If the GetInsights response writes nvp_searchFilters back from inputQuery, any refetch will clear Compare. To test: set Compare, change Date, and check whether Compare is still selected. Test step 4 (refresh) won't catch this.
Nits (non-blocking)
  • Effect dependencies: InsightsDashboard.tsx:173 drops jsonQuery from the effect dependencies. You don't need this change: jsonQuery already stays the same across compare modes, because buildFilterFormValues omits compare. Keeping jsonQuery makes sure a future request field that isn't part of hash still triggers a refetch. For example, numberOfPeriods might become configurable.
  • Stale value without the beta: insightsFilterParsing.ts:45 reads a stored compare even without the insightsCompare beta. InsightsPageControls.tsx:40 hides the only control that can reset it. Nothing reads the value yet, so this is harmless today. Once the charts render comparisons, consider checking the beta where the value is used.
What I checked
  • compare changes the per-chart hash through the ordered query in SearchQueryUtils, so the three snapshot hashes differ. The new test confirms that switching compare modes sends the same request.
  • getInsights clears errors on all three snapshot hashes for each chart, which is correct.
  • useInsightsChartData and Home insights still call applyInsightsFilters without compare, so they keep reading the current-period snapshot.
  • Resetting the control calls onChange(undefined), and buildInsightsQueryString then leaves compare out of the stored query.
  • Translations are present for all 11 locales.

view run

@mhawryluk

Copy link
Copy Markdown
Member Author

Code review

  1. Compare may reset after other filter changes.

I did test it and I didn't find it to happen. and we'll be changing how persisting the filter works anyway

Nits (non-blocking)

  • Effect dependencies:

okay, done

  • Stale value without the beta:

not an issue

luacmartins
luacmartins previously approved these changes Sep 29, 2026

@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

cristipaval
cristipaval previously approved these changes Sep 29, 2026
aldo-expensify
aldo-expensify previously approved these changes Sep 29, 2026
@luacmartins

Copy link
Copy Markdown
Contributor

@truph01 all yours

@truph01

truph01 commented Sep 30, 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 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 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 and each prop has a /** comment above it */
    • The file is named correctly
    • 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
    • For Class Components, any internal methods passed to components event handlers are bound to this properly so there are no scoping issues (i.e. for onClick={this.submit} the method this.submit should be bound to this in the constructor)
    • Any internal methods bound to this are necessary to be bound (i.e. avoid this.submit = this.submit.bind(this); if this.submit is never passed to a component event handler like onClick)
    • All JSX used for rendering exists in the render method
    • 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 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 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

MacOS: Chrome / Safari
Screen.Recording.2026-09-30.at.08.44.09.mov

Comment thread src/pages/Insights/insightsQueries.ts Resolved
Comment thread src/pages/Insights/insightsQueries.ts Resolved
Comment thread src/pages/Insights/insightsQueries.ts Resolved
@mhawryluk

Copy link
Copy Markdown
Member Author

@truph01 back to you

@mhawryluk
mhawryluk requested a review from truph01 September 30, 2026 10:46
@luacmartins
luacmartins merged commit 589b5f8 into Expensify:main Sep 30, 2026
56 of 80 checks passed
@github-actions

Copy link
Copy Markdown
Contributor

🚧 luacmartins 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.

@OSBotify

OSBotify commented Oct 1, 2026

Copy link
Copy Markdown
Contributor

🚀 Deployed to staging by https://github.com/luacmartins in version: 9.5.0-0 🚀

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

@OSBotify

OSBotify commented Oct 1, 2026

Copy link
Copy Markdown
Contributor

🚀 Deployed to production by https://github.com/Julesssss in version: 9.5.0-5 🚀

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

Bundle Size Analysis (Sentry):

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.

8 participants