-
Notifications
You must be signed in to change notification settings - Fork 3k
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
[Awaiting Payment 2024-01-30] [$2000] We can send an empty message using dictation on iPhone #18121
Comments
Triggered auto assignment to @trjExpensify ( |
Bug0 Triage Checklist (Main S/O)
|
ProposalPlease re-state the problem that we are trying to solve in this issue.We can send an empty message using dictation on iPhone What is the root cause of that problem?We are checking if comment is empty to disable the send button, however the result return from empty dictation in iPhone was a escape character
What changes do you think we should make in order to solve the problem?Add more condition to our isCommentEmpty's regex to prevent such thing. So our regex will look like: isCommentEmpty: !!newComment.match(/^(\s|\ufffc)*$/), What alternative solutions did you explore? (Optional)None. Result:Screen.Recording.2023-04-28.at.10.08.56.mov |
I can reliably reproduce this. Moving on |
Job added to Upwork: https://www.upwork.com/jobs/~01fe24292fbc44e5d8 |
Current assignee @trjExpensify is eligible for the External assigner, not assigning anyone new. |
Triggered auto assignment to Contributor-plus team member for initial proposal review - @Santhosh-Sellavel ( |
Triggered auto assignment to @flodnv ( |
📣 @DmytroDumas! 📣 Hey, it seems we don’t have your contributor details yet! You'll only have to do this once, and this is how we'll hire you on Upwork.
Format:
|
ProposalPlease re-state the problem that we are trying to solve in this issue.We can send an empty message using dictation on iPhone What is the root cause of that problem?When we start using the dictation on the keyboard, the system will automatically generate a What changes do you think we should make in order to solve the problem?Solution A: - onChangeText={comment => this.updateComment(comment, true)}
+ onChangeText={comment => /\uFFFC+/.test(comment) ? null : this.updateComment(comment, true)} Solution B: - disabled={isBlockedFromConcierge || this.props.disabled}
+ disabled={isBlockedFromConcierge || this.props.disabled || /\uFFFC+/.test(this.state.value)} |
React Native is a powerful tool for developing cross-platform mobile apps, and I have extensive experience in working with it. I have encountered similar issues in the past and am confident that I have the skills and expertise to resolve this for you. To fix the issue, we need to disable the send button if the user has not spoken any message. We can achieve this by using the onStartListening and onEndListening methods provided by the dictation library. These methods allow us to track the state of the dictation session, and we can use this information to enable/disable the send button accordingly. Also we can fix as follow code: Contributor details |
✅ Contributor details stored successfully. Thank you for contributing to Expensify! |
Quick thoughts Seems the @hellohublot's proposal is straight forward one here We should address this at all places, not just here
cc: @flodnv |
Thanks @Santhosh-Sellavel. This is strange...
@hellohublot are we sure this is due to the OS and not React Native? This StackOverflow post may suggest that yes, it's the OS? |
@flodnv @Santhosh-Sellavel I investigated further and it is indeed a React Native issue. |
@hellohublot I'm not sure /\uFFFC+/ Having this check on multiple places is a bad idea, we need to handle this at a single place for addressing this at every inputs |
@Santhosh-Sellavel Thanks Thanks, but the following video looks like we don’t need to change the _after.mp4 |
#31558 is on prod!!! 😱 Can someone retest this on iPhone please? 🙏 |
@flodnv It's fixed now, tested now. 1.4.24 Issue ExistsBefore_iOS.mp41.4.28 Works FineLatest.Version.mp4 |
Hooray!!!! 😍 @trjExpensify finally we can issue payments here!!! 💸 Once again, thanks for fixing this @hellohublot 👍 |
Niceeee! Okay, so confirming these are the payments?
|
Thanks for confirming, Flo. @Santhosh-Sellavel - go ahead and request. Putting this on |
@hellohublot - paid! |
@jayeshmangwani - paid! @Santhosh-Sellavel once you confirm you've requested, I'll go ahead and close this. |
Bump @Santhosh-Sellavel! Confirm you've requested, please. |
Mic check 1, 2.. @Santhosh-Sellavel you there? 😅 |
Will request this week. Feel free to close |
Thanks! |
Requested on ND |
$2,000 approved for @Santhosh-Sellavel based on the summary above. |
If you haven’t already, check out our contributing guidelines for onboarding and email [email protected] to request to join our Slack channel!
Action Performed:
Expected Result:
If we have not spoken anything then send button should have to be disabled
Actual Result:
Send button is enabled on an empty message and we can send the empty message in the chat
Workaround:
Can the user still use Expensify without this being fixed? Have you informed them of the workaround?
Platforms:
Which of our officially supported platforms is this issue occurring on?
Version Number: 1.3.7
Reproducible in staging?: y
Reproducible in production?: y
If this was caught during regression testing, add the test name, ID and link from TestRail:
Email or phone of affected tester (no customers):
Logs: https://stackoverflow.com/c/expensify/questions/4856
Notes/Photos/Videos: Any additional supporting documentation
dictate-bug.MP4
VSSR0553.1.MP4
Expensify/Expensify Issue URL:
Issue reported by: @jayeshmangwani
Slack conversation: https://expensify.slack.com/archives/C049HHMV9SM/p1682627289846559
View all open jobs on GitHub
Upwork Automation - Do Not Edit
The text was updated successfully, but these errors were encountered: