Search pane (flow) keeps refreshing

Bug Reports
,
1

What’s The Bug?

Flow pane in search pane keeps refreshing itself, making it impossible to use arrows to reach objects.

How To Reproduce It

  1. Go to search pane
  2. Search for an object with links/backlinks
  3. Arrow down to reach lower objects
  4. :lady_beetle: Every 1-2 seconds, the list refreshes and arrow returns to top object

Image or Video

The Expected Behavior

Arrowing allows smooth object selection in flow/search pane.

Device

Macbook Air M1

OS

Sequoia 15.1.1

Anytype Version

v.0.45.3

Network Mode

Local-only (Irrelevant)

Technical Information

OS version: darwin arm64 15.1.1
App version: 0.45.3
Build number: build on 2025-02-17 15:22:27 +0000 UTC at #f1ceda0a1457dbf982d8b3fd8479ccdcb95df6d3 (dirty)
Library version: v0.39.11

2

Yes, there was a problem with a filter, now fixed.

3

I found this bug still happening with v.0.46.0.

OS version: darwin arm64 15.1.1
App version: 0.46.0
Build number: build on 2025-04-16 14:09:11 +0000 UTC at #99fbaeb1270bce6745f65b6cd74ee1664716c812
Library version: v0.40.15

4

Could you elaborate pls as I do not reproduce this problem.

5

I have recorded a new video, but I think there is nothing new compared to the video in original post. I might have missed one reproduction step though. See if this helps.

How to Reproduce

  1. Go to search pane
  2. Search for an object with links/backlinks
  3. Shift+Enter to activate the flow pane (“Show related Objects”) in search pane
  4. Arrow down to reach 2nd (or further) object (to preselect the object, without actually pressing “Enter” to activate the selection of object, just hover)
  5. :lady_beetle:Every 1-2 seconds, the list refreshes and arrow returns to top object

P.S. in the video, after activating flow pane at ~0.7s, there is a second where the results display a (second) search from objects in flow pane, using the text typed in search pane (1st search), which users technically haven’t done such action. Not a big deal though.

7

Thank you

10

Just checked again. This shouldn’t be a problem now on v.0.55.4.

Thanks team for doing whatever that was needed.