ios , mac fail

[kavin851018]

Have you read a contributing guide?

• I have read CONTRIBUTING.md
• I have searched the existing issues and didn't find any that were similar
• I have considered creating a pull request with fixes instead of a bug report and want to proceed

Current Behavior

i update ios app , mac app , self-host docker compose to latest version , then windows app works correctly , ios app and mac app show the remote storage is full , the docker compose logs shows like below

any-sync-node-2-1 | 2025-06-17T13:18:02.335Z INFO net.transport.quic accept error {"localAddr": "172.18.0.9:1012", "error": "IncompatibleVersion"}

Expected Behavior

sync correctly

Steps To Reproduce

i update ios app , mac app , self-host docker compose to latest version , then windows app works correctly , ios app and mac app show the remote storage is full

Environment

- OS:
- Version:

Anything else?

No response

[fb929]

could you provide the versions of all clients, please?
as well as the version of the self-hosted server?

[kavin851018]

this is ios version
裝置：iPhone17,2

作業系統版本：18.5
應用程式版本：0.38.4
建置版本：1
資料庫版本：v0.41.0-rc16

this is windows version
0.46.5 on windows 11

[kavin851018]

i use this commit to docker compose up

d9b7e95

[kavin851018]

Container: 92d810e60f6e, Image: ghcr.io/anyproto/any-sync-tools:latest, Image ID: sha256:59a971222505c3f2853c263e1ffa659c319ece448a982b03837cf9eb90fd40dd
Container: c2f9d1ee6950, Image: ghcr.io/anyproto/any-sync-consensusnode:v0.2.2, Image ID: sha256:7e664d79c6eb5588201d7b62c318bf445e6ef94d36ddb517f5bb66e75a5d48a3
Container: 84b677ebff4c, Image: ghcr.io/anyproto/any-sync-node:v0.4.13, Image ID: sha256:80f10cd99181494444a6757c7ee7664b5879d307071028e559580f24d5216de9
Container: 6844e7a319f9, Image: ghcr.io/anyproto/any-sync-filenode:v0.8.5, Image ID: sha256:2b21463b09b59ae06fc3fcf1f5fede0eef0ef3c514af823bd2af78f40521ee40
Container: db73b618ebd2, Image: ghcr.io/anyproto/any-sync-node:v0.4.13, Image ID: sha256:80f10cd99181494444a6757c7ee7664b5879d307071028e559580f24d5216de9
Container: 25fe0ee89633, Image: ghcr.io/anyproto/any-sync-node:v0.4.13, Image ID: sha256:80f10cd99181494444a6757c7ee7664b5879d307071028e559580f24d5216de9
Container: 32a92ed0c7a4, Image: ghcr.io/anyproto/any-sync-coordinator:v0.4.4, Image ID: sha256:387226b1e23cb3104d9b67eca7c6652f8311fc066b0ed985d3e38bd691b18c30
Container: f5f5549e3546, Image: mongo:7.0.2, Image ID: sha256:ee3b4d1239f12b094c4936dd08a2fbc227300beaf784c46c509e2f1ac5e6d879
Container: 96c828f49375, Image: redis/redis-stack-server:7.2.0-v6, Image ID: sha256:ebee26a6f06392afaa518dd7fb4b8753e1f0400889123d144928aaeed3d12dd4
Container: b113c7c761b4, Image: minio/minio:RELEASE.2024-07-04T14-25-45Z, Image ID: sha256:a9368d642903a117fc2ba7637e09737ea295a499182e5a56178e8081a89e3fe0
Container: 22537fbb6f4e, Image: nginx:latest, Image ID: sha256:be69f2940aaf64fdf50c9c99420cbd57e10ee655ec7204df1c407e9af63d0cc1
Container: 68b02c23ae78, Image: langgenius/dify-plugin-daemon:0.1.1-local, Image ID: sha256:e7cb9c9d11e243f649780540e02ec78fd784cab64750184ece234fc1e49bc758
Container: 8e20f732d641, Image: langgenius/dify-api:1.4.1, Image ID: sha256:85919d954b5a4da8d771f67b20ebd3bff802f8bc6e989678e4c497e2d8a796f8
Container: b752430cf2cd, Image: langgenius/dify-api:1.4.1, Image ID: sha256:85919d954b5a4da8d771f67b20ebd3bff802f8bc6e989678e4c497e2d8a796f8
Container: 87009f89a607, Image: ubuntu/squid:latest, Image ID: sha256:feec1ad0ab0a802905433f9f4350cdd839885ebc6885281ace0ebe27a034df93
Container: f1dda21a7a5f, Image: langgenius/dify-web:1.4.1, Image ID: sha256:cd4fce61b9bd8c236d28d72e0bebcd0efed89659594cdb39b65cb1a20512007a
Container: 95a21281512a, Image: semitechnologies/weaviate:1.19.0, Image ID: sha256:8ec9f084ab23a47d00af39a7a879fc81534c3bf2b6712dd1d48aa799f301a7ac
Container: 9a1be2d77f84, Image: postgres:15-alpine, Image ID: sha256:e7599937cc85d3d711d1f85ad58128fda677279427b56801cefe3cb516b828fb
Container: 884bd0191dc9, Image: redis:6-alpine, Image ID: sha256:70b635414ee205c8afc61f2ca6d702ab542f3f0f59ffe5d2bfcd7b5942857226
Container: 1cf6decc1fcd, Image: langgenius/dify-sandbox:0.2.12, Image ID: sha256:ba1b250b95055bf8c8a5e70aba0448117358fe27c14a91754bf1c121f9cd97ff
Container: 19f6006eb037, Image: ghcr.io/danny-avila/librechat-dev:latest, Image ID: sha256:7312a08b69508835fbd96b554e37fcbb5e9fb3d40f59a25ef126db6fccfe5c54
Container: f4b5bc9ceb40, Image: ghcr.io/danny-avila/librechat-rag-api-dev-lite:latest, Image ID: sha256:095db2c2ff3b428e9c7b14b5128d393c36462609f6f660285775694b2ea9ec49
Container: fe076b05fae4, Image: mongo, Image ID: sha256:6551ff2e441be3fc2daa18db66670724e9e822ca116dd3af668a6a9f44c30126
Container: 11d1c6c7f293, Image: ankane/pgvector:latest, Image ID: sha256:f2c967e41f72b294e2b96f25154dda38dbde3603b3be33888fb437147972f24b
Container: 8610ba31e0ee, Image: getmeili/meilisearch:v1.12.3, Image ID: sha256:9547aac4aabca4f08693680112e794ec8bad21b7c9020b87f206c86f421dbb13
Container: 61fe66096155, Image: anki-sync-server, Image ID: sha256:a6aa5fedef533dae426016cbab682b3698302b82da7ba735b394527592070b52

