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

Share extension Android and iOS implementation #54354

Draft
wants to merge 120 commits into
base: main
Choose a base branch
from

Conversation

Guccio163
Copy link
Contributor

Details

This PR introduces the implementation of Share Extension for mobile apps both for Android and iOS.

Fixed Issues

$#48788
$#48789
PROPOSAL:

Tests

Share test:

  1. Choose a text/file to share from gallery/file manager on device
  2. Select 'Expensify' as the target application to share to
  3. Choose 'Share' tab
  4. Choose a recipient/workspace to share to
  5. Check if 'Share Details' page displays correctly, specifically attachment's section -
    • no attachment if you shared text
    • file's thumbnail if you shared image/video
    • rectangle with file's name and paperclip icon in the rest of the cases
  6. Check if clicking in image/video thumbnail opens full-size modal with image/video
  7. Enter message
  8. Select 'Share'
  9. Check if shared content was shared successfully (added to chat with recipient or new chat was created)

Submit test:

  1. Choose a file to share from gallery/file manager on device
  2. Select 'Expensify' as the target application to share to
  3. Choose 'Submit' tab (should be available)
  4. Choose a recipient/workspace to share to
  5. Check if 'Submit Details' page displays correctly, specifically attachment's section with file's thumbnail
  6. Add description and save it
  7. Select 'Submit'
  8. Check if shared content was submitted successfully (added to chat with recipient or new chat was created)
  • Verify that no errors appear in the JS console

Offline tests

N/A

QA Steps

N/A

  • 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: mWeb Chrome
    • iOS: Native
    • iOS: mWeb 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 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
      • 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 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 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 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.

Screenshots/Videos

Android: Native
Android: mWeb Chrome
iOS: Native
iOS: mWeb Safari
MacOS: Chrome / Safari
MacOS: Desktop

BrtqKr and others added 30 commits August 28, 2024 13:19
@grgia
Copy link
Contributor

grgia commented Jan 3, 2025

Hmm IOS failed- I'm retrying now. Could you take a look?

Copy link
Contributor

github-actions bot commented Jan 3, 2025

🧪🧪 Use the links below to test this adhoc build on Android, iOS, Desktop, and Web. Happy testing! 🧪🧪

Android 🤖 iOS 🍎
https://ad-hoc-expensify-cash.s3.amazonaws.com/android/54354/index.html ❌ FAILED ❌
Android The QR code can't be generated, because the iOS build failed
Desktop 💻 Web 🕸️
https://ad-hoc-expensify-cash.s3.amazonaws.com/desktop/54354/NewExpensify.dmg https://54354.pr-testing.expensify.com
Desktop Web

👀 View the workflow run that generated this build 👀

@@ -246,6 +246,8 @@ dependencies {
implementation "com.squareup.okhttp3:okhttp-urlconnection:4.+"

implementation("androidx.lifecycle:lifecycle-viewmodel-ktx:2.4.0")

implementation("com.google.code.gson:gson:2.8.8")
Copy link
Contributor

Choose a reason for hiding this comment

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

for SNYK to pass we need to use com.google.code.gson:[email protected]

Copy link
Contributor

Choose a reason for hiding this comment

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

done

@Guccio163
Copy link
Contributor Author

Hi @grgia, I'm returning from OOO tomorrow and already started to check your and Błażej's comments - I'll address all of them in the nearest days!

@grgia
Copy link
Contributor

grgia commented Jan 7, 2025

@Guccio163 beautiful, keep me updated!

@filip-solecki
Copy link
Contributor

filip-solecki commented Jan 8, 2025

Hi @grgia !
The issue with our iOS build is due to the lack of provisioning profiles configured for our ShareViewController. To resolve this, you'll need to add the necessary provisioning profiles to the Apple Developer account and then we can update the Fastfile in the repository accordingly.

@grgia
Copy link
Contributor

grgia commented Jan 8, 2025

@filip-solecki Slack DMd you

Copy link
Contributor

@staszekscp staszekscp left a comment

Choose a reason for hiding this comment

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

Android looks good! I'll continue with iOS after lunch 😄

private fun getInternalStorageDirectory(context: Context): File {
val internalStorageDirectory = File(context.filesDir.absolutePath, directoryName)
if (!internalStorageDirectory.exists()) {
internalStorageDirectory.mkdir()
Copy link
Contributor

Choose a reason for hiding this comment

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

I think it's slightly safer to use mkdirs() here, because in case the parent directory doesn't exist, the command won't fail

* @param context
* @return The absolute path of the image
*/
fun copyUriToStorage(uri: Uri?, context: Context): String? {
Copy link
Contributor

Choose a reason for hiding this comment

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

I think the Uri doesn't have to be optional here, because in handleSingleFileIntent the lambda won't run unless fileUri exists. The same applies to other methods with Uri? like createTemporaryFile and saveFileFromProviderUri - I believe it will make the code much simpler, because we won't have to handle the null scenario in any of them 😄

Copy link
Contributor

@staszekscp staszekscp left a comment

Choose a reason for hiding this comment

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

iOS looking good! Noticed just two minor things!

}

private func handleImageData(_ image: UIImage, folder: URL, completion: @escaping (FileSaveError?) -> Void) {
let filename = "shared_image.png"
Copy link
Contributor

Choose a reason for hiding this comment

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

I noticed that SubmitDetailsPage.tsx we use shared_image.jpg not shared_image.png - not sure if these are related or not, but worth mentioning 😄

Copy link
Contributor

Choose a reason for hiding this comment

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

Great catch, thanks!


private func handleStringData(_ dataString: String, folder: URL, completion: @escaping (FileSaveError?) -> Void) {
if !dataString.hasPrefix("file://") {
let filename = "text_to_read.txt"
Copy link
Contributor

Choose a reason for hiding this comment

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

The text_to_read.txt appears three times, maybe we can extract it to a variable for maintanance. It's a minor one, though 😄

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.

7 participants