Merge branch 'main' into korytko/display-sender-avatar-next-to-preview

Author: JakubKorytko

Mobile-Expensify

@@ -13,7 +13,7 @@ apply from: project(':react-native-config').projectDir.getPath() + "/dotenv.grad
 /* Fullstory settings */
 fullstory {
     org 'o-1WN56P-na1'
-    enabledVariants 'production'
+    enabledVariants 'all'
     logcatLevel 'debug'
     recordOnStart false
 }
@@ -114,8 +114,8 @@ android {
         minSdkVersion rootProject.ext.minSdkVersion
         targetSdkVersion rootProject.ext.targetSdkVersion
         multiDexEnabled rootProject.ext.multiDexEnabled
-        versionCode 1009017701
-        versionName "9.1.77-1"
+        versionCode 1009017800
+        versionName "9.1.78-0"
         // 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

@@ -32,7 +32,7 @@ buildscript {
         classpath("com.google.firebase:firebase-crashlytics-gradle:2.7.1")
         classpath("com.google.firebase:perf-plugin:1.4.1")
         // Fullstory integration
-        classpath ("com.fullstory:gradle-plugin-local:1.52.0")
+        classpath ("com.fullstory:gradle-plugin-local:1.61.0")
 
         // NOTE: Do not place your application dependencies here; they belong
         // in the individual module build.gradle files

android/build.gradle

@@ -65,7 +65,7 @@ Navigation.navigate(ROUTES.HOME);
 // Navigation with parameters
 Navigation.navigate(
     ROUTES.SEARCH_ROOT.getRoute({
-        query: 'type:expense status:all search',
+        query: 'type:expense search',
         // additional parameters...
     }),
 );
@@ -654,7 +654,7 @@ function useCustomRootStackNavigatorState({state}: CustomStateHookProps) {
 }
 ```
 
-To optimize the number of routes rendered in `RootStackNavigator` we limit the number of `FullScreenNavigators` rendered to 2 (we need to render the previous fullscreen too for the transition animations to work well). 
+To optimize the number of routes rendered in `RootStackNavigator` we limit the number of `FullScreenNavigators` rendered to 2 (we need to render the previous fullscreen too for the transition animations to work well). There's an exception for `SearchFullscreenNavigator` where we render only last route when possible due to performance implications. The idea stays the same.
 
 -   `src/libs/Navigation/AppNavigator/createSearchFullscreenNavigator/index.tsx`
 
@@ -664,10 +664,9 @@ function useCustomEffects(props: CustomEffectsHookProps) {
     usePreserveNavigatorState(props.state, props.parentRoute);
 }
 
-// This is a custom state hook that is used to render the last two routes in the stack.
-// We do this to improve the performance of the search results screen.
-function useCustomState({state}: CustomStateHookProps) {
-    const routesToRender = [...state.routes.slice(-2)];
+// For web we only render last route in SearchFullscreenNavigator. Other navigators are keep last two routes mounted. The idea stays the same.
+export default function useCustomState({state}: CustomStateHookProps) {
+    const routesToRender = state.routes.slice(-1);
     return {...state, routes: routesToRender, index: routesToRender.length - 1};
 }
 ```

assets/images/treasure-chest.svg

@@ -98,6 +98,7 @@
         "Charleson",
         "Checkmark",
         "checkmarked",
+        "chien",
         "Chronos",
         "citi",
         "clawback",
@@ -136,6 +137,7 @@
         "deeplinks",
         "delegators",
         "delish",
+        "describedby",
         "Deutsch",
         "devportal",
         "DFOLLY",
@@ -295,6 +297,7 @@
         "killall",
         "Kowalski",
         "Krasoń",
+        "labelledby",
         "Lagertha",
         "laggy",
         "lastiPhoneLogin",

contributingGuides/NAVIGATION.md

@@ -32,7 +32,7 @@ You can export transactions from a specific date range to help with monthly reco
 4. Apply the following filters: 
    - **Card**: select the applicable card feed. 
    - **Posted date**: Set the appropriate date range (e.g., `posted<2025-02-28 AND posted>2025-02-01`)
-5. Alternatively, you can enter this directly in the search bar (e.g., `type:expense status:all feed:"all in cards" posted<2025-02-28 posted>2025-02-01`)
+5. Alternatively, you can enter this directly in the search bar (e.g., `type:expense feed:"all in cards" posted<2025-02-28 posted>2025-02-01`)
 6. Once filtered, click the **Export** icon in the top-right corner to download the report as a spreadsheet.
 
 ---

cspell.json

@@ -87,6 +87,33 @@ This feature helps prevent policy violations and ensures accurate expense tracki
 
 ---
 
+# Split Personal Expenses
+
+To split an expense, you’ll need to start a chat with each person you’re requesting money from. Once the chat is started, you can request their share of the bill.
+
+## Start a Chat Before Splitting
+
+1. Click the green Create button in the left sidebar.
+2. Select Start Chat.
+3. Search for the person by name, email, or phone number.
+4. Send them a message to begin the conversation.
+5. Once a chat is started, follow the steps below to split the expense.
+
+## Split the Expense
+
+1. In the chat thread, click the + icon next to the message box.
+2. Select Split Expense.
+3. Upload a photo of your receipt, or manually enter the total bill amount.
+4. Click Next.
+- Select the people you want to split the cost with.
+5. You can enter names, emails, or phone numbers.
+6. Click Next.
+7. (Optional) Add a reason for the request in the Description field.
+8. (Optional) If entering the amount manually, include the merchant and date of purchase.
+9. Click Split.
+
+Each person will receive a notification via email or text with the request details. You can chat about the expense in Expensify Chat, and payments can be received via your Expensify Wallet or through other methods.
+
 # Next Steps for Workspace Expenses
 
 - Expenses are automatically added to a report.

docs/articles/new-expensify/expensify-card/View-and-Reconcile-Expensify-Card-Expenses.md

@@ -59,7 +59,7 @@ Using search formats allows you to define complex report parameters using simple
 - **Locate unapproved reports:** `status:unapproved`
 - **Unapproved employee expenses:** `type:expense status:outstanding`
 - **Unpaid employee expenses:** `type:expense status:approved`
-- **All card spend from December 2024:** `type:expense status:all expense-type:card posted<=2024-12-31 posted>=2024-12-01`
+- **All card spend from December 2024:** `type:expense expense-type:card posted<=2024-12-31 posted>=2024-12-01`
 
 ## Access Search Commands:
 - **Option 1:** Click Reports at the bottom of the left-hand navigation bar.