Issue/36520 android scan second tap on capture button causes error to show up by agent3bood · Pull Request #38320 · Expensify/App

agent3bood · 2024-03-14T15:22:05Z

Details

Follow up on this conversation

This PR fixes a second issue where the user might tap the camera button while navigation has started.

Fixed Issues

$ #36520
PROPOSAL: #36520 (comment)

Tests

Launch New Expensify app
Tap + > Request money
Go to Scan
Tap on the capture button twice
Verify that no errors popup appear in the app

Verify that no errors appear in the JS console

Offline tests

same as tests

QA Steps

Same as tests

PR Author Checklist

Screenshots/Videos

Android: Native

Screen_Recording_20240314-155029_New.Expensify.Dev.mp4

Android: mWeb Chrome

Screen_Recording_20240314-175908_Chrome.mp4

iOS: Native

3BD80AEF-078E-4A3D-9F99-4636FC17DC6B.MP4

iOS: mWeb Safari

RPReplay_Final1710429270.mp4

MacOS: Chrome / Safari

MacOS: Desktop

…apture-button-causes-error-to-show-up

melvin-bot · 2024-03-14T15:22:10Z

@hoangzinh Please copy/paste the Reviewer Checklist from here into a new comment on this PR and complete it. If you have the K2 extension, you can simply click: [this button]

src/pages/iou/request/step/IOURequestStepScan/index.native.js

hoangzinh · 2024-03-18T14:42:42Z

Reviewer Checklist

I have verified the author checklist is complete (all boxes are checked off).
I verified the correct issue is linked in the ### Fixed Issues section above
I verified testing steps are clear and they cover the changes made in this PR
- I verified the steps for local testing are in the Tests section
- I verified the steps for Staging and/or Production testing are in the QA steps section
- I verified the steps cover any possible failure scenarios (i.e. verify an input displays the correct error message if the entered data is not correct)
- I turned off my network connection and tested it while offline to ensure it matches the expected behavior (i.e. verify the default avatar icon is displayed if app is offline)
I checked that screenshots or videos are included for tests on all platforms
I included screenshots or videos for tests on all platforms
I verified tests pass on all platforms & I tested again on:
- Android: Native
- Android: mWeb Chrome
- iOS: Native
- iOS: mWeb Safari
- MacOS: Chrome / Safari
- MacOS: Desktop
If there are any errors in the console that are unrelated to this PR, I either fixed them (preferred) or linked to where I reported them in Slack
I verified proper code patterns were followed (see Reviewing the code)
- I verified that any callback methods that were added or modified are named for what the method does and never what callback they handle (i.e. toggleReport and not onIconClick).
- I verified that the left part of a conditional rendering a React component is a boolean and NOT a string, e.g. myBool && <MyComponent />.
- I verified that comments were added to code that is not self explanatory
- I verified that any new or modified comments were clear, correct English, and explained "why" the code was doing something instead of only explaining "what" the code was doing.
- I verified any copy / text shown in the product is localized by adding it to src/languages/* files and using the translation method
- I verified all numbers, amounts, dates and phone numbers shown in the product are using the localization methods
- I verified any copy / text that was added to the app is grammatically correct in English. It adheres to proper capitalization guidelines (note: only the first word of header/labels should be capitalized), and is either coming verbatim from figma or has been approved by marketing (in order to get marketing approval, ask the Bug Zero team member to add the Waiting for copy label to the issue)
- I verified proper file naming conventions were followed for any new files or renamed files. All non-platform specific files are named after what they export and are not named "index.js". All platform-specific files are named for the platform the code supports as outlined in the README.
- I verified the JSDocs style guidelines (in STYLE.md) were followed
If a new code pattern is added I verified it was agreed to be used by multiple Expensify engineers
I verified that this PR follows the guidelines as stated in the Review Guidelines
I verified other components that can be impacted by these changes have been tested, and I retested again (i.e. if the PR modifies a shared library or component like Avatar, I verified the components using Avatar have been tested & I retested again)
I verified all code is DRY (the PR doesn't include any logic written more than once, with the exception of tests)
I verified any variables that can be defined as constants (ie. in CONST.js or at the top of the file that uses the constant) are defined as such
If a new component is created I verified that:
- A similar component doesn't exist in the codebase
- All props are defined accurately and each prop has a /** comment above it */
- The file is named correctly
- The component has a clear name that is non-ambiguous and the purpose of the component can be inferred from the name alone
- The only data being stored in the state is data necessary for rendering and nothing else
- For Class Components, any internal methods passed to components event handlers are bound to this properly so there are no scoping issues (i.e. for onClick={this.submit} the method this.submit should be bound to this in the constructor)
- Any internal methods bound to this are necessary to be bound (i.e. avoid this.submit = this.submit.bind(this); if this.submit is never passed to a component event handler like onClick)
- All JSX used for rendering exists in the render method
- The component has the minimum amount of code necessary for its purpose, and it is broken down into smaller components in order to separate concerns and functions
If any new file was added I verified that:
- The file has a description of what it does and/or why is needed at the top of the file if the code is not self explanatory
If a new CSS style is added I verified that:
- A similar style doesn't already exist
- The style can't be created with an existing StyleUtils function (i.e. StyleUtils.getBackgroundAndBorderStyle(theme.componentBG)
If the PR modifies code that runs when editing or sending messages, I tested and verified there is no unexpected behavior for all supported markdown - URLs, single line code, code blocks, quotes, headings, bold, strikethrough, and italic.
If the PR modifies a generic component, I tested and verified that those changes do not break usages of that component in the rest of the App (i.e. if a shared library or component like Avatar is modified, I verified that Avatar is working as expected in all cases)
If the PR modifies a component related to any of the existing Storybook stories, I tested and verified all stories for that component are still working as expected.
If the PR modifies a component or page that can be accessed by a direct deeplink, I verified that the code functions as expected when the deeplink is used - from a logged in and logged out account.
If the PR modifies the UI (e.g. new buttons, new UI components, changing the padding/spacing/sizing, moving components, etc) or modifies the form input styles:
- I verified that all the inputs inside a form are aligned with each other.
- I added Design label and/or tagged @Expensify/design so the design team can review the changes.
If a new page is added, I verified it's using the ScrollView component to make it scrollable when more elements are added to the page.
If the main branch was merged into this PR after a review, I tested again and verified the outcome was still expected according to the Test steps.
I have checked off every checkbox in the PR reviewer checklist, including those that don't apply to this PR.

Screenshots/Videos

Android: Native

Screen.Recording.2024-03-18.at.21.53.24.android.mov

Android: mWeb Chrome

Screen.Recording.2024-03-18.at.21.56.23.android.chrome.mov

iOS: Native

Screen.Recording.2024-03-18.at.21.57.40.ios.mov

iOS: mWeb Safari

Screen.Recording.2024-03-18.at.21.58.18.ios.safari.mov

MacOS: Chrome / Safari

Screen.Recording.2024-03-18.at.21.45.53.web.mov

MacOS: Desktop

Screen.Recording.2024-03-18.at.21.47.40.desktop.mov

techievivek · 2024-03-20T05:54:50Z

Ooops, extremely sorry for the delay here. We seem to have some conflicts. @agent3bood can you please resolve it and I will review this ASAP. Thanks.

…apture-button-causes-error-to-show-up

agent3bood · 2024-03-20T15:02:25Z

Conflicts resolved, tested again and it is working fine.

agent3bood · 2024-03-26T11:38:54Z

@techievivek any updates on when this PR can be merged? It is ready and approved.

techievivek · 2024-04-01T04:51:59Z

Sorry once again. I was ooo last week, so I couldn't get to this earlier, and there are new conflicts. Can you please fix them I will merge them ASAP.

…apture-button-causes-error-to-show-up # Conflicts: # src/pages/iou/request/step/IOURequestStepScan/index.native.js

agent3bood · 2024-04-01T14:08:45Z

@techievivek done 🆗

…apture-button-causes-error-to-show-up # Conflicts: # src/pages/iou/request/step/IOURequestStepScan/index.native.js

OSBotify · 2024-04-03T03:39:46Z

✋ This PR was not deployed to staging yet because QA is ongoing. It will be automatically deployed to staging after the next production release.

OSBotify · 2024-04-08T10:54:23Z

🚀 Deployed to production by https://github.com/Julesssss in version: 1.4.60-13 🚀

platform	result
🤖 android 🤖	success ✅
🖥 desktop 🖥	success ✅
🍎 iOS 🍎	success ✅
🕸 web 🕸	success ✅

agent3bood added 2 commits March 13, 2024 23:36

lock capturePhoto

f44142d

Merge branch 'main' into issue/36520-Android---Scan---Second-tap-on-c…

e9df9d5

…apture-button-causes-error-to-show-up

agent3bood requested a review from a team as a code owner March 14, 2024 15:22

