Skip to content

mWeb - CVP - Camera permission asking reappears after back navigation to retake a photo #86269

Closed

Description

@jponikarchuk

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: v9.3.43-0
Reproducible in staging?: Yes
Reproducible in production?: Yes
If this was caught during regression testing, add the test name, ID and link from BrowserStack: https://test-management.browserstack.com/projects/2219752/folder/13176724/test-cases/41237070
Email or phone of affected tester (no customers): agexptest+cvp240326@gmail.com
Issue reported by: Applause Internal Team
Bug source: Exploratory - Significant User Experience Deterioration
Device used: Samsung S23FE/ Android 16, iPhone 13 Mini/ iOS 26.3
App Component: Money Requests

Action Performed:

Preconditions:
Create a new account with a Gmail address in staging.expensify.com by selecting "Organize my own expenses".
In ND, select "Get paid back from my employer" from the intent selector.
Remove camera access from Expensify on the mobile browser level.
These steps must be executed on a mobile browser.

  1. Go to https://staging.new.expensify.com/
  2. Tap on FAB > Create expense
  3. Tap on Continue > Allow while visiting the site
  4. Take a photo of a valid receipt
  5. Complete with any recipient
  6. Complete with any description
  7. Tap on the left arrow to go back to the scan receipt page

Expected Result:

The camera is still enabled and ready to retake a photo.

Actual Result:

The camera is not enabled, and the permission prompt reappears. After tapping Continue twice, the camera is enabled.

Workaround:

Unknown

Platforms:

  • Android: App
  • Android: mWeb Chrome
  • iOS: App
  • iOS: mWeb Safari
  • iOS: mWeb Chrome
  • Windows: Chrome
  • MacOS: Chrome / Safari

Screenshots/Videos

Video.mp4

View all open jobs on GitHub

Activity

  1. melvin-bot commented on Jun 5, 2026

    @melvin-bot

    @jponikarchuk, this Monthly task hasn't been acted upon in 6 weeks; closing.

    If you disagree, feel encouraged to reopen it -- but pick your least important issue to close instead.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions