First time reporting a bug? Refer to our Start Here post.
Team ID:
- In the Glide dashoard URL, e.g.
https://go.glideapps.com/o/4d7kODLke6bvSWoAjzeb/
App ID:
- In the Glide builder URL, e.g.
https://go.glideapps.com/app/SAE3oFFGi8kUubPiJ6s/layout
Description
- The choice component is difficult to use when search in iOS 26.2
How to replicate
-
Be running on iPhone on iOS 26.2
-
Click on Choice that has more items than it can display so the search has to be used
- here is an example, this looks good
-
If I search it finds my name and I can pick it out of the list. All good.
-
If I put “Gary" it covers up everything
-
as show here
-
Now if I click on the checkmark it shows my name.
-
This might be an apple problem.
-
You really have to try it out to see how messy it is as there are many other conditions that are wonky
-
Also try typing a name that does not match. You lose the search typing in that case as well.
-
The choice for the check box has around 250 items
-
It works great on a safari web browser
-
I tried turning off predictive text - did not help
1 Like
So I tried a couple of things. I put the choice component on its own page and it worked acceptably.
I then reordered the widgets like this
and it works better. It has something to do with the Image hiding the search text box. Now I can always see the search text box as per this.
3 Likes
This is not a solution. It is a work around but someone has to figure out a proper solution
2 Likes
Hi Gary, this is the response from the team:
“This is a known issue with the choice list getting filtered when you start searching, which reduces the height of the list. Hiding the keyboard will show the filtered search results. There are existing feature requests to disable search for this (and other reasons). The work around is likely the best course of action in the short-term.”
2 Likes
Thanks Thinh. If I understood, I hope they do not take out the search as I have a list of 300 items so it is not realistic to scroll thru it.
I did quickly try using a collection list for this particular instance and it kinda works but the components below get pushed off screen. Could, I guess, hide components below and then once the selection is finished show them. Maybe that is another work around for some cases.
1 Like