melvin-bot bot requested review from hoangzinh and removed request for a team March 14, 2024 15:22

prettier

0b0847d

hoangzinh reviewed Mar 18, 2024

View reviewed changes

src/pages/iou/request/step/IOURequestStepScan/index.native.js Outdated Show resolved Hide resolved

useFocusEffect

2eaad6f

hoangzinh approved these changes Mar 18, 2024

View reviewed changes

melvin-bot bot requested a review from techievivek March 18, 2024 15:00

agent3bood added 2 commits March 20, 2024 17:23

Merge branch 'main' into issue/36520-Android---Scan---Second-tap-on-c…

9ba821e

…apture-button-causes-error-to-show-up

cleanup

1075405

techievivek assigned agent3bood Apr 1, 2024

agent3bood added 2 commits April 1, 2024 16:10

Merge branch 'main' into issue/36520-Android---Scan---Second-tap-on-c…

26d2437

…apture-button-causes-error-to-show-up # Conflicts: # src/pages/iou/request/step/IOURequestStepScan/index.native.js

cleanup

80d2d26

agent3bood added 3 commits April 1, 2024 23:35

Merge branch 'main' into issue/36520-Android---Scan---Second-tap-on-c…

ec9e146

…apture-button-causes-error-to-show-up # Conflicts: # src/pages/iou/request/step/IOURequestStepScan/index.native.js

Merge branch 'main' into issue/36520-Android---Scan---Second-tap-on-c…

1141f4d

…apture-button-causes-error-to-show-up # Conflicts: # src/pages/iou/request/step/IOURequestStepScan/index.native.js

cleanup

8f820e1

techievivek approved these changes Apr 3, 2024

View reviewed changes

techievivek merged commit 879378f into Expensify:main Apr 3, 2024

github-actions bot mentioned this pull request Apr 4, 2024

[INCORRECT] (used to be a checklist but was incorrectly triggered) #39573

Closed

44 tasks

mountiny mentioned this pull request Apr 4, 2024

Deploy Checklist: New Expensify 2024-04-04 #39588

Closed

48 tasks

melvin-bot bot mentioned this pull request Apr 8, 2024

[C+ Checklist Needs Completion] [$500] Android - Scan - Second tap on capture button causes error to show up #36520

Closed

6 tasks

QichenZhu mentioned this pull request Oct 15, 2024

[HOLD for payment 2024-11-05] [$250] IOU - mWeb - User trying to upload receipt by quickly tapping capture button shows error #50083

Closed

6 tasks

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Issue/36520 android scan second tap on capture button causes error to show up#38320

Issue/36520 android scan second tap on capture button causes error to show up#38320
techievivek merged 11 commits intoExpensify:mainfrom
agent3bood:issue/36520-Android---Scan---Second-tap-on-capture-button-causes-error-to-show-up

agent3bood commented Mar 14, 2024 •

edited

Loading

Uh oh!

melvin-bot bot commented Mar 14, 2024

Uh oh!

Uh oh!

hoangzinh commented Mar 18, 2024 •

edited

Loading

Uh oh!

techievivek commented Mar 20, 2024

Uh oh!

agent3bood commented Mar 20, 2024

Uh oh!

agent3bood commented Mar 26, 2024

Uh oh!

techievivek commented Apr 1, 2024

Uh oh!

agent3bood commented Apr 1, 2024

Uh oh!

OSBotify commented Apr 3, 2024

Uh oh!

OSBotify commented Apr 8, 2024

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

4 participants

Conversation

agent3bood commented Mar 14, 2024 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Details

Fixed Issues

Tests

Offline tests

QA Steps

PR Author Checklist

Screenshots/Videos

Uh oh!

melvin-bot bot commented Mar 14, 2024

Uh oh!

Uh oh!

hoangzinh commented Mar 18, 2024 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Reviewer Checklist

Screenshots/Videos

Uh oh!

techievivek commented Mar 20, 2024

Uh oh!

agent3bood commented Mar 20, 2024

Uh oh!

agent3bood commented Mar 26, 2024

Uh oh!

techievivek commented Apr 1, 2024

Uh oh!

agent3bood commented Apr 1, 2024

Uh oh!

OSBotify commented Apr 3, 2024

Uh oh!

OSBotify commented Apr 8, 2024

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

4 participants

agent3bood commented Mar 14, 2024 •

edited

Loading

hoangzinh commented Mar 18, 2024 •

edited

Loading