[HOLD for payment 2024-12-19] [$150] IOS/Android-Verify account-Inconsistent behavior when returning from Let's make sure it is you #52959

lanitochka17 · 2024-11-22T13:54:04Z

If you haven’t already, check out our contributing guidelines for onboarding and email contributors@expensify.com to request to join our Slack channel!

Version Number: 9.0.65.1
Reproducible in staging?: Y
Reproducible in production?: Y
If this was caught on HybridApp, is this reproducible on New Expensify Standalone?: Y
If this was caught during regression testing, add the test name, ID and link from TestRail: N/A
Issue reported by: Applause - Internal Team

Issue found when executing PR #52232

Action Performed:

precondition: user has enabled Expensify card

Open the app and log in
Navigate to the account settings > Security >Copilot
Continue with the flow
On "Let's make sure it is you" step, tap the back icon
Create a new workspace and open the workspace settings
Select More feature and enable Workflows
Open Workflows > toggle on "Make or track payments" option
Tap Connect bank account > any option
On "Let's make sure it is you" step, tap the back icon
Navigate to the workspace with Expensify card enabled
Start issuing a new card
On "Let's make sure it is you" step, tap the back icon
Navigate to account settings > Profile > Contact method
Start adding a new contact method
On "Let's make sure it is you" step, tap the back icon

Expected Result:

User is navigated to the previous screen after tapping the back icon on "Let's make sure it is you" in the flows where code validation is required

Actual Result:

When tapping the back icon on "Let's make sure it is you" step in the Add copilot and Add bank account flows (steps 4 and 9), the keyboard gets dismissed while in the other flows (Issue a new card, Add new contact method, Reveal card details) user is returned to the previous screen immediately (steps 12 and 15)

Workaround:

Unknown

Platforms:

Which of our officially supported platforms is this issue occurring on?

Screenshots/Videos

Add any screenshot/video evidence

Bug6672434_1732229158372.video_2024-11-21_17-41-09.mp4

View all open jobs on GitHub

Upwork Automation - Do Not Edit

Upwork Job URL: https://www.upwork.com/jobs/~021861312036312016837
Upwork Job ID: 1861312036312016837
Last Price Increase: 2024-11-26

Issue Owner

Current Issue Owner: @VictoriaExpensify

melvin-bot · 2024-11-22T13:54:14Z

Triggered auto assignment to @VictoriaExpensify (Bug), see https://stackoverflow.com/c/expensify/questions/14418 for more details. Please add this bug to a GH project, as outlined in the SO.

NJ-2020 · 2024-11-22T15:00:31Z

Proposal

Please re-state the problem that we are trying to solve in this issue.

IOS/Android-Verify account-Inconsistent behavior when returning from Let's make sure it is you

What is the root cause of that problem?

It's because the ValidateCodeActionModal is wrapped inside ScrollView component

App/src/pages/ReimbursementAccount/BankAccountStep.tsx

Lines 228 to 243 in 8d69d60

    
                       <ValidateCodeActionModal 
        
                           title={translate('contacts.validateAccount')} 
        
                           descriptionPrimary={translate('contacts.featureRequiresValidate')} 
        
                           descriptionSecondary={translate('contacts.enterMagicCode', {contactMethod})} 
        
                           isVisible={!!isValidateCodeActionModalVisible} 
        
                           hasMagicCodeBeenSent={hasMagicCodeBeenSent} 
        
                           validatePendingAction={loginData?.pendingFields?.validateCodeSent} 
        
                           sendValidateCode={() => User.requestValidateCodeAction()} 
        
                           handleSubmitForm={(validateCode) => User.validateSecondaryLogin(loginList, contactMethod, validateCode)} 
        
                           validateError={!isEmptyObject(validateLoginError) ? validateLoginError : ErrorUtils.getLatestErrorField(loginData, 'validateCodeSent')} 
        
                           clearError={() => User.clearContactMethodErrors(contactMethod, !isEmptyObject(validateLoginError) ? 'validateLogin' : 'validateCodeSent')} 
        
                           onClose={() => toggleValidateCodeActionModal?.(false)} 
        
                       /> 
        
                   </View> 
        
               </ScrollView> 
        
           </View>

