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

fix "Downloaded photo is not appearing in the photo album" in android #12033

Merged
merged 9 commits into from
Apr 27, 2023

Conversation

aimane-chnaif
Copy link
Contributor

@aimane-chnaif aimane-chnaif commented Oct 20, 2022

Details

To export file to external storage, we need to follow https://github.com/RonRadtke/react-native-blob-util#copytomediastore.
After export, remove temp file from internal storage.
All files are downloaded in /Download/Expensify folder.
All media (images, photos) can be seen in native Gallery app.

Fixed Issues

$ #11101
PROPOSAL: #11101 (comment)

Tests

  1. Login with any account in android app
  2. Send or receive any attachment in any chat
  3. Open attachment detail
  4. Download
  5. Open native Files app and locate /Download/Expensify
  6. Verify that downloaded file appears in that folder.
    For media (images or videos) only:
  7. Open native Gallery app
  8. Verify that downloaded media appears in list
  • Verify that no errors appear in the JS console

Offline tests

Download not working in offline mode

QA Steps

  1. Login with any account in android app
  2. Send or receive any attachment in any chat
  3. Open attachment detail
  4. Download
  5. Open native Files app and locate /Download/Expensify
  6. Verify that downloaded file appears in that folder.
    For media (images or videos) only:
  7. Open native Gallery app
  8. Verify that downloaded media appears in list
  • Verify that no errors appear in the JS console

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.
  • 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 author 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
android.mp4

@aimane-chnaif aimane-chnaif requested a review from a team as a code owner October 20, 2022 05:41
@melvin-bot melvin-bot bot requested review from parasharrajat and thienlnam and removed request for a team October 20, 2022 05:42
@aimane-chnaif aimane-chnaif requested review from parasharrajat and removed request for thienlnam October 20, 2022 15:13
@aimane-chnaif
Copy link
Contributor Author

I re-requested review from @parasharrajat but it seems github bug that removed request for @thienlnam

Comment on lines 67 to 68
FileUtils.showSuccessAlert();
RNFetchBlob.fs.unlink(attachmentPath);
Copy link
Member

@parasharrajat parasharrajat Oct 20, 2022

Choose a reason for hiding this comment

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

Suggested change
FileUtils.showSuccessAlert();
RNFetchBlob.fs.unlink(attachmentPath);
RNFetchBlob.fs.unlink(attachmentPath);
FileUtils.showSuccessAlert();

let's swap these lines.

Copy link
Member

@parasharrajat parasharrajat left a comment

Choose a reason for hiding this comment

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

Although it is working fine, there is an issue.

BUG: Android: Clicking on the download notification throws error media not found.

Steps:

  1. Send any attachment (image) message.
  2. Click to open the attachment.
  3. Click ⬇️ download icon.
  4. Open notification tray.
  5. Click on the download complete notification.

@aimane-chnaif
Copy link
Contributor Author

BUG: Android: Clicking on the download notification throws error media not found.

@parasharrajat I am not able to reproduce. Can you share your video?

demo.mp4

@aimane-chnaif
Copy link
Contributor Author

BTW, I suggest not to use android download manager.
I tried to download file on android whatsapp and it's not using download manager so our app can be the same.

@parasharrajat
Copy link
Member

BTW, I suggest not to use android download manager.

Why?

I tried to download file on android whatsapp and it's not using download manager so our app can be the same.

Not a good reasoning.

I think it is useful and there is a motive behind using it. But if you think so, feel free to open a slack discussion and explain the problem and reason. Don't forget to share the link here. You can tag me.


Interesting, I can reproduce. Try with an image.

screen-2022-10-26_21.44.29.mp4

@aimane-chnaif
Copy link
Contributor Author

I can reproduce. Try with an image.

@parasharrajat Can you test on physical android device? There might be a problem with emulator storage

@parasharrajat
Copy link
Member

Sure.

@parasharrajat
Copy link
Member

There is a similar problem on the device. The Logical reason is that we are deleting the file after moving to mediasource which was downloaded via the manager.

I think it is useful and there is a motive behind using it. But if you think so, feel free to open a slack discussion and explain the problem and reason. Don't forget to share the link here. You can tag me.

Or we have to find a fix.

@parasharrajat
Copy link
Member

Any update?

@Julesssss
Copy link
Contributor

Julesssss commented Nov 14, 2022

There is a similar problem on the device. The Logical reason is that we are deleting the file after moving to mediasource which was downloaded via the manager.

Pretty certain we'll need to find a fix for this. It should be as simple as hiding the DownloadManager notification. Hopefully the 3rd party library exposes this to us and it should be simple to fix 🤞 -- else I guess we'll need a fork or feature request.

We also need the android.permission.DOWNLOAD_WITHOUT_NOTIFICATION permission, but maybe this will be merged from the 3rd party lib's manifest file 🤷

@parasharrajat
Copy link
Member

