Failed Scan Expenses Can Be Merged: Bug Alert!

by ADMIN 47 views
Iklan Headers

Hey there, Expensify users! Have you ever encountered a situation where a failed scan expense with an amount of 0.00 can sneak its way into the merge expenses list? Well, it seems like there's a bit of a glitch in the system, and we're here to break it down for you. This is a detailed look at the issue, the steps to reproduce it, the expected and actual results, and the platforms affected. Let's dive in and get this sorted out, shall we?

The Core of the Issue: Merging Troubles

So, here's the deal. When you're trying to merge expenses, you'd expect a failed scan with a 0.00 amount to stay put, right? Like, you wouldn't expect it to show up in the merge list at all. But guess what? It does. This is the crux of the problem: the system allows a failed scan expense (with a 0.00 amount) to be selected and merged with other expenses. We're talking about a situation where a scan goes wrong, the amount defaults to zero, and yet, the system still lets you try to merge it. It's like trying to put a square peg in a round hole – it just doesn't fit!

This issue is particularly frustrating because it leads to an empty amount field on the confirmation page. When you select that 0.00 amount and try to merge, the amount doesn't stick. Instead, it retains a different, non-zero amount that wasn't even selected. It's like the system is ignoring your choice and going with something else entirely. This can cause confusion, especially when dealing with multiple expenses and different amounts. Let's walk through the steps to replicate this issue to better understand the core of the problem.

Step-by-Step Guide to Reproducing the Bug

Okay, guys, let's get hands-on and see how to make this bug happen. Follow these steps, and you should be able to reproduce the issue on your own. We'll go through each step carefully so you won't miss a beat. Remember, the goal is to see this failed scan expense pop up where it shouldn't. Keep in mind, this is all happening in the staging environment, so no real-world money is at stake. Let's get started!

  1. Navigate to Staging: First things first, head over to staging.new.expensify.com. This is where the magic (and sometimes the bugs) happen.
  2. Enter the Workspace Chat: Find your way to the workspace chat. This is the place where you'll be playing around with your expenses.
  3. Submit a Manual Expense: Create a manual expense. Input all the necessary details as if you were entering an expense normally. This sets the stage.
  4. Create a Failed Scan Expense: This is where things get interesting. Submit a scan expense. Make sure the receipt fails to scan correctly. You'll end up with a failed scan, likely with a default amount of 0.00.
  5. Open the Expense Report: Go to your expense report and open it.
  6. Open the Manual Expense: Locate and open the manual expense you created earlier.
  7. Initiate the Merge: Click on "More," and then select "Merge."
  8. The Problematic Selection: Here's where the issue arises. You'll see the failed scan expense (with the 0.00 amount) in the merge expenses list. This is the first sign of trouble.
  9. Choose the 0.00 Amount: Select the failed scan expense. This is what allows the bug to occur.
  10. Fill in Details: Complete any other required fields. Then click "Continue."
  11. Empty Amount Field: The amount field on the confirmation page will be empty, because you selected 0.00 amount in the previous step.
  12. Merge the Expenses: Click "Merge expenses."
  13. Check the Merged Expense: Open the merged expense to see the end result. The non-zero amount is retained, instead of the 0.00 amount you selected in step 9.

Expected vs. Actual Results: The Discrepancy

Now, let's get into what should happen versus what does happen. This is where we highlight the core of the bug. The expected result is that the failed scan expense with the 0.00 amount should not even appear in the merge expenses list in the first place. It's a fundamental rule. On the other hand, the actual result shows that the failed scan expense does show up, allowing you to select it, and leading to the confusion we discussed earlier. This discrepancy is what causes the frustration and the incorrect behavior. The system should be smarter, recognizing that a failed scan shouldn't be eligible for merging until the issue is fixed, like the amount is entered.

The core of the problem lies in the merging process, and the way the system handles expenses with an amount of 0.00. It's a critical aspect of the application's functionality. The design of the merge expenses function is supposed to prevent these issues from occurring in the first place. The goal is to make sure that the merge expenses function is efficient, easy to use, and, most importantly, reliable. The unexpected results are a huge deal because they affect the way users interact with the expense reports. Ultimately, it causes inaccuracies, which wastes the user’s time.

Impact and Platforms Affected

This bug isn't just a minor annoyance; it has implications for how users manage their expenses. The issue with the failed scan expenses can lead to confusion and inaccuracies in expense reports. The inability to properly merge these expenses can create extra work, as users have to figure out how to fix or re-enter the data. On top of that, the fact that the receipt is visible in the merge expenses list is also problematic. Fortunately, this issue is limited to a specific part of the platform. We are talking about the following platforms:

  • Android App
  • Android MWeb Chrome
  • iOS App
  • iOS MWeb Chrome
  • MacOS Chrome
  • MacOS Safari
  • MacOS Desktop

Looking Ahead: The Path to Resolution

Unfortunately, there is no known workaround for this issue. It's something that needs to be fixed within the system. Given that this issue affects multiple platforms, it's essential that the Expensify team addresses this bug as soon as possible. Users need to be able to trust the accuracy of their expense reports and the functionality of the merging feature. Keeping the community updated on the progress of this issue is also important, so users can be aware of any workarounds or timelines for resolution. Ultimately, the goal is to ensure the reliability of the expense management process and to create a seamless user experience.