You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Submit Expense - PDF files can not be added to scan expense on mobile apps #40486
Version Number: 1.4.63-0 Reproducible in staging?: y Reproducible in production?: n Issue found when executing PR:#36314 Issue reported by: Applause - Internal Team
Action Performed:
Launch new expensify
Tap on the fab button and Submit Expense
Tap on Scan tab
Tap on image icon and Choose document
Add a PDF file
Expected Result:
The PDF file can be added to the scan receipt and the next part of the flow appears without issues
Actual Result:
An error message appears blocking the user from adding a PDF file for scanning
Workaround:
n/a
Platforms:
Which of our officially supported platforms is this issue occurring on?
👋 Friendly reminder that deploy blockers are time-sensitive ⏱ issues! Check out the open `StagingDeployCash` deploy checklist to see the list of PRs included in this release, then work quickly to do one of the following:
Identify the pull request that introduced this issue and revert it.
Activity
melvin-bot commentedon Apr 18, 2024
Triggered auto assignment to @blimpich (
DeployBlockerCash), see https://stackoverflowteams.com/c/expensify/questions/9980/ for more details.github-actions commentedon Apr 18, 2024
👋 Friendly reminder that deploy blockers are time-sensitive ⏱ issues! Check out the open `StagingDeployCash` deploy checklist to see the list of PRs included in this release, then work quickly to do one of the following:
Krishna2323 commentedon Apr 18, 2024
This is fixed in this PR.
blimpich commentedon Apr 18, 2024
Not a blocker, since its likely already fixed by a PR that hasn't been deployed to staging yet, and is also not a huge bug.
I will retest this once #40351 has been deployed to staging and confirm that it is fixed.
blimpich commentedon Apr 22, 2024
Not overdue, still waiting for that PR to be deployed to staging and ideally production before retesting this and closing.
melvin-bot commentedon Apr 25, 2024
@blimpich Uh oh! This issue is overdue by 2 days. Don't forget to update your issues!
blimpich commentedon Apr 25, 2024
Is fixed in staging now, just tested.