Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fixes width/height extraction with respect to exif orientation tag #14996

Merged
merged 8 commits into from
Feb 10, 2023

Conversation

alexxxwork
Copy link
Contributor

@alexxxwork alexxxwork commented Feb 9, 2023

Details

Expensify uses react-native-fast-image and added a patch to be able to get dimensions of the image displayed in the component on an onLoad event. But this method doesn't work correctly with images that have an exif property of image orientation. In such cases image is displayed properly (rotated according to the exif orientation flag) but dimensions returned from react-native-fast-image component are wrong (width/height swapped).
To resolve this propblem we should add an exif reader to get orientation tag and correct dimensions in such cases.

Fixed Issues

$ #14448
$ #14448 (comment)

Tests

  1. Launch the app
  2. Login with any account
  3. Go to any chat
  4. Tap on plus button
  5. Select Add Attachment
  6. Select Take a photo
  7. Take a photo and send it
  • Verify that no errors appear in the JS console
  • Picture should be displayed in full size
  • upload image from iOS camera and preview in android
  • upload image from iOS gallery and preview in android
  • upload image from web and preview in android
  • upload image from android camera and preview in all platforms
  • upload image from android gallery and preview in all platforms

Offline tests

  1. Go to a chat with previously uploaded pictures
  2. Pictures should be displayed in full size

QA Steps

  1. Launch the app
  2. Login with any account
  3. Go to any chat
  4. Tap on plus button
  5. Select Add Attachment
  6. Select Take a photo
  7. Take a photo and send it
  • Verify that no errors appear in the JS console
  • Picture should be displayed in full size
  • upload image from iOS camera and preview in android
  • upload image from iOS gallery and preview in android
  • upload image from web and preview in android
  • upload image from android camera and preview in all platforms
  • upload image from android gallery and preview in all platforms

