AppFlowy-IO / AppFlowy-IO/AppFlowy

[Bug] Select/Status filter fails to sync and render correctly on Android mobile app

Open
#8,806 1 comment 0 reactions 0 assignees View on GitHub
Dominant language
Dart
Stars
76.6k
Forks
6k
PR merge metrics
No merged PRs in 30d

Description

### Bug Description

There is a synchronization and rendering issue between the AppFlowy Desktop (Windows) and Android mobile applications regarding database filters. When a row's status property (Select/Select option) is updated on the desktop app, the filter on the Android app fails to recognize this change automatically, even though the data itself seems to be synced. The filtered view remains empty or outdated until the status is manually toggled on the mobile device.

### How to Reproduce

Create a database on the Desktop application with a "Select" or "Status" property (e.g., Status options: "A-team", "B-team").

Set up a database view filtered by this status (e.g., Filter: Status = A-team).

Assign the "A-team" status to a new or existing row on Desktop. The desktop view updates correctly.

Open the Android mobile application and navigate to the same filtered database view.

Issue: The newly updated row does not appear in the filtered view on Android, despite the background sync being active.

Workaround: If you tap on the row on mobile, remove the "A-team" status, and then re-assign the "A-team" status directly in the mobile app, the row instantly appears in the filtered view.

### Expected Behavior

The Android app's database filters should react dynamically to data changes synced from the desktop version without requiring manual re-triggering or re-assigning of the filtered properties on the mobile device.

### Operating System

Android

### AppFlowy Version(s)

0.12.2 (29120201)

### Screenshots

_No response_

### Additional Context

_No response_

Contributor guide

No contributing guide indexed for this repository

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.