I can see like inside Profile page the ValidateCodeActionModal got dismissed properly when we click the back button because the ValidateCodeActionModal is not wrapped by ScrollView

App/src/pages/settings/Profile/Contacts/NewContactMethodPage.tsx

Lines 156 to 180 in 8d69d60

    
                   <ValidateCodeActionModal 
        
                       validatePendingAction={pendingContactAction?.pendingFields?.actionVerified} 
        
                       validateError={validateLoginError} 
        
                       handleSubmitForm={addNewContactMethod} 
        
                       clearError={() => { 
        
                           if (!loginData) { 
        
                               return; 
        
                           } 
        
                           User.clearContactMethodErrors(addSMSDomainIfPhoneNumber(pendingContactAction?.contactMethod ?? contactMethod), 'addedLogin'); 
        
                       }} 
        
                       onClose={() => { 
        
                           if (loginData?.errorFields && pendingContactAction?.contactMethod) { 
        
                               User.clearContactMethod(pendingContactAction?.contactMethod); 
        
                               User.clearUnvalidatedNewContactMethodAction(); 
        
                           } 
        
                           setIsValidateCodeActionModalVisible(false); 
        
                       }} 
        
                       isVisible={isValidateCodeActionModalVisible} 
        
                       hasMagicCodeBeenSent={!!loginData?.validateCodeSent} 
        
                       title={translate('delegate.makeSureItIsYou')} 
        
                       sendValidateCode={() => User.requestValidateCodeAction()} 
        
                       descriptionPrimary={translate('contacts.enterMagicCode', {contactMethod})} 
        
                   /> 
        
               </ScreenWrapper> 
        
           );

But in the other side like inside Bank account page the ValidateCodeActionModal is not get dismissed properly because it's wrapped by ScrollView, example here:
BankAccountPage

App/src/pages/ReimbursementAccount/BankAccountStep.tsx

Lines 228 to 243 in 8d69d60

    
                       <ValidateCodeActionModal 
        
                           title={translate('contacts.validateAccount')} 
        
                           descriptionPrimary={translate('contacts.featureRequiresValidate')} 
        
                           descriptionSecondary={translate('contacts.enterMagicCode', {contactMethod})} 
        
                           isVisible={!!isValidateCodeActionModalVisible} 
        
                           hasMagicCodeBeenSent={hasMagicCodeBeenSent} 
        
                           validatePendingAction={loginData?.pendingFields?.validateCodeSent} 
        
                           sendValidateCode={() => User.requestValidateCodeAction()} 
        
                           handleSubmitForm={(validateCode) => User.validateSecondaryLogin(loginList, contactMethod, validateCode)} 
        
                           validateError={!isEmptyObject(validateLoginError) ? validateLoginError : ErrorUtils.getLatestErrorField(loginData, 'validateCodeSent')} 
        
                           clearError={() => User.clearContactMethodErrors(contactMethod, !isEmptyObject(validateLoginError) ? 'validateLogin' : 'validateCodeSent')} 
        
                           onClose={() => toggleValidateCodeActionModal?.(false)} 
        
                       /> 
        
                   </View> 
        
               </ScrollView> 
        
           </View>

Copilot

App/src/pages/settings/Security/AddDelegate/DelegateMagicCodeModal.tsx

