You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[HOLD for payment 2023-08-07] Incorrect font size & family on Two-factor authentication page #23326
Go to Settings > Security > Two-factor authentication page
Observe paragraph text below headline
Expected Result:
The paragraph text should use our normal font size (15px) and font family (Expensify Neue)
Actual Result:
The paragraph text is too small and does not use our brand font.
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?
Android / native
Android / Chrome
iOS / native
iOS / Safari
MacOS / Chrome / Safari
MacOS / Desktop
Version Number: 1.3.42-5 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
What changes do you think we should make in order to solve the problem?
We can remove this style here and use Text component that we designed to make the text has default style which has fontSize as 15px and fontFamily as Expensify Neue
Please re-state the problem that we are trying to solve in this issue.
The font size and font family is different on two factor auth page.
What is the root cause of that problem?
Currently for that text paragraph we are using a Text component from 'react-native' instead of using our own custom Text component, which will make the font-size and family non-standard.
changed the title [-]Incorrect font size & family on Two-factor authentication page[/-][+][HOLD for payment 2023-08-07] Incorrect font size & family on Two-factor authentication page[/+]on Jul 31, 2023
The solution for this issue has been 🚀 deployed to production 🚀 in version 1.3.47-6 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue:
If no regressions arise, payment will be issued on 2023-08-07. 🎊
After the hold period is over and BZ checklist items are completed, please complete any of the applicable payments for this issue, and check them off once done.
External issue reporter
Contributor that fixed the issue
Contributor+ that helped on the issue and/or PR
For reference, here are some details about the assignees on this issue:
@sobitneupanedoes not require payment (Eligable for Manual Requests)
As a reminder, here are the bonuses/penalties that should be applied for any External issue:
Merged PR within 3 business days of assignment - 50% bonus
Merged PR more than 9 business days after assignment - 50% penalty
BugZero Checklist: The PR fixing this issue has been merged! The following checklist (instructions) will need to be completed before the issue can be closed:
[@sobitneupane] The PR that introduced the bug has been identified. Link to the PR:
[@sobitneupane] The offending PR has been commented on, pointing out the bug it caused and why, so the author and reviewers can learn from the mistake. Link to comment:
[@sobitneupane] A discussion in #expensify-bugs has been started about whether any other steps should be taken (e.g. updating the PR review checklist) in order to catch this type of bug sooner. Link to discussion:
[@sobitneupane] Determine if we should create a regression test for this bug.
[@sobitneupane] If we decide to create a regression test for the bug, please propose the regression test steps to ensure the same bug will not reach production again.
[@greg-schroeder] Link the GH issue for creating/updating the regression test once above steps have been agreed upon:
Activity
melvin-bot commentedon Jul 21, 2023
Triggered auto assignment to @greg-schroeder (
Bug), see https://stackoverflow.com/c/expensify/questions/14418 for more details.melvin-bot commentedon Jul 21, 2023
Bug0 Triage Checklist (Main S/O)
Platformsin OP are ✅)dukenv0307 commentedon Jul 21, 2023
Proposal
Please re-state the problem that we are trying to solve in this issue.
Incorrect font size & family on Two-factor authentication page
What is the root cause of that problem?
The paragraph has style
styles.textLabelwhich isn't the expected font-size and doesn't contain font familyApp/src/pages/settings/Security/TwoFactorAuth/IsEnabledPage.js
Line 46 in 7fea760
App/src/styles/styles.js
Lines 293 to 296 in 7fea760
What changes do you think we should make in order to solve the problem?
We can remove this style here and use Text component that we designed to make the text has default style which has
fontSizeas15pxandfontFamilyasExpensify NeueApp/src/pages/settings/Security/TwoFactorAuth/IsEnabledPage.js
Line 46 in 7fea760
What alternative solutions did you explore? (Optional)
getusha commentedon Jul 21, 2023
Proposal
Please re-state the problem that we are trying to solve in this issue.
The font size and font family is different on two factor auth page.
What is the root cause of that problem?
Currently for that text paragraph we are using a Text component from 'react-native' instead of using our own custom Text component, which will make the font-size and family non-standard.
App/src/pages/settings/Security/TwoFactorAuth/IsEnabledPage.js
Line 2 in 7fea760
What changes do you think we should make in order to solve the problem?
We should instead import the
Textcomponent from../../../../components/Textand remove the style applied to the text.App/src/pages/settings/Security/TwoFactorAuth/IsEnabledPage.js
Line 46 in 7fea760
MonilBhavsar commentedon Jul 21, 2023
This was missed during initial implementation, and I'll take a look
melvin-bot commentedon Jul 21, 2023
Job added to Upwork: https://www.upwork.com/jobs/~0112470818bb41c902
melvin-bot commentedon Jul 21, 2023
Triggered auto assignment to Contributor Plus for review of internal employee PR - @sobitneupane (
Internal)greg-schroeder commentedon Jul 21, 2023
Looks like Monil is gonna take this one on, marked
Internalaccordingly8 remaining items
greg-schroeder commentedon Jul 31, 2023
PR on staging, awaiting deploy to prod
[-]Incorrect font size & family on Two-factor authentication page[/-][+][HOLD for payment 2023-08-07] Incorrect font size & family on Two-factor authentication page[/+]melvin-bot commentedon Jul 31, 2023
Reviewinglabel has been removed, please complete the "BugZero Checklist".melvin-bot commentedon Jul 31, 2023
The solution for this issue has been 🚀 deployed to production 🚀 in version 1.3.47-6 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue:
If no regressions arise, payment will be issued on 2023-08-07. 🎊
After the hold period is over and BZ checklist items are completed, please complete any of the applicable payments for this issue, and check them off once done.
For reference, here are some details about the assignees on this issue:
As a reminder, here are the bonuses/penalties that should be applied for any External issue:
melvin-bot commentedon Jul 31, 2023
BugZero Checklist: The PR fixing this issue has been merged! The following checklist (instructions) will need to be completed before the issue can be closed:
MonilBhavsar commentedon Aug 7, 2023
Closing this as it was all internal, and we missed during initial implementation