Some custom properties are locked and uneditable

What’s The Bug?

A critical bug that was previously fixed has reappeared.

Part of my relations that use the “Tag” or “Status” type are locked and can no longer be edited. This regression bug appeared yesterday, immediately after I logged into my Anytype account on a new mobile phone.

How To Reproduce It

  1. Have an existing Anytype account with established Tag or Status relations.
  2. Log in to this account on a new mobile device for the first time.
  3. After the account syncs, try to edit any object’s Tag or Status relation.
  4. Observe that the relations are locked and uneditable.

Image or Video


The Expected Behavior

Logging into a new device should not affect existing data structures. All relations should remain fully editable, just as they were before the new device login.

Additional Context

This is the exact same bug that I (and others) experienced starting on October 28, 2023.
That original issue was documented in a forum post titled:

That bug was not resolved until June 5, 2024. It is very concerning to see this identical, severe issue return.

Device

ROG Zephyrus G16, Huawei Mate XTs

OS

Windows 11, Harmony OS 5(based on Android)

Anytype Version

0.50.5(windows) & 0.40.19-beta(Android)

Network Mode

AnySync

Technical Information

Mobile:
设备:GRL-AL20 HUAWEI
Android 版本:31
应用版本:0.40.19-beta
构建号:4019
库版本:0.44.6
账户 ID: A8GnWbFf93jy9cCKmv9x93camzT7zZwwtqVSFq7TJNhMhfqe
设备 ID: 12D3KooWGh9TL4ubhZ1ZzHA7AxjcviGKsZqjQffWiPChsDibifv8
分析 ID: 560e3ed8-ebb9-4b0c-8f31-a65b2d69f002以太坊密钥 ID: 0xa0706E7E1D3dF0c2EC372bf2cE88fa5b5616Db9a

Desktop:
OS version: win32 x64 10.0.26200
App version: 0.50.5
Build number: build on 2025-10-08 15:40:01 +0000 UTC at #e368dc067e79f7bf281ed5104e5f18df5fb21b04
Library version: v0.44.5
Anytype Identity: A8GnWbFf93jy9cCKmv9x93camzT7zZwwtqVSFq7TJNhMhfqe
Analytics ID: 560e3ed8-ebb9-4b0c-8f31-a65b2d69f002
Device ID: 12D3KooWRYaumej8pDjheX2G6HvHJTh7YRQnBv1CZv4TZkwieSE9
Ethereum Address: 0xa0706E7E1D3dF0c2EC372bf2cE88fa5b5616Db9a

Any response?

???:sweat_smile:

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

Hey Richard, sorry for the delayed response. Could you please confirm whether the properties are locked and/or cannot be edited on both your desktop and mobile devices?

As shown in the screenshot, I can confirm that these properties are locked/uneditable on both the desktop and mobile devices. I think this is exactly the same situation as the one I reported in 2023: All relations with tag or status, which I created, are locked and unbale to be edited - #68 by RichardZ . However, judging from the discussions back then, it seems there might be more than one factor causing this bug

is there any update?

Could I get a definitive answer on whether or not you plan to fix this bug? It has been over two months, and as a paying user, I don’t believe it is fair that I cannot even get a simple confirmation regarding its status. I would appreciate a clear response.

Hey @RichardZ , we’re currently looking into your issue. We’ll let you know as soon as we have an update!

@RichardZ Could you please confirm that you’ve already updated to 0.53.1 and that the issue persists?

Yes I can confirm.

During the previous occurrence in 2023, there was a situation where a “fix” was released that worked for some users, but many others (including myself) remained stuck.

For more technical context, I would like to point back to my previous thread [All relations with tag or status, which I created, are locked and unbale to be edited - Bug Reports / Closed - Anytype Community], where the Anyteam friend @requilience eventually provided a specific solution(I guess) that addressed my case.

@RichardZ it is completely strange why this issue has come to my hands only now. Sorry for this.

You are absolutely right. We have designed a nice migration that has fixed readonly relations with Tag and Status format 2 years ago. And we accidentally broke it this autumn. I have resurrected migration, so your relations must be fixed with next release

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