Skip to main content

Search bar height issue

Bug 1

Abstract:

If you click the ABRP logo next to the search bar to lift up the search menu, it cannot be lowered by swiping on the handle at the top.

Expected result:

Using the grey bar will lower the search location

Observed result:

While the grey bar can slightly pull it (less than 0.5cm) it cannot be lowered. I have to use the back arrow.

Steps to reproduce:

Open ABRP, click on the logo (near the bottom right, after the text “where do you want to go?”

Attempt to lower the menu using the handle at the top. Note that it doesn’t work.

Bug 2

Abstract:

It is not possible to raise the search menu to the full height of the screen using the grey handle.

Expected result:

The grey handle can be used the switch between the half and full height search menu

Observed result:

Same slight movement as above, but it doesn’t switch to the upper state

Steps to reproduce:

Open ABRP.

Lift the search menu using the grey handle (to the middle height).

Attempt to lift it to the full height

Observe that it doesn’t.

General info

Device info:

iPhone 17 (MG6L4QN/A)

iOS 26.2

ABRP version: 6.2.0 (5695)

Notes

This is my first bug report for you, so let me know if you want it formatted differently.
I hope this is the correct place for beta bugs, I was sent here when I emailed the email address you have on your testflight page.

Where does this happen?
ABRP version number (found at bottom of settings menu)
Status: Awaiting Clarification2 comments

Log in to comment and vote

Comments2

  • Mahde - ABRP changed status to Awaiting Clarification
    Team•

    Jan 8

    Pinned

    Hello @Joe,

    Thank you for this feedback for the beta version! We are currently working on resolving issues that users face when using it and has been spotted by us. We will keep this noted and work on it for the full release.

    • Joe

      •

      Jan 8

      Hi,

      I’m only replying to say that the bug still appears in the new update (5700).

      ps Obviously this is not a complaint, I’m just avoiding the question of “has this been fixed with the new version”