Data corruption of types and their relations

WHAT IS THE BUG

app goes all black, relations disappear from types, names of types get lost

HOW TO REPRODUCE IT

  1. Create types named A, B
  2. Create relation on A of type object allowing B
  3. Create objects of A as a and B as b and fill the relation a → b
  4. Change type of b to something else
  5. Edit relation on a, hover over “limit object types”
  6. Screen goes blank, app needs a kill
  7. After restart the names of all manualy created types change to “Untitled”, relations defined for all types are gone

THE EXPECTED BEHAVIOR

No creash, names of types remain as I enter them. Relations of types remain as defined.

SYSTEM INFORMATION

  • OS:
    Linux debian 6.1.0-2-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.1.7-1 (2023-01-18) x86_64 GNU/Linux
  • Device:
    Desktop / Intel(R) Core™ i7-6700 CPU @ 3.40GHz
  • Anytype Version:
    0.30.0

ADDITIONAL CONTEXT

  • There was no object of type B left when the error first occurred
  • I see this error repeatedly in the logs since the defect appeared:
    {“level”:“error”,“ts”:“2023-01-27T19:32:12.784+0100”,“logger”:“anytype-localstore”,“caller”:“objectstore/objects.go:2337”,“msg”:“GetObjectType failed to get relation key from id: datastore: key not found (rel-aperture)”}
3 Likes

@rim Thanks for reporting. Would you be able to get a screen recording of this bahavior?

I tried to reproduce on video but failed.

Have same problem – suddenly Anytype screen become blank & needs a kill – on Windows 11 Build 25284.1000 (Anytype 0.30.0)

All of my relations created on Jan, 29th 2023 changed to Untitled. Sync doesn’t work even between devices (Win11 & Android 13 with Anytype 0.13.2) in the same Wi-Fi network.

1 Like

It happened again with the new account. I don’t remember doing anything weird but after a restart all type’s names were reset to “Untitled”. And now I can reproduce the issue again on each restart of the application.

This time there was no strange behaviour beforehand like the app freezing or crashing.

3 Likes

Tested with 0.31.0, can’t reproduce error anymore. Good.

Please, mark as solving any meaningful answer :smiley: