Some Queries are reset after updating to 0.46.21-beta

Bug Reports Closed
,
1

What’s The Bug?

After updating to 0.46.21-beta, some Queries reset and show up empty. It looks like they’ve lost their query option. “Select Query” and “No query selected” are displayed.

How To Reproduce It

  • Update to 0.46.21-beta.
  • Open some Queries. Some of them work as expected, others are empty.

Image or Video

queries.png
queries.png1458×543 18.6 KB

The Expected Behavior

Queries retain their query option and display objects correctly.

Additional Context

The Query can be manually restored by clicking “Select Query” and selecting the desired query again.

Device

PC

OS

Fedora 41

Anytype Version

0.46.21-beta

Network Mode

AnySync

Technical Information

OS version: linux x64 6.13.12-200.fc41.x86_64
App version: 0.46.21-beta
Build number: build on 2025-05-09 13:52:57 +0000 UTC at #484511e5a6f995ad13d53ae347fa5f60575229af
Library version: v0.41.0-rc3
Anytype Identity: A7kLNo65RFUGs8dZab3DBxrHYDJ6FrszGdSzks9GYXgfiqLc
Analytics ID: ABCxkJgcj9adfaQyFuWM8m9oQpDWV7fa9GSdAeWM1fFf18VZ
Device ID: 12D3KooWPT1WmYsZKP5bFV933NYUmzjQLDnrS8wHyCkyC2xp46v1
Ethereum Address: 0xe1716Ca928159bA1686D569D5d64ac615AF2893a

2

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

4

Hello @boots !

Do you have any broken queries left or you fixed all by resetting type?
If you still have can you please share dubug info: Open Query → Debug → Current object debug

Btw did you try to update to latest version?

5

Greetings @kirillston !

The queries that I manually fixed are all working correctly, and they persist between restarts.

Yes, I managed to find another broken query. I didn’t touch it. This is how it looks (basically the same as the Notes query in OP):

broken query
broken query1471×579 15.2 KB

I tried updating to v0.46.30-alpha but unfortunately it’s still broken.

This is the debug info:

at.dbg.{bafyreicma44lnrcvtewvxj3prenoa2p75uve42vgnzbvkajx3ppynvq6oa bafyreiedjuaxk3rtmtfxduzdnueyr7ze3xuupilhrpsbftahal3m22jpda.2pp341uqdixk6}.20250523.183759.17.zip (30.4 KB)

6

Oh, I see we had a pretty ancient mechanism that transformed old relation ids to new one. It became necessary with multi-space coming, as similar relations need to have different ids in different spaces. It seems it didn’t work for you.

Do you remember from what version did you update approx?

7

I see, thanks for the explanation :+1:

If I remember correctly the issue started after updating from 0.46.5 to 0.46.21-beta.

10

Hello @boots !
Try to update to 0.46.8. We’ve returned mechanism that used to migrate ids of old types and relations

11

Hello @kirillston , I confirm that on 0.46.8 the issue is fixed for me. Thanks!

12

That’s good! Happy to help!

13

Hey, @boots, could you please check one more time to make sure everything was fixed properly?

14

Hi @Filip ,

I checked all my queries one by one, both on 0.46.8 and on 0.46.42-beta. Everything’s ok :+1:

15

This issue has been fixed by the Development Team and will be implemented in an upcoming release.