[Bug] Desktop Client v0.14.10 Fails to Render Database Views Despite Successful Server Responses (Web Version Works Perfectly)

Open
#9,089 3 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
48/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Active
Tech stack
dart, flutter, postgresql

Research direction

Start by comparing how the Web and Desktop clients load database views and receive updates; the issue names no source files or tests, so first locate the desktop database view and sync entry points. Reproduce with the same self-hosted backend and inspect client-side logs while opening a view and changing a row in Web. Done when Desktop renders the view correctly and reflects Web changes without a manual refresh.

Written by the indexing model from the issue text.

Description

Bug Description

The Desktop Client (v0.14.10 on Linux) fails to properly render and sync database views, even though:

  1. Server returns HTTP 200 + successful responses for all operations
  2. WebSocket connection is healthy (verified via connection test)
  3. Web version works perfectly with the exact same self-hosted backend
  4. Server logs show "outcome":"success" for all database operations
  5. Data exists and is accessible (confirmed via Web version)

The issue is 100% isolated to the Desktop Client. The same database views that display correctly in the Web version either fail to load, display incorrectly, or require manual refresh to show updates made from the Web version.

This is a critical bug that undermines the core value proposition of having a native Desktop application, as users are forced to rely on the Web version for reliable database operations.

How to Reproduce
  1. Set up AppFlowy Cloud v0.19.10 self-hosted via Podman (all services healthy: database, redis, websocket, nginx)
  2. Open Web version (localhost) and create/open a database with views (e.g., "Plan Weak")
  3. Verify the view displays correctly with all rows and columns
  4. Open Desktop Client v0.14.10 connected to the same self-hosted backend
  5. Navigate to the same database and attempt to open the same view
  6. Observe: View either fails to load, displays incorrectly, or shows stale data
  7. Make a change in Web version (add row, modify field)
  8. Wait 60+ seconds
  9. Check Desktop Client → Changes NOT visible
  10. Manual refresh or app restart required to see updates

Expected: Real-time sync between Web and Desktop via WebSocket
Actual: Desktop requires manual intervention to reflect Web changes

Expected Behavior

Desktop Client should:

  1. Render database views identically to Web version
  2. Sync changes in real-time (<5 seconds) via WebSocket
  3. Display all columns, rows, and formatting consistently
  4. Not require manual refresh to show updates made from Web version

Both clients should provide identical user experience when connected to the same backend.

Operating System

CachyOS (Arch Linux-based distribution)

AppFlowy Version(s)
  • Desktop Client: v0.14.10 - Self-Hosted Server (Cloud): v0.19.10 - Deployment: Podman/Podman-compose
Screenshots

Screenshot 1: Web Version - View Displays Correctly

Image

Screenshot 2: Desktop Client - View Fails to Render Properly

Image

Screenshot 3: Connection Test - Both HTTP and WebSocket Healthy

Image
Additional Context

Server Infrastructure Status (All Healthy)

Running Containers:
  • ✅ appflowy-cloud_appflowy_cloud_1 (main backend)
  • ✅ appflowy-cloud_postgres_1 (database - healthy)
  • ✅ appflowy-cloud_redis_1 (cache)
  • ✅ appflowy-cloud_minio_1 (storage - unhealthy but functional)
  • ✅ appflowy-cloud_gotrue_1 (auth - healthy)
  • ✅ appflowy-cloud_appflowy_search_1 (search - healthy)
  • ✅ appflowy-cloud_nginx_1 (reverse proxy)
  • ✅ appflowy-cloud_appflowy_web_1 (web frontend)
  • ✅ appflowy-cloud_appflowy_worker_1 (background tasks)
  • ✅ appflowy-cloud_ai_1 (AI service - healthy)
  • ✅ appflowy-cloud_admin_frontend_1 (admin panel)
Connection Verification:
  • HTTP API: 200 OK (Duration: 5ms)
  • WebSocket: 101 Switching Protocols (Duration: 2ms)
  • Same host and port: Yes

Server Logs Analysis

1. Main Backend Logs (appflowy_cloud)

All operations return success with no errors:

{"timestamp":"2026-10-21T16:09:44.907141Z","level":"INFO","fields":{"message":"Startup state changed: initializing -> database_ready (component: Database ready)"},"target":"appflowy_cloud_core::startup_state","filename":"libs/appflowy-cloud-core/src/startup_state.rs","line_number":204}

