[GH-ISSUE #8476] [Bug] can't access 1st row in grid view in iPhone app #3871

New issue

Closed

opened 2026-03-23 21:33:46 +00:00 by mirror · 1 comment

mirror commented

2026-03-23 21:33:46 +00:00

Owner

Originally created by @RobpokeDev on GitHub (Feb 9, 2026).
Original GitHub issue: https://github.com/AppFlowy-IO/AppFlowy/issues/8476

Bug Description

After several tests I can confirm that on iPhone 17 the Appflowy app will not let me click the title or any properties of the first row in a grid view.

How to Reproduce

Create entries in a grid view using the iPhone app on iPhone 17. The top entry (1st row) can not be tapped in any way. The other tasks can be dragged to the 1st row but once they are on top they can no longer be clicked and values can not be changed on the top row.

Expected Behavior

The top row should behave like the other rows.

Operating System

iOS latest

AppFlowy Version(s)

0.11.1 (5)

Screenshots

Additional Context

No response

Originally created by @RobpokeDev on GitHub (Feb 9, 2026). Original GitHub issue: https://github.com/AppFlowy-IO/AppFlowy/issues/8476 ### Bug Description After several tests I can confirm that on iPhone 17 the Appflowy app will not let me click the title or any properties of the first row in a grid view. ### How to Reproduce Create entries in a grid view using the iPhone app on iPhone 17. The top entry (1st row) can not be tapped in any way. The other tasks can be dragged to the 1st row but once they are on top they can no longer be clicked and values can not be changed on the top row. ### Expected Behavior The top row should behave like the other rows. ### Operating System iOS latest ### AppFlowy Version(s) 0.11.1 (5) ### Screenshots <img width="1206" height="2622" alt="Image" src="https://github.com/user-attachments/assets/8a568485-6325-46dd-812e-cdd650128a97" /> ### Additional Context _No response_

mirror closed this issue

2026-03-23 21:33:46 +00:00

mirror commented

2026-03-23 21:33:47 +00:00

Author

Owner

@greatnose619 commented on GitHub (Feb 10, 2026):

Hi, thanks for the report. We’ll look into it and fix the issue asap.

@greatnose619 commented on GitHub (Feb 10, 2026): Hi, thanks for the report. We’ll look into it and fix the issue asap.