Let me bump the thread. We need to plan out the changes here. Simply removing the notification is not a good plan.

  1. Either we remove the notification and create a new issue to find a fix
  2. Or we just find a fix here on this issue?

Note: Removing notifications means we will have to do that for iOS as well to make it consistent.

@parasharrajat
Copy link
Member

@Julesssss Could you please create a new issue we want to implement the notification?

For now, it seems many agree to disable the notification for moving this PR. @aimane-chnaif let's do that for now. Also, same for iOS.

@Julesssss
Copy link
Contributor

Julesssss commented Nov 16, 2022

To move forward we would need an alternative solution for the invalid image URI, else we agree with this workaround and hold this while a custom notification is implemented.

@parasharrajat
Copy link
Member

I don't have access to the slack discussion. Could you please post it here? I am good with holding this.

@Julesssss
Copy link
Contributor

@parasharrajat oops sorry, I pasted the wrong link. Updated.

@aimane-chnaif
Copy link
Contributor Author

For now, it seems many agree to disable the notification for moving this PR. @aimane-chnaif let's do that for now. Also, same for iOS.

Ok, so go ahead with this for now?

@Julesssss
Copy link
Contributor

@aimane-chnaif
Copy link
Contributor Author

The MediaCollection solution only appears to work for newer Android OS versions. On my older device (Android 8.0) the image isn't saved to public storage.

Oh really? I will try to check on lower versions.

@parasharrajat
Copy link
Member

@aimane-chnaif Any update?

@aimane-chnaif
Copy link
Contributor Author

aimane-chnaif commented Apr 23, 2023

Latest update:

Device OS Files app Gallery app Google Photos
Samsung Galaxy S10 12
Samsung Galaxy Tablet A7 12
Nexus 5 (emulator) 8 ❌ (WhatsApp: ✅) ❌ (WhatsApp: ✅)
Google Pixel XL (emulator) 13

Still investigating why it doesn't save on old OS devices, though upstream says it's fixed - Copy file to Download directory in android < 10

I see the notification on both Andorid 8 and Android 13

Btw, download manager notification never shows on any devices.

@Julesssss
Copy link
Contributor

Julesssss commented Apr 26, 2023

From the Google developer site:

Downloaded files, which are stored in the Download/ directory. On devices that run Android 10 (API level 29) and higher, these files are stored in the MediaStore.Downloads table. This table isn't available on Android 9 (API level 28) and lower.

So I'd be interested to see how the upstream lib maintainers achieved this.

@parasharrajat
Copy link
Member

We are still using 0.16.0. I think upgrading might solve this @aimane-chnaif

@aimane-chnaif
Copy link
Contributor Author

We are still using 0.16.0. I think upgrading might solve this @aimane-chnaif

yes I checked version also. They fixed <10 issue on exactly 0.16.0. But still I will retest on latest version today

@parasharrajat
Copy link
Member

@aimane-chnaif Were you able to test it?

@aimane-chnaif
Copy link
Contributor Author

@parasharrajat I confirmed working on latest version - 0.17.3. Tested on Android 8 emulator. Just pushed.
@Julesssss can you please test again on Android 8 real device?

android8.mov

@parasharrajat
Copy link
Member

parasharrajat commented Apr 27, 2023

@aimane-chnaif can you please update POD lock file?

@parasharrajat
Copy link
Member

parasharrajat commented Apr 27, 2023

I am trying on an emulator now with Oreo OS.

Copy link
Member

@parasharrajat parasharrajat left a comment

Choose a reason for hiding this comment

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

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 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 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 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 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.

cc: @Julesssss

🎀 👀 🎀 C+ reviewed

@parasharrajat
Copy link
Member

parasharrajat commented Apr 27, 2023

Tested the following features as well and everything looks good.

  1. Add Attachment
  2. Download attachments of all types.
  3. Upload avatar cropping and save.

Tes devices - Android 8, 13 and IOS 16.2.


I noticed that folder name is different on Android 8 then the Android 13. It is Expensify on Android 13 but DownloadExpensify on android 8. No biggy for me.

@aimane-chnaif
Copy link
Contributor Author

I tried to find solution of replacing DownloadExpensify with Expensify on lower versions but no documenation or no GHs found for that

Copy link
Contributor

@Julesssss Julesssss left a comment

Choose a reason for hiding this comment

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

👍

@Julesssss
Copy link
Contributor

Julesssss commented Apr 27, 2023

I'm ignoring the checklist failure, it matches the provided link and looks good to me

@Julesssss Julesssss merged commit c3fa98d into Expensify:main Apr 27, 2023
@OSBotify
Copy link
Contributor

🚀 Deployed to staging by https://github.com/Julesssss in version: 1.3.7-2 🚀

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

@OSBotify
Copy link
Contributor

🚀 Deployed to production by https://github.com/jasperhuangg in version: 1.3.7-3 🚀

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
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants