Blank screen after opening specific pages (Anytype 54.2)

Bug Reports Closed
,
1

WHAT IS THE BUG

I’ve moved from Notion to Anytype months ago and everything was working just fine. Most of the pages where moved without any issue and I was able to open them.

But suddely after the update to 54.2, I can’t open specific pages, after opening, Anytype shows a blank screen and I can’t change the page. I have to open a new window from the upper bar and be very fast at clicking one of the pages that doesn’t crash the app to be able to keep working.

This behavior wasn’t there in previous versions (not sure what version to be exact), I’ve not spent time to search through the versions to find the version which this behavior doesn’t appear.

I’m not sure if that is caused by the migration from Notion to Anytype, but I think so?! Maybe some pages have specific attributes or data within it that causes the app to crash. Not sure…

I thought first that maybe it has to do with the icons that I have on the pages, but I do have other pages with icons that don’t crash the app.

Note that I’m running Anytype on Ubuntu 25.10.

HOW TO REPRODUCE IT

Outline the steps needed to reproduce the behavior in sequence:

  1. Open Anytype

  2. Go to one of the pages that crashes the app

  3. Boom…

THE EXPECTED BEHAVIOR

I expect the application not to crash obviously and be able to open the page and edit it.

ADDITIONAL CONTEXT

I will include a video of the behavior.

Note: I think I’ve locked myself in this behavior for the video​:sweat_smile:… I hope this helps

TECHNICAL INFORMATION

OS version: linux x64 6.17.0-14-generic
App version: 0.54.2
Build number: build on 2026-02-16 15:18:28 +0000 UTC at #b2bd40d7e4429cd9969a75a064db1f17407adb9a
Library version: v0.48.1
Anytype Identity: A6j6GpsWT9yT93Dv25gk6UpJHUcx41WoShdhgRaXiHtKdh68
Analytics ID: MeZouHCT5DA26451pkvTNPQMKLuhBzL6C4iVwGm2aPBRDafZ
Device ID: 12D3KooWR3jc2WCUBYGwciT1JdeAf5zAtoWZtrMaqyPiWjVDNByG
Ethereum Address: 0x1fb21B3B7dC41bC7a1Ab6c3a6F31bd073E89A575

2

Hello, this problem with this crash is fixed and I will make a build today or tomorrow hopefully with a fix.

3

Release v0.54.7-alpha · anyproto/anytype-ts · GitHub this build should fix the problem.

4

Any chance that this will also fix that very similar bug?

5

yes, it does

6

Hi Razor,

First thanks for taking time to look into the issue.

I’ve had some issues (one object keeps showing in the sync but hanging) when trying to move into the alpha release, so I’ve deleted the whole application and started fresh by installing the alpha (after looking after all the files left over from the previous installation and deleting them).

When I open one of the pages that were hanging, I get this error;

image
image1849×963 57.5 KB

Syntax error, unrecognized expression: #dataviewCell-6884c58cd426ed1d0f791a5c-type-/tmp/anytype_notion_import/3422238e2e078705640caefd9430687b414f200b5d28abd961be8a054c26057e