PR Author Checklist

  • I linked the correct issue in the ### Fixed Issues section above
  • I wrote clear testing steps that cover the changes made in this PR
    • I added steps for local testing in the Tests section
    • I added steps for the expected offline behavior in the Offline steps section
    • I added steps for Staging and/or Production testing in the QA steps section
    • I added steps to cover 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 tested this PR with a High Traffic account against the staging or production API to ensure there are no regressions (e.g. long loading states that impact usability).
  • I included screenshots or videos for tests on all platforms
  • I ran the tests on all platforms & verified they passed on:
    • Android / native
    • Android / Chrome
    • iOS / native
    • iOS / Safari
    • MacOS / Chrome / Safari
    • MacOS / Desktop
  • I verified there are no console errors (if there's a console error not related to the PR, report it or open an issue for it to be fixed)
  • I followed proper code patterns (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 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
      • If any non-english text was added/modified, I verified the translation was requested/reviewed in #expensify-open-source and it was approved by an internal Expensify engineer. Link to Slack message:
    • 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 correct English and approved by marketing by adding the Waiting for Copy label for a copy review on the original GH to get the correct copy.
    • 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 followed the guidelines as stated in the Review Guidelines
  • I tested other components that can be impacted by my changes (i.e. if the PR modifies a shared library or component like Avatar, I verified the components using Avatar are working as expected)
  • 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
  • I verified that if a function's arguments changed that all usages have also been updated correctly
  • 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(themeColors.componentBG)
  • 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 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.
  • I have checked off every checkbox in the PR author checklist, including those that don't apply to this PR.

Screenshots/Videos

Web image
Mobile Web - Chrome

Screenshot_20230210_030608_Chrome

Mobile Web - Safari

screen_web_ios

Desktop image
iOS

screen_ios

Android

Screenshot_20230210_040127_New Expensify

@alexxxwork alexxxwork requested a review from a team as a code owner February 9, 2023 20:05
@github-actions
Copy link
Contributor

github-actions bot commented Feb 9, 2023

CLA Assistant Lite bot All contributors have signed the CLA ✍️ ✅

@melvin-bot melvin-bot bot requested review from grgia and removed request for a team February 9, 2023 20:06
@MelvinBot
Copy link

@grgia 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]

@alexxxwork
Copy link
Contributor Author

I have read the CLA Document and I hereby sign the CLA

@0xmiros
Copy link
Contributor

0xmiros commented Feb 10, 2023

@alexxxwork please let us know when PR is ready for review.
Also, please make sure to follow PR template exactly from next time. Reviewers are not linked correctly. pullerbear should have correctly assigned @mountiny and me as reviewers.

@alexxxwork alexxxwork marked this pull request as draft February 10, 2023 09:59
@alexxxwork
Copy link
Contributor Author

@alexxxwork please let us know when PR is ready for review. Also, please make sure to follow PR template exactly from next time. Reviewers are not linked correctly. pullerbear should have correctly assigned @mountiny and me as reviewers.

Seems like a don't have enough rights to request review from specific persons. Should I just mention desired reviewers @mountiny @0xmiroslav? The PR is ready for review

@alexxxwork alexxxwork marked this pull request as ready for review February 10, 2023 10:29
@0xmiros
Copy link
Contributor

0xmiros commented Feb 10, 2023

@alexxxwork I believe you didn't comment like this. Can you share your screenshot on editing state?
template

@alexxxwork
Copy link
Contributor Author

@alexxxwork I believe you didn't comment like this. Can you share your screenshot on editing state? template

Do you mean that mention in comment above details header?

<!-- If necessary, assign reviewers that know the area or changes well. Feel free to tag any additional reviewers you see fit. @mountiny @0xmiroslav  -->
### Details

### Fixed Issues
<!---
1. Please replace GH_LINK with a URL link to the GitHub issue this Pull Request is fixing.
2. Please replace PROPOSAL: GH_LINK_ISSUE(COMMENT) with a URL link to your GitHub comment, which contains the approved proposal (i.e. the proposal that was approved by Expensify).

Do NOT add the special GH keywords like `fixed` etc, we have our own process of managing the flow.
It MUST be an entire link to the github issue and your comment proposal ; otherwise, the linking will not work as expected.

Make sure this section looks similar to this (you can link multiple issues using the same formatting, just add a new line):

$ https://github.com/Expensify/App/issues/<number-of-the-issue>
$ https://github.com/Expensify/App/issues/<number-of-the-issue(comment)>

Do NOT only link the issue number like this: $ #<number-of-the-issue>
--->
$ [#14448](https://github.com/Expensify/App/issues/14448)   
PROPOSAL: [#14448 (comment)](https://github.com/Expensify/App/issues/14448#issuecomment-1422330478)

@0xmiros
Copy link
Contributor

0xmiros commented Feb 10, 2023

@alexxxwork ok so that's the issue. Automation didn't work because you didn't follow template.

- $ [#14448](https://github.com/Expensify/App/issues/14448) 
+ $ https://github.com/Expensify/App/issues/14448

I understand this is your first PR but from next job, please follow template correctly.

@alexxxwork alexxxwork marked this pull request as draft February 10, 2023 10:46
@alexxxwork
Copy link
Contributor Author

@alexxxwork ok so that's the issue. Automation didn't work because you didn't follow template.

- $ [#14448](https://github.com/Expensify/App/issues/14448) 
+ $ https://github.com/Expensify/App/issues/14448

I understand this is your first PR but from next job, please follow template correctly.

🤦 Thought that this automation worked correctly as long as the link to PR appeared in the issue.

@alexxxwork alexxxwork marked this pull request as ready for review February 10, 2023 10:48
@alexxxwork
Copy link
Contributor Author

alexxxwork commented Feb 10, 2023

@alexxxwork ok so that's the issue. Automation didn't work because you didn't follow template.

- $ [#14448](https://github.com/Expensify/App/issues/14448) 
+ $ https://github.com/Expensify/App/issues/14448

I understand this is your first PR but from next job, please follow template correctly.

@0xmiroslav should I recreate this PR to trigger correct assignment?

@0xmiros
Copy link
Contributor

0xmiros commented Feb 10, 2023

@0xmiroslav should I recreate this PR to trigger correct assignment?

As I said, no need anymore for this PR. But don't repeat the same mistake from next PR for the next job.

@0xmiros
Copy link
Contributor

0xmiros commented Feb 10, 2023

Typo in Tests step:
Log i with expensifail account -> Login with any account

@mountiny
Copy link
Contributor

@alexxxwork no problem as @0xmiroslav mentioned the issue needs to be linked exactly as the template says to make this work.

Can you also fill out the details section with some summary of what are we doing here?

Also will we make an upstream PR?

@0xmiros
Copy link
Contributor

0xmiros commented Feb 10, 2023

Also will we make an upstream PR?

@mountiny this is not upstream issue as I stated here. So the issue came from patch itself and it makes sense to fix in patch itself too.

@mountiny
Copy link
Contributor

@0xmiroslav oh sorry, thanks for the link! Thank you 🙇

@alexxxwork
Copy link
Contributor Author

Can you also fill out the details section with some summary of what are we doing here?

@mountiny updated details

@0xmiros
Copy link
Contributor

0xmiros commented Feb 10, 2023

@alexxxwork please replace with this file and commit again
react-native-fast-image+8.6.3.patch

@alexxxwork
Copy link
Contributor Author

@alexxxwork please replace with this file and commit again react-native-fast-image+8.6.3.patch

Seems to be ok now

Copy link
Contributor

@mountiny mountiny left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looking good so far!

@0xmiros
Copy link
Contributor

0xmiros commented Feb 10, 2023

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 / Chrome
    • iOS / native
    • iOS / 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 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 correct English and approved by marketing by adding the Waiting for Copy label for a copy review on the original GH to get the correct copy.
    • 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(themeColors.componentBG)
  • 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 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.
  • I have checked off every checkbox in the PR reviewer checklist, including those that don't apply to this PR.

Screenshots/Videos

Web
web.mov
Mobile Web - Chrome
mchrome.mp4
Mobile Web - Safari
msafari.mp4
Desktop
desktop.mov
iOS
ios.mp4
Android

Before:

android-old.mov

After:

android.mp4

Copy link
Contributor

@0xmiros 0xmiros left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

windows

mac.rotate1.mov
mac.rotate2.mov

tested various cases: windows/mac images rotation, android/iOS camera/gallery portrait/landscape images and all look good.
I attached before-fix and after-fix videos in Android Screenshots. All other platforms look same between before-fix and after-fix.

Copy link
Contributor

@mountiny mountiny left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@0xmiroslav I do appreciate your thorough testing here!

@alexxxwork Congratulations, you first PR done, onwards and upwards 😍

@mountiny mountiny merged commit da3494a into Expensify:main Feb 10, 2023
@OSBotify
Copy link
Contributor

✋ 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
Copy link
Contributor

🚀 Deployed to staging by https://github.com/mountiny in version: 1.2.70-0 🚀

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

1 similar comment
@OSBotify
Copy link
Contributor

🚀 Deployed to staging by https://github.com/mountiny in version: 1.2.70-0 🚀

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

@OSBotify
Copy link
Contributor

🚀 Deployed to staging by https://github.com/mountiny in version: 1.2.70-0 🚀

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

@OSBotify
Copy link
Contributor

🚀 Deployed to production by https://github.com/francoisl in version: 1.2.70-1 🚀

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants