Any-sync: file contents are not synchronized

WHAT IS THE BUG

Environment: selfhosted

When uploading a file in the desktop app only its object data / metadata is synchronized to the android app not its content.

HOW TO REPRODUCE IT

  1. on desktop

    1. create a new space
    2. create a new collection
    3. drag & drop a file to this collection
  2. on android (with “unlimited offline downloads” activated)

    1. wait for synchronization to finish (steady green dot icon)
    2. activate flight mode
    3. open file
  3. error: “get reader: get node peer: unable to connect”

  4. Workaround: open the file on android after synchronization finishes (steady green dot) and before activating flight mode.

THE EXPECTED BEHAVIOR

File content should be synchronized/downloaded to android device when synchronization icon states that synchronization has finished.

Since the workaround is not suitable for a large set of files, this bug prevents anytype from being used as a shared document storage solution.

ADDITIONAL CONTEXT

Possibly related: Missing image/file attachments in spaces created during temporary network misconfiguration (Broken spaceId/fileId -> cid binding) · Issue #2227 · anyproto/anytype-ts · GitHub

TECHNICAL INFORMATION
Desktop: Top Menu > Help > Tech Info
OS-Version:

linux x64 6.1.0-30-amd64

App-Version:

0.55.4

Versionsnummer:

build on 2026-05-04 16:31:34 +0000 UTC at #545ed723e3e227b1f0906ec57aaf4adea24d06ec

Bibliotheksversion:

v0.50.4

Mobile: Profile > About > Tech info:

App-Version: 0.46.12

Build-Nummer: 4612

Bibliotheksversion: 0.50.4

More info on this. The cloud version has the same bug.

Steps to reproduce:

  1. Create a new anytype account on device A (pc)
  2. Create a new collection in the newly created space
  3. Upload a file (e.g. txt-file) to this collection via drag&drop
  4. Connect another (android) device B to this account (via QR code)
  5. Activate unlimited offline space
  6. DON’T click the file’s object created in step 3 yet)
  7. intermediate result: Objects and metadata are synchronized to device B.
  8. Deactivate network connection on device B
  9. open the file’s object created in step 3 on device B
  10. Click on “download”
  11. Error: “net::ERR_FILE_NOT_FOUND”
    (alternatively: “get reader: get node peer: unable to connect”, see first post)