Error: Syntax error, unrecognized expression: #dataviewCell-6884c58cd426ed1d0f791a5c-type-/tmp/anytype_notion_import/3422238e2e078705640caefd9430687b414f200b5d28abd961be8a054c26057e
    at find.error (file:///opt/Anytype/resources/app.asar/dist/js/main.js:37236:8)
    at tokenize (file:///opt/Anytype/resources/app.asar/dist/js/main.js:37902:8)
    at select (file:///opt/Anytype/resources/app.asar/dist/js/main.js:38361:20)
    at jQuery.find (file:///opt/Anytype/resources/app.asar/dist/js/main.js:36688:9)
    at jQuery.fn.init.find (file:///opt/Anytype/resources/app.asar/dist/js/main.js:38571:11)
    at new jQuery.fn.init (file:///opt/Anytype/resources/app.asar/dist/js/main.js:38681:32)
    at jQuery (file:///opt/Anytype/resources/app.asar/dist/js/main.js:35908:10)
    at file:///opt/Anytype/resources/app.asar/dist/js/main.js:795284:36
    at Qj (file:///opt/Anytype/resources/app.asar/dist/js/main.js:120090:332)
    at Hk (file:///opt/Anytype/resources/app.asar/dist/js/main.js:120132:111)
    at Wk (file:///opt/Anytype/resources/app.asar/dist/js/main.js:120129:409)
    at Pk (file:///opt/Anytype/resources/app.asar/dist/js/main.js:120127:398)
    at Ek (file:///opt/Anytype/resources/app.asar/dist/js/main.js:120119:439)
    at jg (file:///opt/Anytype/resources/app.asar/dist/js/main.js:119974:105)
    at file:///opt/Anytype/resources/app.asar/dist/js/main.js:120113:273

With the alpha release I have also the issue where one object is keeps trying to sync but not syncing. I’m not sure if that has to do with the same issue or not, but just to be sure I’m reporting everything weird I’m experiencing.

image
image563×138 11.9 KB

It seems like there is a process hanging or something like that which makes one of the processes use 100% of the scheduled cores. Note that I’ve tried to close the application completely and start again, but the same behavior keeps showing (that is the object that keeps trying to sync and never syncs).

image
image1394×120 16.9 KB

7

I will check

8

Fixed now

9

Hey Razor,

Thanks, the issue where I wasn’t able to open some pages is indeed fixed in release **v0.54.8-alpha**:heart:

There is some weirdness with the object that never syncs and I see alot of objects in different collections in my space that are untitled and cannot be opened. Are these issues related to the same bug or do I have to open different bug reports for these two issues?

Screenshot of the never synced object:

image
image561×147 11.2 KB

Screenshot of the objects that can’t open (all have the same behavior):

image
image1070×644 22 KB

image
image581×451 14.7 KB

{"level":"INFO","ts":"2026-02-27T14:53:31.292+0100","logger":"common.commonspace.headsync","msg":"sync done:","spaceId":"bafyreiaxqhb2gyvn6g22k44oaeg6kdbonvd3yqnfwaqcagylu4f5w6cnu4.1fn6mjd541dm0","newIds":0,"changedIds":0,"removedIds":0,"already deleted ids":0,"peerId":"12D3KooWEGtP8w6CtqGFi597i5HToSm8XFTBiK51NJrjLAUAfdZx"}
{"level":"INFO","ts":"2026-02-27T14:53:31.620+0100","logger":"common.commonspace.headsync","msg":"sync done:","spaceId":"bafyreif6e4ztbqbwzcvknrqxhd2ugyrhmmfwk2fdngro37hjdkc3jmto3i.1fn6mjd541dm0","newIds":1,"changedIds":0,"removedIds":0,"already deleted ids":0,"peerId":"12D3KooWEGtP8w6CtqGFi597i5HToSm8XFTBiK51NJrjLAUAfdZx"}
{"level":"INFO","ts":"2026-02-27T14:53:51.627+0100","logger":"common.commonspace.headsync","msg":"sync done:","spaceId":"bafyreif6e4ztbqbwzcvknrqxhd2ugyrhmmfwk2fdngro37hjdkc3jmto3i.1fn6mjd541dm0","newIds":1,"changedIds":0,"removedIds":0,"already deleted ids":0,"peerId":"12D3KooWEGtP8w6CtqGFi597i5HToSm8XFTBiK51NJrjLAUAfdZx"}
{"level":"INFO","ts":"2026-02-27T14:54:11.620+0100","logger":"common.commonspace.headsync","msg":"sync done:","spaceId":"bafyreif6e4ztbqbwzcvknrqxhd2ugyrhmmfwk2fdngro37hjdkc3jmto3i.1fn6mjd541dm0","newIds":1,"changedIds":0,"removedIds":0,"already deleted ids":0,"peerId":"12D3KooWEGtP8w6CtqGFi597i5HToSm8XFTBiK51NJrjLAUAfdZx"}
10

this should be moved to another bug as this is some middleware problem @Filip

12

Could you please submit a new bug report while including the debug info?

14

I had the same thing.
I ended up deleting everything and reimporting it, and this time it worked (well… except for the empty properties…).