Merge branch 'main' into snyk-fix-d4b5669ca76951e1fd2fab3e4130c806

Author: chiragsalian

Mobile-Expensify

@@ -443,15 +443,7 @@ Files should be named after the component/function/constants they export, respec
 - All React components should be PascalCase (a.k.a. UpperCamelCase 🐫).
 
 ## Platform-Specific File Extensions
-In most cases, the code written for this repo should be platform-independent. In such cases, each module should have a single file, `index.js`, which defines the module's exports. There are, however, some cases in which a feature is intrinsically tied to the underlying platform. In such cases, the following file extensions can be used to export platform-specific code from a module:
-- Mobile => `index.native.js`
-- iOS Native App/Android Native App => `index.ios.js`/`index.android.js`
-- Web => `index.website.js`
-- Desktop => `index.desktop.js`
-
-**Note:** `index.js` should be the default and only platform-specific implementations should be done in their respective files. i.e: If you have mobile-specific implementation in `index.native.js`, then the desktop/web implementation can be contained in a shared `index.js`.
-
-`index.ios.js` and `index.android.js` are used when the app is running natively on respective platforms. These files are not used when users access the app through mobile browsers, but `index.website.js` is used instead. `index.native.js` are for both iOS and Android native apps. `index.native.js` should not be included in the same module as `index.ios.js` or `index.android.js`.
+This section has moved [here](contributingGuides/philosophies/CROSS-PLATFORM.md).
 
 ## API building
 When adding new API commands (and preferably when starting using a new one that was not yet used in this codebase) always
@@ -659,10 +651,7 @@ This application is built with the following principles.
         5. UI updates with data from the server
 
 1. **Cross Platform 99.9999%**
