Expense Report Issue: 'Not Here' Error After Account Merge

Nov 10, 2025 by Admin 59 views

Hey guys, let's dive into a frustrating bug report that's been making the rounds! We're talking about an issue where the "Add Expense" button in an expense report is leading users to a "Not Here" page. This bug specifically pops up after accounts have been merged, a process where we combine two user profiles into one. This can be a real headache for users trying to manage their expenses. We'll break down the steps, the expected and actual results, and the platforms affected, so you're all clued in.

The Nitty-Gritty: Steps to Reproduce the Issue

Okay, so here's how you can trigger this "Not Here" error. Think of it like a recipe; if you follow these steps, you'll see the same issue. This is crucial for anyone trying to reproduce the bug to understand how it happens.

Launch the App: Start by opening the Expensify app. This is our starting point. We're assuming you've got the latest version of the app installed. If not, make sure you update!
Use Expensifail Accounts to Log In: Use expensifail accounts to login. These test accounts are the go-to for simulating scenarios.
User B Creates a Workspace Report: Login as User B and create a report within a workspace. The report is where the expenses are tracked.
User A Merges Accounts with User B: Log in as User A and merge your account with User B's account. Account merging is where the problem starts brewing.
Sign Out as User A: Log out as User A. Make sure you fully log out.
Log In as User B: Log back in as User B.
Open an Archived Chat: Open an archived chat. The chat should contain the report.
Access the Empty Report: Open the empty report. This is where you'll be adding the expenses.
Click "Add Expense": Finally, click on the "Add Expense" button, and this is where the "Not Here" page should appear.

Following these steps carefully allows you to reproduce the bug and understand the sequence of actions that cause the issue.

Expected vs. Actual Results: What's Going Wrong?

So, what's supposed to happen versus what's actually happening? Let's clarify the contrast.

Expected Result: The "Add Expense" button shouldn't even be visible in this scenario. Users are not supposed to be able to add expenses in this case.
Actual Result: Clicking the "Add Expense" button takes you to a "Not Here" page. Clearly, something went wrong, and the expected behavior wasn't delivered.

The difference between the two is really the crux of the problem. Users see a page that isn't supposed to be there. And this error can be frustrating because it interrupts the flow of the app.

Platforms Affected: Where is this Bug Popping Up?

Here's the breakdown of where this bug is showing up:

Windows: Chrome: The primary platform affected is Windows using the Chrome browser. This indicates that users on Windows who use Chrome will likely encounter the bug.

This information is vital for developers and testers to focus their efforts on the specific platforms where the issue is most prevalent. It helps prioritize the bug fix and ensure it reaches the most impacted users first.

Delving Deeper: The Core of the Problem

Let's get into the why behind the "Not Here" error. After the account merge, the system likely misinterprets the report's status or the user's permissions, leading it to display the wrong page. Account merging can be a complex process, and it often involves updating user data and report settings. When these updates don't go smoothly, you get errors like this.

There may be several underlying causes:

Data Synchronization Issues: The account merge process might not fully synchronize all the necessary data related to the report and user permissions. For example, some report flags or user roles may not be updated correctly after the merge.
Incorrect Permissions: The system could be incorrectly assigning permissions to the user. Perhaps the code doesn't recognize the user's new status or the new report owner, leading to the "Not Here" page. These permissions issues are common, particularly when dealing with merged accounts.
Cache Problems: The app might be using cached data that hasn't been updated after the merge. Cache issues can show old data even when the back-end servers have the correct information. The older data can lead the app to make wrong decisions about navigation and display.
Logic Errors in Report Handling: There might be an error in the logic that handles expense reports after a merge. The system might be failing to correctly identify the merged user as the owner or authorized user of the report.

These potential causes highlight how the account merge process, if it's not perfectly executed, can break core app functions.

The Impact of the Bug on Users

This bug significantly impacts the user experience. Imagine trying to manage expenses, and you get a "Not Here" page instead of being able to add new expenses. This kind of experience:

Creates Frustration: Users get annoyed when the app doesn't work as expected. They might think they did something wrong or that the app is broken. This can damage user satisfaction.
Disrupts Workflow: The "Not Here" error stops users from doing what they need to do—in this case, adding expenses to a report. It blocks the normal course of their work.
Undermines Trust: When users consistently encounter errors, they start to lose trust in the app. They may question the reliability of the platform for their financial tasks.
Causes Confusion: The "Not Here" error message isn't helpful; it doesn't explain what went wrong or how to fix it. This creates confusion for users. They may have to spend extra time figuring out what's happening or contacting support.

The overall result is a bad experience that damages user engagement and potentially drives users away.

Possible Workarounds (For Now)

Unfortunately, the bug report doesn't include any workarounds. It's tough when you're stuck and can't add expenses. However, here are some potential temporary solutions that users could try:

Restart the App: Close the app completely and reopen it. This can sometimes clear temporary glitches or cached data.
Check Account Status: Make sure your account merge was successful. Sometimes, retrying the account merge process could resolve the issue.
Contact Support: Reach out to Expensify's support team. They may have a temporary solution or know when the bug is expected to be fixed.

These workarounds are not guaranteed to work, but they might help a user deal with the problem in the short term.

The Road Ahead: Fixing the Bug

Developers will need to investigate the code that handles account merges, user permissions, and report functionality. Here are the likely steps:

Reproduce the Bug: Developers must first verify they can reproduce the issue following the steps. This ensures everyone's on the same page.
Code Review: They'll have to examine the relevant code for potential errors. They will pay extra attention to how user data and permissions are updated during account merges.
Debugging: Use debugging tools to track down the exact point where the error occurs. They will check how the app is handling the user's actions.
Implement a Fix: Write code to fix the problem. This might involve updating the logic for handling user permissions or correctly identifying the report's status after an account merge.
Testing: Thorough testing will be essential to ensure the fix resolves the issue and doesn't introduce new problems. This includes unit tests and integration tests.
Deployment: Deploy the fix to production after testing. The fix should resolve the "Not Here" error and restore the functionality of the "Add Expense" button.

The development team will likely also need to review the app's overall account merging process to prevent similar issues from appearing again in the future.

Conclusion: A Bug That Needs Immediate Attention

This bug report highlights a real problem affecting users' ability to manage expenses after an account merge. It needs prompt attention from the developers. The impact on users is immediate, potentially causing confusion, frustration, and disrupting workflows. By understanding the steps, the expected versus the actual results, and the platforms affected, the development team has a clear path to resolving the issue. The goal is simple: to ensure a smooth, functional experience for all users of the app. Let's get this fixed, team!