Skip to content

Conversation

@ZhenjaHorbach
Copy link
Contributor

@ZhenjaHorbach ZhenjaHorbach commented Dec 17, 2025

Explanation of Change

Implement a ‘Split by date’ flow that does the following:

Adds a third split options at the top of the split table: Amount, Percentage, (these should already exist) and Date (this is the new one)
When the user taps 'Date' in the split menu we'll change the view of the split table like so:
Add a date picker for Start Date in the UI
Add a date picker for End Date in the UI
When the user confirms the dates, use the selected dates to overrwrite the existing splits in the table, creating one split for each day of the date range selected.
Set the amounts of the individual splits to equal proportions of the original expense amount.
Important Notes:

We'll maintain the logic and copy for our current warnings/errors on saving splits where the sum of the splits differs from the original transaction amounts.
The 'Date' mode button will not be available when editing splits to avoid adding more logic to start

Fixed Issues

$ #72442
PROPOSAL:

Tests

Enabling Date Mode:

  1. Submitter creates an expense for $200.
  2. Submitter taps 'Split' from the 'More' menu. Two even splits are created in the Split table, each for $100.
  3. Submitter taps the 'Date' pill
  4. Verify the pill is selected and the Split dates field shows

Changing Dates:

  1. After step 3 above, tap on Split dates
  2. Verify that the Split dates page opens
  3. Verify that the date picker opens to the month the original transaction date is in
  4. Set the start date as the 16th
  5. Open the end date picker
  6. Verify that the date picker opens to the month the original transaction date is in
  7. Set the end date as the 18th and tap Save
  8. Verify three splits are created with equal amounts adding up to the original transaction amount
  • Verify that no errors appear in the JS console

Offline tests

Enabling Date Mode:

  1. Submitter creates an expense for $200.
  2. Submitter taps 'Split' from the 'More' menu. Two even splits are created in the Split table, each for $100.
  3. Submitter taps the 'Date' pill
  4. Verify the pill is selected and the Split dates field shows

Changing Dates:

  1. After step 3 above, tap on Split dates
  2. Verify that the Split dates page opens
  3. Verify that the date picker opens to the month the original transaction date is in
  4. Set the start date as the 16th
  5. Open the end date picker
  6. Verify that the date picker opens to the month the original transaction date is in
  7. Set the end date as the 18th and tap Save
  8. Verify three splits are created with equal amounts adding up to the original transaction amount

QA Steps

// TODO: These must be filled out, or the issue title must include "[No QA]."

Enabling Date Mode:

  1. Submitter creates an expense for $200.
  2. Submitter taps 'Split' from the 'More' menu. Two even splits are created in the Split table, each for $100.
  3. Submitter taps the 'Date' pill
  4. Verify the pill is selected and the Split dates field shows

Changing Dates:

  1. After step 3 above, tap on Split dates
  2. Verify that the Split dates page opens
  3. Verify that the date picker opens to the month the original transaction date is in
  4. Set the start date as the 16th
  5. Open the end date picker
  6. Verify that the date picker opens to the month the original transaction date is in
  7. Set the end date as the 18th and tap Save
  8. Verify three splits are created with equal amounts adding up to the original transaction amount
  • Verify that no errors appear in the JS console

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
Android: mWeb Chrome
iOS: Native
iOS: mWeb Safari
MacOS: Chrome / Safari
2025-12-18.15.16.03.mov

@melvin-bot
Copy link

melvin-bot bot commented Dec 17, 2025

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 ts-node ./scripts/generateTranslations.ts --help

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

@ZhenjaHorbach ZhenjaHorbach changed the title Add date tab for splits New Feature: Add Split by date to the split expense flow for new splits Dec 17, 2025
@github-actions
Copy link
Contributor

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

@github-actions
Copy link
Contributor

🧪🧪 Use the links below to test this adhoc build on Android, iOS, Desktop, and Web. Happy testing! 🧪🧪
Built from App PR #77920.

Android 🤖 iOS 🍎
⏩ SKIPPED ⏩ ⏩ SKIPPED ⏩
The build for Android was skipped The build for iOS was skipped
Desktop 💻 Web 🕸️
⏩ SKIPPED ⏩ https://77920.pr-testing.expensify.com
The build for Desktop was skipped Web

👀 View the workflow run that generated this build 👀

@JmillsExpensify
Copy link
Contributor

I went through the testing steps and everything tested well.

@ZhenjaHorbach ZhenjaHorbach marked this pull request as ready for review December 18, 2025 13:22
@ZhenjaHorbach ZhenjaHorbach requested review from a team as code owners December 18, 2025 13:22
@melvin-bot
Copy link

melvin-bot bot commented Dec 18, 2025

@ikevin127 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 request for a team December 18, 2025 13:22
@ZhenjaHorbach
Copy link
Contributor Author

@parasharrajat
You can start reviewing
I just need to add translations

@OSBotify
Copy link
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 c45fe7ee..233ab57d 100644
--- a/src/languages/de.ts
+++ b/src/languages/de.ts
@@ -1380,6 +1380,8 @@ const translations: TranslationDeepObject<typeof en> = {
             quantityGreaterThanZero: 'Die Menge muss größer als Null sein',
             invalidSubrateLength: 'Es muss mindestens einen Untertarif geben',
             invalidRate: 'Satz für diesen Workspace ungültig. Bitte wählen Sie einen verfügbaren Satz aus dem Workspace aus.',
+            endDateBeforeStartDate: 'Das Enddatum darf nicht vor dem Startdatum liegen',
+            endDateSameAsStartDate: 'Das Enddatum darf nicht mit dem Startdatum identisch sein',
         },
         dismissReceiptError: 'Fehler ausblenden',
         dismissReceiptErrorConfirmation: 'Achtung! Wenn du diesen Fehler verwirfst, wird dein hochgeladener Beleg vollständig entfernt. Bist du sicher?',
@@ -1525,6 +1527,10 @@ const translations: TranslationDeepObject<typeof en> = {
             },
         },
         chooseWorkspace: 'Arbeitsbereich auswählen',