-    1. A feature isn't done until it works on all platforms.  Accordingly, don't even bother writing a platform-specific code block because you're just going to need to undo it.
-    1. If the reason you can't write cross-platform code is because there is a bug in ReactNative that is preventing it from working, the correct action is to fix RN and submit a PR upstream -- not to hack around RN bugs with platform-specific code paths.
-    1. If there is a feature that simply doesn't exist on all platforms and thus doesn't exist in RN, rather than doing if (platform=iOS) { }, instead write a "shim" library that is implemented with NOOPs on the other platforms.  For example, rather than injecting platform-specific multi-tab code (which can only work on browsers, because it's the only platform with multiple tabs), write a TabManager class that just is NOOP for non-browser platforms.  This encapsulates the platform-specific code into a platform library, rather than sprinkling through the business logic.
-    1. Put all platform specific code in dedicated files and folders, like /platform, and reject any PR that attempts to put platform-specific code anywhere else.  This maintains a strict separation between business logic and platform code.
+See details [here](contributingGuides/philosophies/CROSS-PLATFORM.md).
 
 ----
 

README.md

@@ -114,8 +114,8 @@ android {
         minSdkVersion rootProject.ext.minSdkVersion
         targetSdkVersion rootProject.ext.targetSdkVersion
         multiDexEnabled rootProject.ext.multiDexEnabled
-        versionCode 1009019701
-        versionName "9.1.97-1"
+        versionCode 1009019703
+        versionName "9.1.97-3"
         // Supported language variants must be declared here to avoid from being removed during the compilation.
         // This also helps us to not include unnecessary language variants in the APK.
         resConfigs "en", "es"

android/app/build.gradle

@@ -0,0 +1,45 @@
+# Cross Platform Philosophy
+Learn how the app supports features across all our different platforms.
+
+Currently supported platforms:
+- Web
+- Mobile Web
+- Desktop
+- iOS
+- Android
+
+The goal is: **Cross Platform 99.9999%**
+
+## Rules
+### - Features MUST be implemented on all supported platforms
+A feature isn't done until it works on all platforms. Any platform-specific code blocks will be asked to be undone.
+
+### - React Native bugs MUST be fixed upstream
+If the reason cross-platform code cannot be written is because there is a bug in ReactNative that is preventing it from working, the correct action is to fix RN and submit a PR upstream -- not to hack around RN bugs with platform-specific code paths.
+
+While upstream PRs are waiting to be merged, a patch can be used which is managed by the NPM package `patch-package`. Read more about it [here](https://github.com/Expensify/App?tab=readme-ov-file#adding-hybridapp-related-patches).
+
+### - Features that don't exist on all platforms MUST use NOOP shims
+If there is a feature that simply doesn't exist on all platforms and thus doesn't exist in RN, rather than doing `if (platform=iOS) { }`, instead write a "shim" library that is implemented with NOOPs on the other platforms.  For example, rather than injecting platform-specific multi-tab code (which can only work on browsers, because it's the only platform with multiple tabs), write a TabManager class that just is NOOP for non-browser platforms.  This encapsulates the platform-specific code into a platform library, rather than sprinkling through the business logic.
+
+### - Platform specific code MUST be placed in dedicated files and folders
+Put all platform specific code in dedicated files and folders (see below) and reject any PR that attempts to put platform-specific code anywhere else.  This maintains a strict separation between business logic and platform code.
+
+## Platform-Specific File Extensions
+In most cases, the code written for this repo should be platform-independent. In such cases, each module should have a single file, `index.js`, which defines the module's exports. There are, however, some cases in which a feature is intrinsically tied to the underlying platform. In such cases, the following file extensions can be used to export platform-specific code from a module:
+- Mobile => `index.native.js`
+- iOS Native App/Android Native App => `index.ios.js`/`index.android.js`
+- Web => `index.website.js`
+- Desktop => `index.desktop.js`
+
+**Note:** `index.js` should be the default and only platform-specific implementations should be done in their respective files. i.e: If you have mobile-specific implementation in `index.native.js`, then the desktop/web implementation can be contained in a shared `index.js`.
+
+`index.ios.js` and `index.android.js` are used when the app is running natively on respective platforms. These files are not used when users access the app through mobile browsers, but `index.website.js` is used instead. `index.native.js` are for both iOS and Android native apps. `index.native.js` should not be included in the same module as `index.ios.js` or `index.android.js`.
+
+### Supporting Mobile Web
+The above platform-specific files only work because they are compiled when the app is built for the different platforms. This means that a different mechanism needs to be used for Mobile Web (since "mobile web" and "web" are the same at build time).
+
+It is also well known that different mobile browsers have different quirks and need to use different workarounds at times.
+
+#### - Mobile browser detection SHOULD never be used
+If there is absolutely no other way to fix a bug, then the proper way of detecting the browser is using `@libs/Browser`. Use this as an absolute last resort and have the exception approved by several (ie. more than one) internal engineers.

contributingGuides/PERFORMANCE.md

@@ -5,5 +5,6 @@ The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "S
 "OPTIONAL" are to be interpreted as described in [RFC 2119](https://datatracker.ietf.org/doc/html/rfc2119).
 
 ## Contents
+* [Cross-Platform Philosophy](/contributingGuides/philosophies/CROSS-PLATFORM.md)
 * [Offline Philosophy](/contributingGuides/philosophies/OFFLINE.md)
 * [Routing Philosophy](/contributingGuides/philosophies/ROUTING.md)

contributingGuides/philosophies/CROSS-PLATFORM.md

@@ -306,6 +306,7 @@
         "Italiano",
         "ITSM",
         "Jakub",
+        "jank",
         "janky",
         "jarsigner",
         "johndoe",
@@ -591,6 +592,7 @@
         "Smartscan",
         "soloader",
         "SONIFICATION",
+        "Speedscope",
         "Spotnana",
         "spreadsheetml",
         "SSAE",
@@ -622,7 +624,9 @@
         "Svmy",
         "Swipeable",
         "symbolicate",
+        "symbolicated",
         "Symbolicates",
+        "symbolication",
         "systempreferences",
         "tabindex",
         "Talkspace",
@@ -737,6 +741,8 @@
         "zoneinfo",
         "zxcv",
         "zxldvw",
+        "inputmethod",
+        "copyable",
         "مثال"
     ],
     "ignorePaths": [

contributingGuides/philosophies/INDEX.md

@@ -1,94 +1,116 @@
 ---
-title: Search and Download Expenses
-description: Learn how to find expenses in New Expensify and export them as a CSV or PDF.
-keywords: [New Expensify, search expenses, download expenses, export CSV, export PDF, download report, download receipt]
+title: Export Expenses and Reports
+description: Learn how to export your expenses and reports in CSV or PDF format using default or custom templates in New Expensify.
+keywords: [New Expensify, export expenses, export reports, CSV export, PDF export, download reports, accounting integration, report templates]
 ---
+
 <div id="new-expensify" markdown="1">
 
-You can quickly find and download your expenses in New Expensify—either as a spreadsheet-ready CSV or a printable PDF.
+Expensify offers flexible options to search and export expenses and reports in various formats. You can export them directly to an accounting integration, as a CSV, or as a PDF—right from the web or mobile app.
 
----
+# Export Options
 
-# Search for Expenses
+- **Accounting integration**: Export directly to your connected accounting software.
+- **CSV export**: Choose a default or custom template.
+- **PDF export**: Download full reports, including receipts and notes.
 
-Use filters to quickly locate the expenses you need.
+> **Note:** You can export from both the web and mobile apps.
 
-1. Click **Reports** in the left-hand menu
-2. Select **Expenses**
-3. Use **Filters** to search for expenses by:
-   - Credit card
-   - Category or tag
-   - Date range
-   - Keyword
-   - Expense amount
-   - And more
-4. Click **View results** to display the list of expenses matching your search parameters
+# Export as CSV
 
----
+## Web
 
-# Download Expenses as a CSV
-
-Once you’ve filtered the list:
-
-1. Select the checkbox beside each expense, or choose to **select all** above the expense list.
-2. Click **Selected > Download**.
-3. A CSV file will automatically download to your device (prefixed with “Expensify”).
-4. Open it in your spreadsheet tool.
-
-**Included in the CSV:**
-- Date  
-- Merchant  
-- Description  
-- From  
-- To  
-- Category + GL code  
-- Tag + GL code  
-- Tax + Tax code  
-- Amount  
-- Currency  
-- Type (e.g., cash, card, distance)  
-- Receipt URL
+1. In the left-hand menu, select **Reports > Expense Reports**.
+2. Check the box next to the expenses or reports you want to export, or use the top checkbox to select all.
+3. Click **Selected** at the top.
+4. Select **Export** from the dropdown.
+5. Choose one of the following templates:
+   - **Basic Export** – Simplified, essential fields (date, amount, merchant, category, receipt URL).
+   - **All Data – Expense Level Export** – One row per expense with full data.
+   - **All Data – Report Level Export** – One row per report with summary data.
+   - **Custom Templates** – Any template created by you or your Workspace Admin (if available).
 
----
+You’ll receive a message from **Concierge** with the exported file.
 
-# Download a Report (PDF or CSV)
+> **Note:** Report-level templates only appear if you select full reports (i.e., all expenses in the report).
 
-1. In the left-hand menu, select **Reports**
-2. On the **Reports** tab, click the report you want to download
-3. In the upper-right corner, click **More**
-4. Choose either:
-   - **Download as PDF** to generate a printable version
-   - **Download as CSV** to get a spreadsheet version of the report
+## Mobile
 
-**Note:** You can only download one report at a time.
+1. In the left-hand menu, select **Reports > Expense Reports**.
+2. Tap the three-line icon in the top-right corner.
+3. Choose between **Reports** or **Expenses**.
+4. Check the box next to the items you want to export, or use the top checkbox to select all.
+5. Tap **Selected**, then choose **Export**.
+6. Choose a default or custom export template as described above.
 
----
+You’ll receive the export in a Concierge message.
+
+> **Note:** Report-level templates only appear when full reports are selected.
+
+# Export as PDF
+
+1. Open the individual report you want to export.
+2. Click **More** in the top-right corner.
+3. Select **Download as PDF**.
+
+The PDF will include:
+- All expenses
+- Attached receipts
+- Report notes
 
 # FAQ
 
+## Can I export one line per report?
+
+Yes, use the **All Data – Report Level Export** template. All other templates will export one line per expense.
+
 ## Can I export in PDF or XLS format?
 
-You can export:
-- CSV for raw expense data
-- PDF for full reports
+- **CSV/XLS** – Available for raw expense data.
+- **PDF** – Available for full reports only.
+
+## Can I download individual expenses as a PDF?
+
+No, PDF export is only available for full reports.
+
+## Can I customize the columns in the CSV export?
+
+No, the columns follow a fixed template.
+
+## How do I export to an accounting integration?
+
+Ensure your workspace is connected to a supported accounting platform. [Click here](https://docs.expensify.com) for connection instructions.
+
+## How do I receive my export?
+
+- **Basic Export**: Downloads immediately to your device.
+- **All other templates**: Concierge will send the export file to you via direct message.
+
+## Can I export expenses or reports in bulk?
 
-XLS format is not supported.
+- **CSV export**: Yes, select multiple or all items.
+- **PDF export**: Must be downloaded one at a time.
 
-## Is it possible to download individual expenses as a PDF?
+## Why do I see a 404 error when clicking a receipt URL?
 
-No, you can only download a PDF of full reports. 
+Make sure you're logged into your Expensify account in the same browser when clicking the receipt link.
 
-## Can I customize the columns in the CSV file?
+## The data looks wrong in Excel. How can I fix it?
 
-No, the CSV download uses a fixed template and cannot be customized.
+- Long IDs may appear in scientific notation. To avoid this:
+  1. Open Excel and go to **File > Import**.
+  2. Select your CSV and follow the prompts.
+  3. Format the report/transaction ID column as **Text**.
 
-## Can I select expenses or reports in bulk?
+## Why do the numbers look incorrect in the export?
 
-Yes! Use **Select multiple** or **Select all** to choose multiple expenses for CSV export.  
-PDFs must be downloaded one at a time.
+Switch your spreadsheet program's formatting to **Plain Text** or **Number format** to prevent scientific notation (e.g., `1.79e+308`).
 
-## Why do I see a 404 error when clicking the receipt URL in the CSV?
+## Why are leading zeros missing in my export?
 
-Make sure you're logged into your Expensify account in the same browser. Receipt links only work when you're signed in.
+Excel may remove them automatically. To prevent this:
+1. Open Excel and go to **File > Import**.
+2. Select your CSV.
+3. Set columns with leading zeros to **Text format**.
 
 </div>