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 82 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
return (
<MoneyRequestParticipantsSelector
iouType={CONST.IOU.TYPE.SUBMIT}
onFinish={() => {}}
Copy link
Contributor

Choose a reason for hiding this comment

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

MoneyRequestParticipantsSelector is a memoized component, and passing an anonymous function makes it rerender always, because its reference will change

callback.invoke(e.toString(), null)
}
}
}
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 a lot of components with missing last line 😄

@@ -0,0 +1,19 @@
package com.expensify.chat.intentHandler
Copy link
Contributor

Choose a reason for hiding this comment

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

Minor thing but Java package names are typically all lowercase 😄

Suggested change
package com.expensify.chat.intentHandler
package com.expensify.chat.intenthandler

Comment on lines +46 to +49
(intent.getParcelableExtra<Uri>(Intent.EXTRA_STREAM))?.let { fileUri ->
if (fileUri == null) {
return
}
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 this is redundant, since ?.let should make sure that fileUri exists

Comment on lines +55 to +58
val sharedPreferences = context.getSharedPreferences(IntentHandlerConstants.preferencesFile, Context.MODE_PRIVATE)
val editor = sharedPreferences.edit()
editor.putString(IntentHandlerConstants.shareObjectProperty, shareFileObject.toString())
editor.apply()
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 this is duplicated in handleTextPlanIntent, can we extract it to a separate method?

Comment on lines +31 to +33
route: {
params: {reportID},
},
Copy link
Contributor

Choose a reason for hiding this comment

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

Is this common pattern across the App to deconstruct params like that?

Comment on lines +48 to +68
if (unknownUserDetails) {
optimisticReport.reportID = unknownUserDetails?.accountID?.toString() ?? '';
displayReport.participantsList = [{...unknownUserDetails, displayName: unknownUserDetails.login, accountID: unknownUserDetails.accountID ?? CONST.DEFAULT_NUMBER_ID}];
}

if (!onyxReport || onyxReport?.ownerAccountID === 0) {
const participants = onyxReport
? ReportUtils.getDisplayNamesWithTooltips(
OptionsListUtils.getPersonalDetailsForAccountIDs(
Object.keys(onyxReport?.participants ?? {})
.map((p) => parseInt(p ?? '', 10))
.filter((u) => u !== currentUserID),
personalDetails,
),
false,
)
: displayReport.participantsList;
const participant = participants?.filter((u) => u.accountID !== currentUserID).at(0);
displayReport.text = participant?.displayName;
displayReport.alternateText = participant?.login;
}
Copy link
Contributor

@jnowakow jnowakow Dec 20, 2024

Choose a reason for hiding this comment

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

Has it to be done on each render? It seems like manipulating data that will be displayed so it looks like asking for troubles. It's also interesting that react-compiler eslint rule isn't complaining about it.

Comment on lines +808 to +810
option.isDisabled = true;
option.selected = false;
option.isSelected = false;
Copy link
Contributor

Choose a reason for hiding this comment

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

This rather should be set in createOption

width?: number;
};

type FileObject = Partial<File | ImagePickerResponse>;
Copy link
Contributor

Choose a reason for hiding this comment

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

Is this type necessary? You only use file.name in this component and create object of that type maunaly

Comment on lines +38 to +45
const file = useMemo<FileObject | undefined>(() => {
const originalFileName: string = source.split('/').pop() ?? '';
return originalFileName
? {
name: originalFileName,
}
: undefined;
}, [source]);
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 you don't have to construct object with one property here. Something like this works better I think:

    const fileName = source.split('/').pop() ?? '';

Even useMemo is not necessary because it's not heavy operation

Comment on lines +6 to +7
override fun toString(): String {
return Gson().toJson(this)
Copy link
Contributor

Choose a reason for hiding this comment

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

Do we need to add library for handling json for this line? Wouldn't it be easier just to do something like:

    override fun toString(): String {
        return "{\"content\": ${content}, \"mimeType\": ${mimeType}}"

Comment on lines +29 to +31
for (file in files) {
file.delete()
}
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 we should add a check if files exist, otherwise in case of some problems we may get a NullPointerException

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.

I did the native side for now 😄 In general great job! I just pointed out some thing that came up on the way that we can improve

}

fun clearInternalStorageDirectory(context: Context) {
val internalStorageDirectory = File(context.filesDir.absolutePath, directoryName)
Copy link
Contributor

Choose a reason for hiding this comment

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

Maybe we can reuse the getInternalStorageDirectory here?

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

Choose a reason for hiding this comment

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

Is lateinit necessary here? I think we could just return the correct value


// Check if filename contains "text_to_read"
if ([fileName containsString:@"text_to_read"]) {
NSError *fileError = nil;
Copy link
Contributor

Choose a reason for hiding this comment

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

Suggested change
NSError *fileError = nil;
NSError *fileError;


NSTimeInterval timestampInterval = [[NSDate date] timeIntervalSince1970] * 1000;
NSString *timestamp = [NSString stringWithFormat:@"%.0f", timestampInterval];
NSString *identifier = [NSString stringWithFormat:@"%@_%@", (unsigned long)timestamp, filePath];
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 that unsigned long interpolation isn't needed here. i may be wrong though 😄


RCT_EXPORT_MODULE(RCTShareActionHandlerModule);

RCT_EXPORT_METHOD(processFiles:(RCTResponseSenderBlock)callback)
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 this method is pretty long and has many responsibilities. Could we split it a bit for the readability?

NSURL *sharedFilesFolderPathURL = [groupURL URLByAppendingPathComponent:ShareExtensionFilesKey];
NSString *sharedFilesFolderPath = [sharedFilesFolderPathURL path];

[defaults setObject:NULL forKey:ShareExtensionFilesKey];
Copy link
Contributor

Choose a reason for hiding this comment

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

NULL in Objective-C is used rather to inform that there is no pointer. In this case we should use nil instead, or even better:

Suggested change
[defaults setObject:NULL forKey:ShareExtensionFilesKey];
[defaults removeObjectForKey:ShareExtensionFilesKey];

Comment on lines +154 to +181
else if let url = data as? NSURL, let fileData = NSData(contentsOf: url as URL) {
guard let filename = url.lastPathComponent else {
completion(.CouldNotLoad)
return
}
if let fileFinalPath = self.saveFileToFolder(folder: folder, filename: filename, fileData: fileData) {
completion(nil)
}
else {
os_log("Skipping file %@, failed to save", type: .error, String(describing: filename) as CVarArg) // Safe typecasting
completion(.CouldNotLoad)
}
// Try to get file as UIFile. This is the case when extension is run from screenshot editor.
}
else if let file = data as? UIImage, let fileData = file.pngData() as NSData? {
let filename = "shared_image.png"
if let fileFinalPath = self.saveFileToFolder(folder: folder, filename: filename, fileData: fileData) {
completion(nil)
}
else {
os_log("Skipping file %@, failed to save", type: .error, filename as CVarArg)
completion(.CouldNotLoad)
}
}
else {
os_log("Received data of unhandled type", type: .error)
completion(.URLError)
}
Copy link
Contributor

Choose a reason for hiding this comment

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

I see some data repetition that could be avoided 😄

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