Skip to content

[HOLD for payment 2024-12-19] [$250] iOS - Search query is cut off at the bottom for certain letters #53590

Closed

Description

@vincdargento

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.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:

  1. Open hybrid app
  2. Navigate to search
  3. Tap on the search icon at the top right corner
  4. Type lower case g multiple of times
  5. 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

Workaround:

Unknown

Platforms:

  • Android: Standalone
  • Android: HybridApp
  • Android: mWeb Chrome
  • iOS: Standalone
  • iOS: HybridApp
  • iOS: mWeb Safari
  • MacOS: Chrome / Safari
  • MacOS: Desktop
  • Reproduced on iPhone 11 and iPhone 13 models.

Screenshots/Videos

bug.mp4

View all open jobs on GitHub

Upwork Automation - Do Not Edit
  • Upwork Job URL: https://www.upwork.com/jobs/~021864712686512100060
  • Upwork Job ID: 1864712686512100060
  • Last Price Increase: 2024-12-05
  • Automatic offers:
    • suneox | Reviewer | 105260216
    • abzokhattab | Contributor | 105260217
Issue OwnerCurrent Issue Owner: @isabelastisser

Activity

  1. added
    BugSomething is broken. Auto assigns a BugZero manager.
    on Dec 4, 2024
  2. melvin-bot commented on Dec 4, 2024

    @melvin-bot

    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.

  3. abzokhattab commented on Dec 4, 2024

    @abzokhattab
    Contributor

    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 SearchTypeMenuNarrow component, the container height is set to componentSizeNormal however the text height is set to large

    <Animated.View style={[styles.tabSelectorButton, styles.tabBackground(hovered, true, theme.border), styles.w100, StyleUtils.getHeight(variables.componentSizeNormal)]}>
    <View style={[styles.flexRow, styles.gap2, styles.alignItemsCenter, titleViewStyles]}>
    <Icon
    src={menuIcon}
    fill={theme.icon}
    small
    />
    <Text
    numberOfLines={1}
    style={[styles.textStrong, styles.flexShrink1, styles.label]}
    >
    {menuTitle}
    </Text>
    <Icon
    src={Expensicons.DownArrow}
    fill={theme.icon}
    small
    />
    </View>
    </Animated.View>

    App/src/styles/index.ts

    Lines 379 to 382 in 2403fcd

    label: {
    fontSize: variables.fontSizeLabel,
    lineHeight: variables.lineHeightLarge,
    },

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

    • we should either change the view height to be large and match the text height
    • or change the text height to normal
                                    style={[styles.textStrong, styles.flexShrink1, styles.textLineHeightNormal, styles.fontSizeLabel]}

    Result

    image

    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)

  4. added
    InternalRequires API changes or must be handled by Expensify staff
    Help WantedApply this label when an issue is open to proposals by contributors
    Hot PickReady for an engineer to pick up and run with
    on Dec 4, 2024
  5. isabelastisser commented on Dec 4, 2024

    @isabelastisser
    Contributor

    I think hybrid issues need to be internal.

  6. abzokhattab commented on Dec 4, 2024

    @abzokhattab
    Contributor

    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

  7. added
    ExternalAdded to denote the issue can be worked on by a contributor
    and removed
    InternalRequires API changes or must be handled by Expensify staff
    Hot PickReady for an engineer to pick up and run with
    on Dec 5, 2024
  8. 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
  9. 17 remaining items

  10. added
    Awaiting PaymentAuto-added when associated PR is deployed to production
    and removed on Dec 10, 2024
  11. 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
  12. melvin-bot commented on Dec 12, 2024

    @melvin-bot

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

  13. melvin-bot commented on Dec 12, 2024

    @melvin-bot

    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:

  14. melvin-bot commented on Dec 12, 2024

    @melvin-bot

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

  15. suneox commented on Dec 15, 2024

    @suneox
    Contributor

    BugZero Checklist:

    • [Contributor] Classify the bug:
    Bug classification

    Source of bug:

    • 1a. Result of the original design (eg. a case wasn't considered)
    • 1b. Mistake during implementation
    • 1c. Backend bug
    • 1z. Other:

    Where bug was reported:

    • 2a. Reported on production (eg. bug slipped through the normal regression and PR testing process on staging)
    • 2b. Reported on staging (eg. found during regression or PR testing)
    • 2d. Reported on a PR
    • 2z. Other:

    Who reported the bug:

    • 3a. Expensify user
    • 3b. Expensify employee
    • 3c. Contributor
    • 3d. QA
    • 3z. Other:
    • [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

  16. isabelastisser commented on Dec 20, 2024

    @isabelastisser
    Contributor

    The payments are processed in Upwork. All set!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Labels

Awaiting PaymentAuto-added when associated PR is deployed to productionBugSomething is broken. Auto assigns a BugZero manager.DailyKSv2ExternalAdded to denote the issue can be worked on by a contributor

Type

No type

Projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions