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 2024-12-19] [$250] iOS - Search query is cut off at the bottom for certain letters #53590
Version Number: 9.0.71-0 Reproducible in staging?: Yes Reproducible in production?: Yes If this was caught on HybridApp, is this reproducible on New Expensify Standalone?: N/A If this was caught during regression testing, add the test name, ID and link from TestRail:#53317 Email or phone of affected tester (no customers):nathanmulugetatesting+2299@gmail.com Issue reported by: Applause Internal Team
Action Performed:
Open hybrid app
Navigate to search
Tap on the search icon at the top right corner
Type lower case g multiple of times
Hit enter
Expected Result:
The letters does not get cut off at the bottom
Actual Result:
The lower case letter g and other letters like lower case p get cut off at the bottom
changed the title [-]iOS - Search query is cut off at the bottom for certain letters[/-][+][$250] iOS - Search query is cut off at the bottom for certain letters[/+]on Dec 5, 2024
changed the title [-][$250] iOS - Search query is cut off at the bottom for certain letters[/-][+][HOLD for payment 2024-12-19] [$250] iOS - Search query is cut off at the bottom for certain letters[/+]on Dec 12, 2024
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:
@suneox@isabelastisser@suneox 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]
[Contributor] If the regression was CRITICAL (e.g. interrupts a core flow) A discussion in #expensify-open-source 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: N/A
[Contributor] If it was decided to create a regression test for the bug, please propose the regression test steps using the template below to ensure the same bug will not reach production again.
Activity
melvin-bot commentedon Dec 4, 2024
Triggered auto assignment to @isabelastisser (
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.abzokhattab commentedon Dec 4, 2024
Proposal
Please re-state the problem that we are trying to solve in this issue.
Search query is cut off at the bottom for certain letters
What is the root cause of that problem?
in the
SearchTypeMenuNarrowcomponent, the container height is set tocomponentSizeNormalhowever the text height is set to largeApp/src/pages/Search/SearchTypeMenuNarrow.tsx
Lines 181 to 200 in be17e04
App/src/styles/index.ts
Lines 379 to 382 in 2403fcd
What changes do you think we should make in order to solve the problem?
Result
What specific scenarios should we cover in automated tests to prevent reintroducing this issue in the future?
NA
What alternative solutions did you explore? (Optional)
isabelastisser commentedon Dec 4, 2024
I think hybrid issues need to be internal.
abzokhattab commentedon Dec 4, 2024
should it be external? i see its happening on ios standalone as well not only the hybrid.
for reference here is a similar issue #49890
[-]iOS - Search query is cut off at the bottom for certain letters[/-][+][$250] iOS - Search query is cut off at the bottom for certain letters[/+]17 remaining items
[-][$250] iOS - Search query is cut off at the bottom for certain letters[/-][+][HOLD for payment 2024-12-19] [$250] iOS - Search query is cut off at the bottom for certain letters[/+]melvin-bot commentedon Dec 12, 2024
Reviewinglabel has been removed, please complete the "BugZero Checklist".melvin-bot commentedon Dec 12, 2024
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:
If no regressions arise, payment will be issued on 2024-12-19. 🎊
For reference, here are some details about the assignees on this issue:
melvin-bot commentedon Dec 12, 2024
@suneox @isabelastisser @suneox 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]
suneox commentedon Dec 15, 2024
BugZero Checklist:
Bug classification
Source of bug:
Where bug was reported:
Who reported the bug:
[Contributor] 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: https://github.com/Expensify/App/pull/50075/files#r1885756110
[Contributor] If the regression was CRITICAL (e.g. interrupts a core flow) A discussion in #expensify-open-source 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: N/A
[Contributor] If it was decided to create a regression test for the bug, please propose the regression test steps using the template below to ensure the same bug will not reach production again.
N/A: Due to it isn't an impactful bug
isabelastisser commentedon Dec 20, 2024
The payments are processed in Upwork. All set!