New created object cannot be searched in mention/link/relation

What’s The Bug?

New created object cannot be searched in mention / /link and object-supported relation on desktop.
This new object also can’t be searched on mobile (But if the object is created from mobile, it can be searched on mobile, but still not on desktop).

Sometimes opening the newly created object resolve the bug and it can be searched but not always.

Remarks: This indexing(?) issue occurs even if mobile is not involved

How To Reproduce It

Part A
A1. Create a new object on desktop (without opening the object)
A2. Attempt to search for the new object with @ mention, /link or object-supported relation
A3. the new object doesn’t show up when search :lady_beetle:
A4. Confirm this new object is synced to mobile
A5. Repeat A2 on mobile
A6. Same issue as A3

Part B (object created on mobile)
B1. Do A1 except on mobile
B2. Attempt to link (on mobile)
B3. This B1 object does show up on mobile :white_check_mark:
B4. Confirm synced to desktop
B5. Attempt to link (on desktop)
B6. B1 object does not show up :lady_beetle:

Video:

The Expected Behavior

Able to search for new object for linking

Additional Context

Checking the timing of when this bug started, I might have forced quit Anytype :sweat_smile: right before this bug appeared, because MacOS told me Anytype stopped my MacBook to restart /shut down (perhaps because of this bug)

Edit: after two days, these objects could finally make it to search in link menus. Note: this space is not usually used, not sure if this influence the indexing speed.

Device

MacBook Air M1 / iPad Air 4

OS

Sonoma 14.5 / iPadOS 17.5.1

Anytype Version

v.0.42.3 / v.0.32.1 / v.0.44.0

Network Mode

AnySync

Technical Information

OS version: darwin arm64 14.5.0
App version: 0.42.3
Build number: build on 2024-08-02 12:17:02 +0000 UTC at #e1e3c496021c87ea0488f4a9eba8836e61a01072 (dirty)
Library version: v0.35.0

Device: iPad Air (4th generation)
OS version: 17.5.1
App version: 0.32.1
Build number: 1
Library version: v0.35.0-rc11

This report has been added to our issue tracker and received by the Development Team.

@C.c Does this issue still occur for you?

Yes. I reopened this bug for 0.44.0.

Should be fixed in the upcoming release