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
Have an existing Anytype account with established Tag or Status relations.
Log in to this account on a new mobile device for the first time.
After the account syncs, try to edit any object’s Tag or Status relation.
Observe that the relations are locked and uneditable.
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.
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
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.
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.
@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