+        date: 'Datum',
+        splitDates: 'Datumsangaben aufteilen',
+        splitDateRange: ({startDate, endDate, count}: SplitDateRangeParams) => `${startDate} bis ${endDate} (${count} Tage)`,
+        splitByDate: 'Nach Datum aufteilen',
     },
     transactionMerge: {
         listPage: {
diff --git a/src/languages/fr.ts b/src/languages/fr.ts
index 11ff89a8..e872baf9 100644
--- a/src/languages/fr.ts
+++ b/src/languages/fr.ts
@@ -1383,6 +1383,8 @@ const translations: TranslationDeepObject<typeof en> = {
             quantityGreaterThanZero: 'La quantité doit être supérieure à zéro',
             invalidSubrateLength: 'Il doit y avoir au moins un sous-taux',
             invalidRate: 'Taux non valide pour cet espace de travail. Veuillez sélectionner un taux disponible dans l’espace de travail.',
+            endDateBeforeStartDate: 'La date de fin ne peut pas être antérieure à la date de début',
+            endDateSameAsStartDate: 'La date de fin ne peut pas être identique à la date de début',
         },
         dismissReceiptError: 'Ignorer l’erreur',
         dismissReceiptErrorConfirmation: 'Attention ! Ignorer cette erreur supprimera entièrement votre reçu téléchargé. Êtes-vous sûr ?',
@@ -1528,6 +1530,10 @@ const translations: TranslationDeepObject<typeof en> = {
             },
         },
         chooseWorkspace: 'Choisir un espace de travail',
+        date: 'Date',
+        splitDates: 'Diviser les dates',
+        splitDateRange: ({startDate, endDate, count}: SplitDateRangeParams) => `Du ${startDate} au ${endDate} (${count} jours)`,
+        splitByDate: 'Scinder par date',
     },
     transactionMerge: {
         listPage: {
diff --git a/src/languages/it.ts b/src/languages/it.ts
index 691355df..f3082b9c 100644
--- a/src/languages/it.ts
+++ b/src/languages/it.ts
@@ -1376,6 +1376,8 @@ const translations: TranslationDeepObject<typeof en> = {
             quantityGreaterThanZero: 'La quantità deve essere maggiore di zero',
             invalidSubrateLength: 'Deve esserci almeno un sottotariffa',
             invalidRate: 'Tariffa non valida per questo workspace. Seleziona una tariffa disponibile dal workspace.',
+            endDateBeforeStartDate: 'La data di fine non può essere precedente alla data di inizio',
+            endDateSameAsStartDate: 'La data di fine non può essere uguale alla data di inizio',
         },
         dismissReceiptError: 'Ignora errore',
         dismissReceiptErrorConfirmation: 'Attenzione! Se ignori questo errore, la ricevuta caricata verrà rimossa completamente. Sei sicuro?',
@@ -1521,6 +1523,10 @@ const translations: TranslationDeepObject<typeof en> = {
             },
         },
         chooseWorkspace: 'Scegli uno spazio di lavoro',
+        date: 'Data',
+        splitDates: 'Dividi date',
+        splitDateRange: ({startDate, endDate, count}: SplitDateRangeParams) => `${startDate} a ${endDate} (${count} giorni)`,
+        splitByDate: 'Dividi per data',
     },
     transactionMerge: {
         listPage: {
diff --git a/src/languages/ja.ts b/src/languages/ja.ts
index 64fe296d..1091889c 100644
--- a/src/languages/ja.ts
+++ b/src/languages/ja.ts
@@ -1377,6 +1377,8 @@ const translations: TranslationDeepObject<typeof en> = {
             quantityGreaterThanZero: '数量は0より大きくなければなりません',
             invalidSubrateLength: '少なくとも 1 つのサブレートが必要です',
             invalidRate: 'このワークスペースでは無効なレートです。ワークスペースから利用可能なレートを選択してください。',
+            endDateBeforeStartDate: '終了日は開始日より前にはできません',
+            endDateSameAsStartDate: '終了日は開始日と同じにはできません',
         },
         dismissReceiptError: 'エラーを閉じる',
         dismissReceiptErrorConfirmation: '注意!このエラーを無視すると、アップロードした領収書が完全に削除されます。本当に実行しますか?',
@@ -1522,6 +1524,10 @@ const translations: TranslationDeepObject<typeof en> = {
             },
         },
         chooseWorkspace: 'ワークスペースを選択',
+        date: '日付',
+        splitDates: '日付を分割',
+        splitDateRange: ({startDate, endDate, count}: SplitDateRangeParams) => `${startDate} から ${endDate} まで(${count} 日間)`,
+        splitByDate: '日付で分割',
     },
     transactionMerge: {
         listPage: {
diff --git a/src/languages/nl.ts b/src/languages/nl.ts
index e925f134..6fdc1aeb 100644
--- a/src/languages/nl.ts
+++ b/src/languages/nl.ts
@@ -1375,6 +1375,8 @@ const translations: TranslationDeepObject<typeof en> = {
             quantityGreaterThanZero: 'Hoeveelheid moet groter zijn dan nul',
             invalidSubrateLength: 'Er moet ten minste één subtarief zijn',
             invalidRate: 'Tarief is niet geldig voor deze workspace. Selecteer een beschikbaar tarief uit de workspace.',
+            endDateBeforeStartDate: 'De einddatum kan niet vóór de startdatum liggen',
+            endDateSameAsStartDate: 'De einddatum mag niet hetzelfde zijn als de startdatum',
         },
         dismissReceiptError: 'Foutmelding sluiten',
         dismissReceiptErrorConfirmation: 'Let op! Als je deze foutmelding negeert, wordt je geüploade bon volledig verwijderd. Weet je het zeker?',
@@ -1520,6 +1522,10 @@ const translations: TranslationDeepObject<typeof en> = {
             },
         },
         chooseWorkspace: 'Kies een workspace',
+        date: 'Datum',
+        splitDates: 'Datums splitsen',
+        splitDateRange: ({startDate, endDate, count}: SplitDateRangeParams) => `${startDate} tot ${endDate} (${count} dagen)`,
+        splitByDate: 'Splitsen op datum',
     },
     transactionMerge: {
         listPage: {
diff --git a/src/languages/pl.ts b/src/languages/pl.ts
index 64311a57..1b41fef6 100644
--- a/src/languages/pl.ts
+++ b/src/languages/pl.ts
@@ -1373,6 +1373,8 @@ const translations: TranslationDeepObject<typeof en> = {
             quantityGreaterThanZero: 'Ilość musi być większa niż zero',
             invalidSubrateLength: 'Musi istnieć co najmniej jedna podstawka',
             invalidRate: 'Stawka nie jest prawidłowa dla tego przestrzeni roboczej. Wybierz dostępną stawkę z tej przestrzeni roboczej.',
+            endDateBeforeStartDate: 'Data zakończenia nie może być wcześniejsza niż data rozpoczęcia',
+            endDateSameAsStartDate: 'Data zakończenia nie może być taka sama jak data rozpoczęcia',
         },
         dismissReceiptError: 'Odrzuć błąd',
         dismissReceiptErrorConfirmation: 'Uwaga! Odrzucenie tego błędu spowoduje całkowite usunięcie przesłanego paragonu. Czy na pewno chcesz kontynuować?',
@@ -1518,6 +1520,10 @@ const translations: TranslationDeepObject<typeof en> = {
             },
         },
         chooseWorkspace: 'Wybierz przestrzeń roboczą',
+        date: 'Data',
+        splitDates: 'Podziel daty',
+        splitDateRange: ({startDate, endDate, count}: SplitDateRangeParams) => `${startDate} do ${endDate} (${count} dni)`,
+        splitByDate: 'Podziel według daty',
     },
     transactionMerge: {
         listPage: {
diff --git a/src/languages/pt-BR.ts b/src/languages/pt-BR.ts
index e50adb79..2c69c0cb 100644
--- a/src/languages/pt-BR.ts
+++ b/src/languages/pt-BR.ts
@@ -1373,6 +1373,8 @@ const translations: TranslationDeepObject<typeof en> = {
             quantityGreaterThanZero: 'A quantidade deve ser maior que zero',
             invalidSubrateLength: 'Deve haver pelo menos uma subtarifa',
             invalidRate: 'Taxa inválida para este workspace. Selecione uma taxa disponível do workspace.',
+            endDateBeforeStartDate: 'A data de término não pode ser anterior à data de início',
+            endDateSameAsStartDate: 'A data de término não pode ser igual à data de início',
         },
         dismissReceiptError: 'Dispensar erro',
         dismissReceiptErrorConfirmation: 'Atenção! Ignorar este erro removerá completamente o seu recibo enviado. Tem certeza?',
@@ -1518,6 +1520,10 @@ const translations: TranslationDeepObject<typeof en> = {
             },
         },
         chooseWorkspace: 'Escolha um workspace',
+        date: 'Data',
+        splitDates: 'Dividir datas',
+        splitDateRange: ({startDate, endDate, count}: SplitDateRangeParams) => `${startDate} a ${endDate} (${count} dias)`,
+        splitByDate: 'Dividir por data',
     },
     transactionMerge: {
         listPage: {
diff --git a/src/languages/zh-hans.ts b/src/languages/zh-hans.ts
index 2ec19d37..18ddb257 100644
--- a/src/languages/zh-hans.ts
+++ b/src/languages/zh-hans.ts
@@ -1353,6 +1353,8 @@ const translations: TranslationDeepObject<typeof en> = {
             quantityGreaterThanZero: '数量必须大于零',
             invalidSubrateLength: '必须至少有一个子费率',
             invalidRate: '此汇率对该工作区无效。请选择此工作区中的可用汇率。',
+            endDateBeforeStartDate: '结束日期不能早于开始日期',
+            endDateSameAsStartDate: '结束日期不能与开始日期相同',
         },
         dismissReceiptError: '忽略错误',
         dismissReceiptErrorConfirmation: '提醒!关闭此错误会完全删除你上传的收据。确定要继续吗?',
@@ -1495,6 +1497,10 @@ const translations: TranslationDeepObject<typeof en> = {
             },
         },
         chooseWorkspace: '选择一个工作区',
+        date: '日期',
+        splitDates: '拆分日期',
+        splitDateRange: ({startDate, endDate, count}: SplitDateRangeParams) => `${startDate} 至 ${endDate}(${count} 天)`,
+        splitByDate: '按日期拆分',
     },
     transactionMerge: {
         listPage: {

Note

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

@codecov
Copy link

codecov bot commented Dec 18, 2025

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 86.48% <ø> (ø)
src/ONYXKEYS.ts 100.00% <ø> (ø)
src/SCREENS.ts 100.00% <ø> (ø)
src/libs/DateUtils.ts 61.74% <100.00%> (+0.82%) ⬆️
src/libs/DebugUtils.ts 68.36% <ø> (ø)
src/libs/Navigation/linkingConfig/config.ts 75.00% <ø> (ø)
...gation/AppNavigator/ModalStackNavigators/index.tsx 8.33% <0.00%> (-0.02%) ⬇️
src/types/form/SplitExpenseEditDateForm.ts 0.00% <0.00%> (ø)
src/components/TabSelector/TabSelector.tsx 1.92% <0.00%> (-0.08%) ⬇️
src/libs/TransactionUtils/index.ts 71.78% <50.00%> (-0.10%) ⬇️
... and 4 more
... and 6 files with indirect coverage changes

@ZhenjaHorbach
Copy link
Contributor Author

ZhenjaHorbach commented Dec 18, 2025

TS issue is not related with this PR

Снимок экрана 2025-12-18 в 15 22 17

The same issue

@parasharrajat
Copy link
Member

BUG: On reload, it shows not found page briefly.

BUG: Header title is wrong.

Expected; header title shows split by percentage or split by date based on tab

18.12.2025_22.52.38_REC.mp4

@parasharrajat
Copy link
Member

parasharrajat commented Dec 18, 2025

BUG: No save button date selector and extra space.

image

@ZhenjaHorbach
Copy link
Contributor Author

ZhenjaHorbach commented Dec 18, 2025

BUG: No save button date selector and extra space.

image

I suppose we just have the wrong designs
And the extra space we have on all datepickers

@parasharrajat
Copy link
Member

parasharrajat commented Dec 18, 2025

BUG: no date highlights for selected dates.

Expected: Grey should be today and green should be selected dates.

image

@parasharrajat
Copy link
Member

I suppose we just have the wrong designs

Can you please confirm this on slack or Gh?

@ZhenjaHorbach
Copy link
Contributor Author

ZhenjaHorbach commented Dec 18, 2025

BUG: On reload, it shows not found page briefly.

BUG: Header title is wrong.

Expected; header title shows split by percentage or split by date based on tab

18.12.2025_22.52.38_REC.mp4

As I remember this issue was already in the previous PR

@parasharrajat
Copy link
Member

parasharrajat commented Dec 18, 2025

BUG: Split dates are wrong when splits are created.

I think this one should be fixed #77920 (comment). This impact offline behaviour as well.

@parasharrajat
Copy link
Member

TS issue is not related with this PR

@ZhenjaHorbach I do not see this error on any other PR.

@ZhenjaHorbach
Copy link
Contributor Author

ZhenjaHorbach commented Dec 18, 2025

TS issue is not related with this PR

@ZhenjaHorbach I do not see this error on any other PR.

But we don't use country key here
Strange
But I will check

@parasharrajat
Copy link
Member

May be try merging main first.

@ZhenjaHorbach
Copy link
Contributor Author

May be try merging main first.

I already merged

@lakchote lakchote merged commit 13312ba into Expensify:main Dec 18, 2025
29 of 32 checks passed
@melvin-bot
Copy link

melvin-bot bot commented Dec 18, 2025

@lakchote looks like this was merged without a test passing. Please add a note explaining why this was done and remove the Emergency label if this is not an emergency.

@melvin-bot melvin-bot bot added the Emergency label Dec 18, 2025
@lakchote
Copy link
Contributor

@lakchote
Copy link
Contributor

Not an emergency, see #77920 (comment)

@OSBotify
Copy link
Contributor

🚀 Deployed to staging by https://github.com/lakchote in version: 9.2.82-0 🚀

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

@OSBotify
Copy link
Contributor

🚀 Deployed to staging by https://github.com/lakchote in version: 9.2.82-0 🚀

platform result
🖥 desktop 🖥 success ✅
🕸 web 🕸 success ✅
🤖 android 🤖 cancelled 🔪
🍎 iOS 🍎 success ✅

@OSBotify
Copy link
Contributor

🚀 Deployed to staging by https://github.com/lakchote in version: 9.2.82-0 🚀

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

@OSBotify
Copy link
Contributor

🚀 Deployed to staging by https://github.com/lakchote in version: 9.2.84-0 🚀

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

@OSBotify
Copy link
Contributor

🚀 Deployed to production by https://github.com/AndrewGable in version: 9.2.84-8 🚀

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

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.

7 participants