{"timestamp":"2026-10-21T16:09:45.001858Z","level":"INFO","fields":{"message":"Startup state changed: database_ready -> redis_ready (component: Redis ready)"},"target":"appflowy_cloud_core::startup_state","filename":"libs/appflowy-cloud-core/src/startup_state.rs","line_number":204}

{"timestamp":"2026-10-21T16:09:45.001892Z","level":"INFO","fields":{"message":"building named redis connection manager","redis":"redis://redis:6379","redis_manager":"collab_cache"},"target":"appflowy_cloud::application","filename":"src/application.rs","line_number":3036}

#### Database row creation operations (all successful):
{"timestamp":"2026-10-21T16:22:40.277762Z","level":"INFO","fields":{"message":"atomic page creation completed","operation":"database_row.default.v1","workspace_id":"ad28d34c-478c-4ab8-9570-39dd77ab021b","logical_request_id":"f188a9aa-2db7-4db5-91b2-a31a1e44806a","http_span_id":105834866121113601,"stage":"lifecycle_release","outcome":"success","failure_reason":"none","boundary":"owner","stage_elapsed_ms":"{\"admission\": 0, \"authorization\": 1, \"cache_cleanup\": 0, \"encode\": 4, \"folder_metadata_reservation\": 0, \"folder_publication\": 0, \"lifecycle_guard\": 0, \"lifecycle_release\": 0, \"permission_update\": 0, \"persistence\": 20, \"preparation\": 0, \"publication\": 10, \"restore_check\": 0, \"source_admission\": 0, \"source_read\": 8}","response_ready_ms":48,"commit_outcome":"applied","elapsed_ms":48},"target":"appflowy_cloud_pages::creation_observation","filename":"libs/appflowy-cloud-pages/src/creation_observation.rs","line_number":455,"span":{"client_version":"0.14.10","device_id":"8c5d2d73-453c-4405-92b0-d6bd57ce2e62","method":"POST","path":"/api/workspace/{workspace_id}/v2/database/{database_id}/row/default","payload_size":392,"request_id":"a1e154941861ed7561c04e6fdd38f005","name":"request"}}

#### 2. Worker Logs (appflowy_worker)
{"timestamp":"2026-10-21T16:10:14.582602Z","level":"INFO","fields":{"message":"[Folder][Cache] recover_pending: no pending folder streams found"},"target":"folder::cache"}

{"timestamp":"2026-10-21T16:10:14.582613Z","level":"INFO","fields":{"message":"Worker startup: ready -> ready (Folder Cache Warm-Load ready)"},"target":"appflowy_worker::startup_state"}

{"timestamp":"2026-10-21T16:10:44.594812Z","level":"INFO","fields":{"message":"Completed automatic Folder snapshot frontier migration","marker":"completed:0.19.10"},"target":"appflowy_worker::repair::folder_snapshot_frontier_repair"}


####  3. Search Logs (appflowy_search)
{"timestamp":"2026-10-21T16:39.499382Z","level":"INFO","fields":{"message":"maintenance cycle complete"},"target":"search::maintenance","filename":"services/appflowy-search/src/biz/maintenance.rs","line_number":211}

{"timestamp":"2026-10-21T16:39.537088Z","level":"INFO","fields":{"message":"storage pressure cleared; resuming normal poll cadence","kind":"content"},"target":"search::keyword","filename":"services/appflowy-search/src/biz/lmdb_worker.rs","line_number":257}

#### 4. Nginx Configuration
# WebSocket
location /ws {
    proxy_pass $appflowy_cloud_backend;
    proxy_http_version 1.1;
    proxy_set_header Upgrade $http_upgrade;
    proxy_set_header Connection "Upgrade";
    proxy_set_header Host $host;
    proxy_set_header X-Real-IP $remote_addr;
    proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
    proxy_set_header X-Forwarded-Proto $scheme;
    proxy_read_timeout 86400s;
}
Dominant language
Dart
Stars
79.1k
Forks
6.3k
Avg merge
17h 29m
Merged PRs (30d)
1

Getting set up

  • No Dockerfile or Docker Compose file
  • Has a pull request template
  • No contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from AppFlowy-IO/AppFlowy

All issues in AppFlowy-IO/AppFlowy

Similar issues

More Dart issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.