[jdreinhardt]

I am also experiencing the same issue, but across all the latest desktop client versions. Clients won't connect to the server.

Server: v6.3.0 (commit d9b7e95)
macOS (15.5): 0.46.8
Windows (10 22H2): 0.46.8
Linux (Flatpak): 0.46.8

If I switch to an older version of the client (0.46.0) on the Mac and Windows then the desktop will connect and sync as expected. My linux system was a bit out of date, and was on 0.46.5 before I updated it. On that version it would connect to the server, but the sync icon was yellow, not the standard green. After the update to 0.46.8 it will also no longer connect to the server.

The logs are full of IncompatibleVersion errors like these:

any-sync-node-3-1 | 2025-06-18T14:52:26.017Z INFO net.transport.yamux incoming connection handshake error {"error": "IncompatibleVersion", "remoteAddr": "XXX.XXX.XXX.XXX:64731"} any-sync-node-1-1 | 2025-06-18T14:52:26.018Z INFO net.transport.yamux incoming connection handshake error {"error": "IncompatibleVersion", "remoteAddr": "XXX.XXX.XXX.XXX:64733"} any-sync-node-2-1 | 2025-06-18T14:52:26.018Z INFO net.transport.yamux incoming connection handshake error {"error": "IncompatibleVersion", "remoteAddr": "XXX.XXX.XXX.XXX:64734"}

any-sync-coordinator-1 | 2025-06-18T14:53:44.455Z INFO net.transport.quic accept error {"localAddr": "172.18.0.9:1014", "error": "IncompatibleVersion"} any-sync-node-1-1 | 2025-06-18T14:53:44.458Z INFO net.peerservice can't connect to host {"rootOp": "periodicCall", "addr": "quic://XXX.XXX.XXX.XXX:1014", "error": "IncompatibleVersion"} any-sync-coordinator-1 | 2025-06-18T14:53:44.458Z INFO net.transport.quic accept error {"localAddr": "172.18.0.9:1014", "error": "Application error 0x3 (remote): outbound handshake failed"}

For completeness, mobile clients do work correctly. They can connect to the server and sync as expected.
Android (15): 0.38.20
iOS (26.0 Dev Beta 1): 0.38.4

[elaiel]

I can confirm the same behavior on my windows (11) machines and in Debian after I updated the desktop client to 0.47.2 and 0.47.3
can't connect to host {"addr": "...", "error": "IncompatibleVersion"}

[serml]

Same issue, but only when trying to share.

[fb929]

Container: 84b677ebff4c, Image: ghcr.io/anyproto/any-sync-node:v0.4.13, Image ID: sha256:80f10cd99181494444a6757c7ee7664b5879d307071028e559580f24d5216de9

@kavin851018 the version of any-sync-node is too old.
please check that there are no specific versions in your .env.override, and then update the environment by running:

make update

[elaiel]

This fixed the issue for me! Thanks!!

[jdreinhardt]

@fb929 running make update does resolve the issue. Is there a mechanism in the server to detect container updates? I've monitored this repo in the past, but it hasn't updated in a couple of weeks, so I was unaware there were outstanding updates. Should I monitor https://puppetdoc.anytype.io/api/v1/prod-any-sync-compatible-versions/ for when to run the update, or is there a recommended best practice?

[kavin851018]

Container: 84b677ebff4c, Image: ghcr.io/anyproto/any-sync-node:v0.4.13, Image ID: sha256:80f10cd99181494444a6757c7ee7664b5879d307071028e559580f24d5216de9

@kavin851018 the version of any-sync-node is too old. please check that there are no specific versions in your .env.override, and then update the environment by running:

make update

this does fix the issue , however windows version keep showing yellow light now

[kavin851018]

after download 0.47.3 windows version , yello light issue fixed , thanks !!

[fb929]

@fb929 running make update does resolve the issue. Is there a mechanism in the server to detect container updates? I've monitored this repo in the past, but it hasn't updated in a couple of weeks, so I was unaware there were outstanding updates. Should I monitor https://puppetdoc.anytype.io/api/v1/prod-any-sync-compatible-versions/ for when to run the update, or is there a recommended best practice?

yes, we do have a version update mechanism - it uses the API you mentioned.

You can either:

• monitor version changes in this API
• Or keep an eye on client updates, as server updates are typically released in tandem with new client versions.