Prevent travel booking for SMS logins #48180

Gonals · 2024-08-28T14:16:04Z

Details

Fixed Issues

https://github.com/Expensify/Expensify/issues/423889
PROPOSAL:

Tests

Log into newDot with an account that has a phone number as primary login.
Click +-> Book Travel -> Book Travel
Confirm this error displays:

Repeat the same, but with an email as primary login. Confirm it does NOT display
Verify that no errors appear in the JS console

Offline tests

None

QA Steps

Same as tests

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

Only UI change is the error message in the tests

melvin-bot · 2024-08-28T14:16:35Z

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

puneetlath · 2024-08-28T14:20:31Z

src/languages/en.ts

@@ -2107,6 +2107,7 @@ export default {
        tripSummary: 'Trip summary',
        departs: 'Departs',
        errorMessage: 'Something went wrong. Please try again later.',
+        phoneError: 'To book travel, your primary login must be a valid email',


Could we link them in the error to the place where they can update this?

Maybe! Giving it a shot.
I'm also considering rephrasing this, as we call it "Default contact method" in newdot, istead of "primary login" like we do in oldDot. What do you think?

Ok, it can be done, but we don't really have an existing structure for it. We could do something similar to what we do for receipt errors in DotIndicatorMessage, but it would be, basically, writing another exception for this specific error. Since we have other similar errors that don't really link anywhere, I don't think it is worth it for this case.

Thoughts?

I think it would make for a better, more useful error message if we did. Perhaps we have a contributor do it as follow-up?

What do you think about this @Gonals?

puneetlath

Looks good to me but I'm going to ask a C+ to review as well.

ishpaul777 · 2024-08-29T17:55:03Z

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: mWeb Chrome
- iOS: Native
- iOS: mWeb 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 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 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(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.
I have checked off every checkbox in the PR reviewer checklist, including those that don't apply to this PR.

Screenshots/Videos

Android: Native

Android: mWeb Chrome

iOS: Native

iOS: mWeb Safari

MacOS: Chrome / Safari

MacOS: Desktop

src/languages/es.ts

ishpaul777 · 2024-08-29T18:12:31Z

I feel there should be some margin between error and button

melvin-bot · 2024-08-29T18:39:28Z

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

melvin-bot · 2024-08-29T18:39:31Z

🎯 @ishpaul777, thanks for reviewing and testing this PR! 🎉

An E/App issue has been created to issue payment here: #48289.

puneetlath · 2024-08-29T18:40:13Z

I agree with that. @Gonals can we make that look better?

Gonals · 2024-09-02T12:59:36Z

I agree with that. @Gonals can we make that look better?

Sure thing! Added a small margin. Updated the image in the original post

Gonals · 2024-09-02T13:00:11Z

I feel there should be some margin between error and button

Added!

melvin-bot · 2024-09-02T15:51:03Z

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

lakchote · 2024-09-03T06:35:23Z

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: mWeb Chrome
- iOS: Native
- iOS: mWeb 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 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 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(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.
I have checked off every checkbox in the PR reviewer checklist, including those that don't apply to this PR.

Screenshots/Videos

Android: Native

Android: mWeb Chrome

iOS: Native

iOS: mWeb Safari

MacOS: Chrome / Safari

MacOS: Desktop

Gonals · 2024-09-03T10:57:26Z

Ready for merge @lakchote?

thienlnam

Looks like Melvin did a double assignee - looks good, will ship it

OSBotify · 2024-09-03T17:37:38Z

✋ 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 · 2024-09-03T23:43:18Z

🚀 Deployed to staging by https://github.com/thienlnam in version: 9.0.29-0 🚀

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

IuliiaHerets · 2024-09-04T14:54:27Z

@Gonals QA team do not have Book travel option when use a phone account.
Is it an internal or need to raise it?

Recording.3875.mp4

ishpaul777 · 2024-09-04T17:03:38Z

Your account should be in travel beta, you can add yourself temporarily by executing this in js console on web.

Onyx.merge('betas', ['spotnanaTravel'])

@lanitochka17

IuliiaHerets · 2024-09-04T17:19:18Z

@ishpaul777 Works well according to your comment, but only on Web

thienlnam · 2024-09-04T17:21:45Z

Yeah it just seems like your account is not on the beta then - otherwise looks like it passes QA

IuliiaHerets · 2024-09-04T17:30:29Z

@thienlnam @ishpaul777 Can you check another platforms
internally?

ishpaul777 · 2024-09-04T17:44:28Z

it works well, i am also not in beta to check on staging, videos for dev env. can be found in checklist #48180 (comment)

OSBotify · 2024-09-05T19:17:20Z

🚀 Deployed to production by https://github.com/roryabraham in version: 9.0.29-12 🚀

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

Gonals added 4 commits August 28, 2024 15:48

Display error

5ddc97a

correctly show error

a9a3875

style

d62d476

spnish

8fe9f7c

Gonals self-assigned this Aug 28, 2024

Gonals requested a review from a team as a code owner August 28, 2024 14:16

melvin-bot bot requested review from puneetlath and removed request for a team August 28, 2024 14:16

puneetlath requested changes Aug 28, 2024

View reviewed changes

Gonals added 3 commits August 28, 2024 16:22

typescript

6f3c395

prettier

e387323

new message

f8014c3

puneetlath previously approved these changes Aug 29, 2024

View reviewed changes

puneetlath requested a review from ishpaul777 August 29, 2024 17:52

ishpaul777 reviewed Aug 29, 2024

View reviewed changes

src/languages/es.ts Show resolved Hide resolved

ishpaul777 approved these changes Aug 29, 2024

View reviewed changes

melvin-bot bot requested a review from thienlnam August 29, 2024 18:39

melvin-bot bot mentioned this pull request Aug 29, 2024

[PAID] Payment issue for E/App PR#48180 #48289

Closed

Gonals added 3 commits September 2, 2024 14:51

Merge branch 'main' into alberto-travelSMS

b384936

Add margin

1bbf430

smaller margin

968e757

Gonals dismissed puneetlath’s stale review via 968e757 September 2, 2024 12:58

ishpaul777 approved these changes Sep 2, 2024

View reviewed changes

melvin-bot bot requested a review from lakchote September 2, 2024 15:51

lakchote approved these changes Sep 3, 2024

View reviewed changes

thienlnam approved these changes Sep 3, 2024

View reviewed changes

thienlnam merged commit 0c948c6 into main Sep 3, 2024
20 checks passed

thienlnam deleted the alberto-travelSMS branch September 3, 2024 17:17

github-actions bot mentioned this pull request Sep 3, 2024

Deploy Checklist: New Expensify 2024-09-03 #48515

Closed

68 tasks

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Prevent travel booking for SMS logins #48180

Prevent travel booking for SMS logins #48180

Gonals commented Aug 28, 2024 •

edited

Loading

melvin-bot bot commented Aug 28, 2024

puneetlath Aug 28, 2024

Gonals Aug 28, 2024

Gonals Aug 28, 2024 •

edited

Loading

puneetlath Aug 29, 2024

puneetlath Sep 2, 2024

puneetlath left a comment

ishpaul777 commented Aug 29, 2024 •

edited

Loading

ishpaul777 commented Aug 29, 2024

melvin-bot bot commented Aug 29, 2024

melvin-bot bot commented Aug 29, 2024

puneetlath commented Aug 29, 2024

Gonals commented Sep 2, 2024 •

edited

Loading

Gonals commented Sep 2, 2024

melvin-bot bot commented Sep 2, 2024

lakchote commented Sep 3, 2024 •

edited

Loading

Gonals commented Sep 3, 2024

thienlnam left a comment

OSBotify commented Sep 3, 2024

OSBotify commented Sep 3, 2024

IuliiaHerets commented Sep 4, 2024

ishpaul777 commented Sep 4, 2024

IuliiaHerets commented Sep 4, 2024

thienlnam commented Sep 4, 2024

IuliiaHerets commented Sep 4, 2024 •

edited

Loading

ishpaul777 commented Sep 4, 2024

OSBotify commented Sep 5, 2024

Prevent travel booking for SMS logins #48180

Prevent travel booking for SMS logins #48180

Conversation

Gonals commented Aug 28, 2024 • edited Loading

Details

Fixed Issues

Tests

Offline tests

QA Steps

PR Author Checklist

Screenshots/Videos

melvin-bot bot commented Aug 28, 2024

puneetlath Aug 28, 2024

Choose a reason for hiding this comment

Gonals Aug 28, 2024

Choose a reason for hiding this comment

Gonals Aug 28, 2024 • edited Loading

Choose a reason for hiding this comment

puneetlath Aug 29, 2024

Choose a reason for hiding this comment

puneetlath Sep 2, 2024

Choose a reason for hiding this comment

puneetlath left a comment

Choose a reason for hiding this comment

ishpaul777 commented Aug 29, 2024 • edited Loading

Reviewer Checklist

Screenshots/Videos

ishpaul777 commented Aug 29, 2024

melvin-bot bot commented Aug 29, 2024

melvin-bot bot commented Aug 29, 2024

puneetlath commented Aug 29, 2024

Gonals commented Sep 2, 2024 • edited Loading

Gonals commented Sep 2, 2024

melvin-bot bot commented Sep 2, 2024

lakchote commented Sep 3, 2024 • edited Loading

Reviewer Checklist

Screenshots/Videos

Gonals commented Sep 3, 2024

thienlnam left a comment

Choose a reason for hiding this comment

OSBotify commented Sep 3, 2024

OSBotify commented Sep 3, 2024

IuliiaHerets commented Sep 4, 2024

ishpaul777 commented Sep 4, 2024

IuliiaHerets commented Sep 4, 2024

thienlnam commented Sep 4, 2024

IuliiaHerets commented Sep 4, 2024 • edited Loading

ishpaul777 commented Sep 4, 2024

OSBotify commented Sep 5, 2024

Gonals commented Aug 28, 2024 •

edited

Loading

Gonals Aug 28, 2024 •

edited

Loading

ishpaul777 commented Aug 29, 2024 •

edited

Loading

Gonals commented Sep 2, 2024 •

edited

Loading

lakchote commented Sep 3, 2024 •

edited

Loading

IuliiaHerets commented Sep 4, 2024 •

edited

Loading