search

Expensify / App

Welcome to New Expensify: a complete re-imagination of financial collaboration, centered around chat. Help us build the next generation of Expensify by sharing feedback and contributing to the code.
https://new.expensify.com
MIT License
3.42k stars 2.8k forks source link

Onboarding tasks - Blank attachment screen is displayed after onboarding video ends #50179

Open isagoico opened 2 hours ago

isagoico commented 2 hours ago

If you haven’t already, check out our contributing guidelines for onboarding and email contributors@expensify.com to request to join our Slack channel!

Version Number: 9.0.44-0 Reproducible in staging?: Yes Reproducible in production?: Yes If this was caught during regression testing, add the test name, ID and link from TestRail: Bottom UP - New user searches for Expensify and can create a new account

Issue reported by: Applause - Internal team

Action Performed:

  1. Create a new account in ND
  2. On the onboarding menu, tap on "Get paid back from my employer"
  3. Input any name and tap on the "Continue" button
  4. Tap on "Concierge"
  5. Tap on the video
  6. Wait until the video ends

Expected Result:

Video preview could be loading again, or the user could be dropped to Concierge after finishing the video.

Actual Result:

Blank attachment screen is displayed after "Submit video" ends.

Workaround:

Can the user still use Expensify without this being fixed? Have you informed them of the workaround?

Platforms:

Which of our officially supported platforms is this issue occurring on?

Screenshots/Videos

Issue seen at second 55 of the video. https://github.com/user-attachments/assets/6aba42d2-d799-4b87-938c-ce4686cca3a3

View all open jobs on GitHub

This was found when executing the newly added flows for CVP here https://github.com/Expensify/Expensify/issues/412920. CC @JmillsExpensify

melvin-bot[bot] commented 2 hours ago

Triggered auto assignment to @VictoriaExpensify (Bug), see https://stackoverflow.com/c/expensify/questions/14418 for more details. Please add this bug to a GH project, as outlined in the SO.