Lines 49 to 52 in 8d69d60

    
           return ( 
        
               <ValidateCodeActionModal 
        
                   clearError={clearError} 
        
                   onClose={onBackButtonPress}

App/src/pages/settings/Security/AddDelegate/ConfirmDelegatePage.tsx

Lines 76 to 88 in 8d69d60

    
               <DelegateMagicCodeModal 
        
                   login={login} 
        
                   role={role} 
        
                   onClose={() => { 
        
                       if (!showValidateActionModal) { 
        
                           setIsValidateCodeActionModalVisible(false); 
        
                           return; 
        
                       } 
        
                       Navigation.navigate(ROUTES.SETTINGS_SECURITY); 
        
                   }} 
        
                   isValidateCodeActionModalVisible={isValidateCodeActionModalVisible} 
        
               /> 
        
           </HeaderPageLayout>

App/src/components/HeaderPageLayout.tsx

Lines 101 to 107 in 8d69d60

    
           <ScrollView contentContainerStyle={[safeAreaPaddingBottomStyle, style, scrollViewContainerStyles]}> 
        
               {!Browser.isSafari() && <View style={styles.overscrollSpacer(backgroundColor ?? theme.appBG, windowHeight)} />} 
        
               <View style={[styles.alignItemsCenter, styles.justifyContentEnd, StyleUtils.getBackgroundColorStyle(backgroundColor ?? theme.appBG), headerContainerStyles]}> 
        
                   {headerContent} 
        
               </View> 
        
               <View style={[styles.pt5, appBGColor, childrenContainerStyles]}>{children}</View> 
        
           </ScrollView>

What changes do you think we should make in order to solve the problem?

We should put the ValidateCodeActionModal outside the ScrollView

App/src/pages/ReimbursementAccount/BankAccountStep.tsx

Lines 228 to 243 in 8d69d60

    
                       <ValidateCodeActionModal 
        
                           title={translate('contacts.validateAccount')} 
        
                           descriptionPrimary={translate('contacts.featureRequiresValidate')} 
        
                           descriptionSecondary={translate('contacts.enterMagicCode', {contactMethod})} 
        
                           isVisible={!!isValidateCodeActionModalVisible} 
        
                           hasMagicCodeBeenSent={hasMagicCodeBeenSent} 
        
                           validatePendingAction={loginData?.pendingFields?.validateCodeSent} 
        
                           sendValidateCode={() => User.requestValidateCodeAction()} 
        
                           handleSubmitForm={(validateCode) => User.validateSecondaryLogin(loginList, contactMethod, validateCode)} 
        
                           validateError={!isEmptyObject(validateLoginError) ? validateLoginError : ErrorUtils.getLatestErrorField(loginData, 'validateCodeSent')} 
        
                           clearError={() => User.clearContactMethodErrors(contactMethod, !isEmptyObject(validateLoginError) ? 'validateLogin' : 'validateCodeSent')} 
        
                           onClose={() => toggleValidateCodeActionModal?.(false)} 
        
                       /> 
        
                   </View> 
        
               </ScrollView> 
        
           </View>

And we can do the same approach for other pages also

Result

Screen.Recording.2024-11-22.at.07.02.17.mov

What alternative solutions did you explore? (Optional)

bernhardoj · 2024-11-22T15:50:11Z

Proposal

Please re-state the problem that we are trying to solve in this issue.

Inconsistent behavior on some pages that use the magic code validation modal.

What is the root cause of that problem?

For the copilot and bank account validation modal, the validation modal is wrapped inside a ScrollView.

App/src/pages/settings/Security/AddDelegate/ConfirmDelegatePage.tsx

Lines 76 to 88 in a35df5b

    
               <DelegateMagicCodeModal 
        
                   login={login} 
        
                   role={role} 
        
                   onClose={() => { 
        
                       if (!showValidateActionModal) { 
        
                           setIsValidateCodeActionModalVisible(false); 
        
                           return; 
        
                       } 
        
                       Navigation.navigate(ROUTES.SETTINGS_SECURITY); 
        
                   }} 
        
                   isValidateCodeActionModalVisible={isValidateCodeActionModalVisible} 
        
               /> 
        
           </HeaderPageLayout>

App/src/components/HeaderPageLayout.tsx

Lines 101 to 107 in a35df5b

    
           <ScrollView contentContainerStyle={[safeAreaPaddingBottomStyle, style, scrollViewContainerStyles]}> 
        
               {!Browser.isSafari() && <View style={styles.overscrollSpacer(backgroundColor ?? theme.appBG, windowHeight)} />} 
        
               <View style={[styles.alignItemsCenter, styles.justifyContentEnd, StyleUtils.getBackgroundColorStyle(backgroundColor ?? theme.appBG), headerContainerStyles]}> 
        
                   {headerContent} 
        
               </View> 
        
               <View style={[styles.pt5, appBGColor, childrenContainerStyles]}>{children}</View> 
        
           </ScrollView>

App/src/pages/ReimbursementAccount/BankAccountStep.tsx

Lines 228 to 242 in a35df5b

    
                   <ValidateCodeActionModal 
        
                       title={translate('contacts.validateAccount')} 
        
                       descriptionPrimary={translate('contacts.featureRequiresValidate')} 
        
                       descriptionSecondary={translate('contacts.enterMagicCode', {contactMethod})} 
        
                       isVisible={!!isValidateCodeActionModalVisible} 
        
                       hasMagicCodeBeenSent={hasMagicCodeBeenSent} 
        
                       validatePendingAction={loginData?.pendingFields?.validateCodeSent} 
        
                       sendValidateCode={() => User.requestValidateCodeAction()} 
        
                       handleSubmitForm={(validateCode) => User.validateSecondaryLogin(loginList, contactMethod, validateCode)} 
        
                       validateError={!isEmptyObject(validateLoginError) ? validateLoginError : ErrorUtils.getLatestErrorField(loginData, 'validateCodeSent')} 
        
                       clearError={() => User.clearContactMethodErrors(contactMethod, !isEmptyObject(validateLoginError) ? 'validateLogin' : 'validateCodeSent')} 
        
                       onClose={() => toggleValidateCodeActionModal?.(false)} 
        
                   /> 
        
               </View> 
        
           </ScrollView>

ScrollView by default will dismiss the keyboard first when tapping on it, so we need to press the back button again to close the modal. Compared to the issue new card confirm page, the modal is outside the scroll view, so it doesn't have this problem.

What changes do you think we should make in order to solve the problem?

In a normal case, we won't have this problem because a header is usually not wrapped in a scroll view. But in this case, it's a bit different because the modal is put inside the scroll view, so the whole modal is affected. To fix this, we can keyboardShouldPersistTaps="handled" to the scroll view.

<ScrollView keyboardShouldPersistTaps="handled">

It's the same as what we did on the contact method details page.

App/src/pages/settings/Profile/Contacts/ContactMethodDetailsPage.tsx

Lines 244 to 273 in a35df5b

    
           <ScrollView keyboardShouldPersistTaps="handled"> 
        
               {isFailedAddContactMethod && ( 
        
                   <ErrorMessageRow 
        
                       errors={ErrorUtils.getLatestErrorField(loginData, 'addedLogin')} 
        
                       errorRowStyles={[themeStyles.mh5, themeStyles.mv3]} 
        
                       onClose={() => { 
        
                           User.clearContactMethod(contactMethod); 
        
                           User.clearUnvalidatedNewContactMethodAction(); 
        
                           Navigation.goBack(ROUTES.SETTINGS_CONTACT_METHODS.getRoute(backTo)); 
        
                       }} 
        
                       canDismissError 
        
                   /> 
        
               )} 
        
               <ValidateCodeActionModal 
        
                   title={formattedContactMethod} 
        
                   onModalHide={() => {}} 
        
                   hasMagicCodeBeenSent={hasMagicCodeBeenSent} 
        
                   isVisible={isValidateCodeActionModalVisible && !loginData.validatedDate && !!loginData} 
        
                   validatePendingAction={loginData.pendingFields?.validateCodeSent} 
        
                   handleSubmitForm={(validateCode) => User.validateSecondaryLogin(loginList, contactMethod, validateCode)} 
        
                   validateError={!isEmptyObject(validateLoginError) ? validateLoginError : ErrorUtils.getLatestErrorField(loginData, 'validateCodeSent')} 
        
                   clearError={() => User.clearContactMethodErrors(contactMethod, !isEmptyObject(validateLoginError) ? 'validateLogin' : 'validateCodeSent')} 
        
                   onClose={() => { 
        
                       Navigation.goBack(ROUTES.SETTINGS_CONTACT_METHODS.getRoute(backTo)); 
        
                       setIsValidateCodeActionModalVisible(false); 
        
                   }} 
        
                   sendValidateCode={() => User.requestContactMethodValidateCode(contactMethod)} 
        
                   descriptionPrimary={translate('contacts.enterMagicCode', {contactMethod})} 
        
               />

This is especially useful for cases like the copilot confirm page because it uses HeaderPageLayout and the children is always wrapped with a scroll view. For other cases, if it's possible to put the modal outside the scroll view, then we put it outside the scroll view.

It's technically possible for the copilot confirm page too by doing it like this:

<>
    <HeaderPageLayout ... />
    <DelegateMagicCodeModal ... />
</>

But I think it would be cleaner to just apply keyboardShouldPersistTaps="handled" to the scroll view inside HeaderPageLayout (we can add a new prop to control it if needed).

Also, there are other pages that put the modal inside the scroll view too which we may need to fix too, such as the CodesStep.

App/src/pages/settings/Security/TwoFactorAuth/Steps/CodesStep.tsx

Lines 172 to 186 in a35df5b

    
               <ValidateCodeActionModal 
        
                   title={translate('contacts.validateAccount')} 
        
                   descriptionPrimary={translate('contacts.featureRequiresValidate')} 
        
                   descriptionSecondary={translate('contacts.enterMagicCode', {contactMethod})} 
        
                   isVisible={!isUserValidated} 
        
                   hasMagicCodeBeenSent={hasMagicCodeBeenSent} 
        
                   validatePendingAction={loginData?.pendingFields?.validateCodeSent} 
        
                   sendValidateCode={() => User.requestValidateCodeAction()} 
        
                   handleSubmitForm={(validateCode) => User.validateSecondaryLogin(loginList, contactMethod, validateCode, true)} 
        
                   validateError={!isEmptyObject(validateLoginError) ? validateLoginError : ErrorUtils.getLatestErrorField(loginData, 'validateCodeSent')} 
        
                   clearError={() => User.clearContactMethodErrors(contactMethod, !isEmptyObject(validateLoginError) ? 'validateLogin' : 'validateCodeSent')} 
        
                   onModalHide={() => {}} 
        
                   onClose={() => TwoFactorAuthActions.quitAndNavigateBack(backTo)} 
        
               /> 
        
           </ScrollView>

VictoriaExpensify · 2024-11-26T07:32:10Z

Hmm ok so I think this is a pretty minor issue, but because we do want everything to be consistent, we should fix it.

My feeling is that this is a pretty easy fix so I'm going to lower the bounty on this one. If I'm missing anything to do with the complexity here, please let me know.

melvin-bot · 2024-11-26T07:32:27Z

Job added to Upwork: https://www.upwork.com/jobs/~021861312036312016837

melvin-bot · 2024-11-26T07:32:32Z

Triggered auto assignment to Contributor-plus team member for initial proposal review - @thesahindia (External)

melvin-bot · 2024-11-26T07:32:41Z

Upwork job price has been updated to $150

thesahindia · 2024-11-27T20:56:11Z

@bernhardoj's proposal looks good to me!

🎀 👀 🎀 C+ reviewed

melvin-bot · 2024-11-27T20:56:26Z

Triggered auto assignment to @danieldoglas, see https://stackoverflow.com/c/expensify/questions/7972 for more details.

danieldoglas · 2024-12-02T21:05:32Z

assigned

bernhardoj · 2024-12-03T08:24:09Z

PR is ready

cc: @thesahindia

@VictoriaExpensify btw, I think we can keep the price at a normal price (250) since we need to fix this at 3 pages, so we need to test more too.

melvin-bot · 2024-12-12T01:34:27Z

Reviewing label has been removed, please complete the "BugZero Checklist".

melvin-bot · 2024-12-12T01:34:32Z

The solution for this issue has been 🚀 deployed to production 🚀 in version 9.0.74-8 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue:

Fix pressing back button doesn't close the validate code modal when keyboard is shown #53435

If no regressions arise, payment will be issued on 2024-12-19. 🎊

For reference, here are some details about the assignees on this issue:

@bernhardoj requires payment through NewDot Manual Requests
@thesahindia requires payment through NewDot Manual Requests

melvin-bot · 2024-12-12T01:34:33Z

@thesahindia @VictoriaExpensify @thesahindia The PR fixing this issue has been merged! The following checklist (instructions) will need to be completed before the issue can be closed. Please copy/paste the BugZero Checklist from here into a new comment on this GH and complete it. If you have the K2 extension, you can simply click: [this button]

melvin-bot · 2024-12-19T09:03:33Z

Payment Summary

Upwork Job

Reviewer: @bernhardoj owed $250 via NewDot
Reviewer: @thesahindia owed $250 via NewDot

BugZero Checklist (@VictoriaExpensify)

I have verified the correct assignees and roles are listed above and updated the neccesary manual offers
I have verified that there are no duplicate or incorrect contracts on Upwork for this job (https://www.upwork.com/ab/applicants/1861312036312016837/hired)
I have paid out the Upwork contracts or cancelled the ones that are incorrect
I have verified the payment summary above is correct

VictoriaExpensify · 2024-12-22T22:11:01Z

Payment summary:
Contributor: @bernhardoj owed $250 via Upwork
C+: @thesahindia owed $250 via Upwork

bernhardoj · 2024-12-23T01:08:45Z

Requested in ND.

JmillsExpensify · 2024-12-23T12:17:02Z

$250 approved for @bernhardoj

lanitochka17 added Daily KSv2 Bug Something is broken. Auto assigns a BugZero manager. labels Nov 22, 2024

melvin-bot bot assigned VictoriaExpensify Nov 22, 2024

melvin-bot bot added the Overdue label Nov 25, 2024

melvin-bot bot removed the Overdue label Nov 26, 2024

VictoriaExpensify added this to [#whatsnext] #quality Nov 26, 2024

VictoriaExpensify added the External Added to denote the issue can be worked on by a contributor label Nov 26, 2024

melvin-bot bot changed the title ~~IOS/Android-Verify account-Inconsistent behavior when returning from Let's make sure it is you~~ [$250] IOS/Android-Verify account-Inconsistent behavior when returning from Let's make sure it is you Nov 26, 2024

melvin-bot bot added the Help Wanted Apply this label when an issue is open to proposals by contributors label Nov 26, 2024

melvin-bot bot assigned thesahindia Nov 26, 2024

VictoriaExpensify changed the title ~~[$250] IOS/Android-Verify account-Inconsistent behavior when returning from Let's make sure it is you~~ [$150] IOS/Android-Verify account-Inconsistent behavior when returning from Let's make sure it is you Nov 26, 2024

melvin-bot bot assigned danieldoglas Nov 27, 2024

danieldoglas assigned bernhardoj Dec 2, 2024

melvin-bot bot added Overdue and removed Help Wanted Apply this label when an issue is open to proposals by contributors labels Dec 2, 2024

melvin-bot bot removed the Overdue label Dec 2, 2024

bernhardoj mentioned this issue Dec 3, 2024

Fix pressing back button doesn't close the validate code modal when keyboard is shown #53435

Merged

50 tasks

melvin-bot bot added Reviewing Has a PR in review Weekly KSv2 and removed Daily KSv2 labels Dec 3, 2024

muttmuure moved this to LOW in [#whatsnext] #quality Dec 3, 2024

melvin-bot bot added Weekly KSv2 Awaiting Payment Auto-added when associated PR is deployed to production and removed Weekly KSv2 labels Dec 12, 2024

melvin-bot bot changed the title ~~[$150] IOS/Android-Verify account-Inconsistent behavior when returning from Let's make sure it is you~~ [HOLD for payment 2024-12-19] [$150] IOS/Android-Verify account-Inconsistent behavior when returning from Let's make sure it is you Dec 12, 2024

melvin-bot bot removed the Reviewing Has a PR in review label Dec 12, 2024

melvin-bot bot added Daily KSv2 and removed Weekly KSv2 labels Dec 18, 2024

melvin-bot bot added the Overdue label Dec 20, 2024

VictoriaExpensify closed this as completed Dec 22, 2024

melvin-bot bot removed Overdue labels Dec 22, 2024

github-project-automation bot moved this from LOW to Done in [#whatsnext] #quality Dec 22, 2024

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

[HOLD for payment 2024-12-19] [$150] IOS/Android-Verify account-Inconsistent behavior when returning from Let's make sure it is you #52959

[HOLD for payment 2024-12-19] [$150] IOS/Android-Verify account-Inconsistent behavior when returning from Let's make sure it is you #52959

lanitochka17 commented Nov 22, 2024 •

edited by melvin-bot bot

Loading

melvin-bot bot commented Nov 22, 2024

NJ-2020 commented Nov 22, 2024 •

edited

Loading

bernhardoj commented Nov 22, 2024

VictoriaExpensify commented Nov 26, 2024

melvin-bot bot commented Nov 26, 2024

melvin-bot bot commented Nov 26, 2024

melvin-bot bot commented Nov 26, 2024

thesahindia commented Nov 27, 2024

melvin-bot bot commented Nov 27, 2024

danieldoglas commented Dec 2, 2024

bernhardoj commented Dec 3, 2024

melvin-bot bot commented Dec 12, 2024

melvin-bot bot commented Dec 12, 2024

melvin-bot bot commented Dec 12, 2024

melvin-bot bot commented Dec 19, 2024 •

edited by VictoriaExpensify

Loading

VictoriaExpensify commented Dec 22, 2024

bernhardoj commented Dec 23, 2024

JmillsExpensify commented Dec 23, 2024

[HOLD for payment 2024-12-19] [$150] IOS/Android-Verify account-Inconsistent behavior when returning from Let's make sure it is you #52959

[HOLD for payment 2024-12-19] [$150] IOS/Android-Verify account-Inconsistent behavior when returning from Let's make sure it is you #52959

Comments

lanitochka17 commented Nov 22, 2024 • edited by melvin-bot bot Loading

Action Performed:

Expected Result:

Actual Result:

Workaround:

Platforms:

Screenshots/Videos

melvin-bot bot commented Nov 22, 2024

NJ-2020 commented Nov 22, 2024 • edited Loading

Proposal

Please re-state the problem that we are trying to solve in this issue.

What is the root cause of that problem?

What changes do you think we should make in order to solve the problem?

Result

What alternative solutions did you explore? (Optional)

bernhardoj commented Nov 22, 2024

Proposal

Please re-state the problem that we are trying to solve in this issue.

What is the root cause of that problem?

What changes do you think we should make in order to solve the problem?

VictoriaExpensify commented Nov 26, 2024

melvin-bot bot commented Nov 26, 2024

melvin-bot bot commented Nov 26, 2024

melvin-bot bot commented Nov 26, 2024

thesahindia commented Nov 27, 2024

melvin-bot bot commented Nov 27, 2024

danieldoglas commented Dec 2, 2024

bernhardoj commented Dec 3, 2024

melvin-bot bot commented Dec 12, 2024

melvin-bot bot commented Dec 12, 2024

melvin-bot bot commented Dec 12, 2024

melvin-bot bot commented Dec 19, 2024 • edited by VictoriaExpensify Loading

Payment Summary

BugZero Checklist (@VictoriaExpensify)

VictoriaExpensify commented Dec 22, 2024

bernhardoj commented Dec 23, 2024

JmillsExpensify commented Dec 23, 2024

lanitochka17 commented Nov 22, 2024 •

edited by melvin-bot bot

Loading

NJ-2020 commented Nov 22, 2024 •

edited

Loading

melvin-bot bot commented Dec 19, 2024 •

edited by VictoriaExpensify

Loading