Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Cancelling a swipe delete leaves the session row stuck showing the red delete background

Open
#82 1 comment 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

@gnacho is already working on this.

Since Oct 26, 2026.

  • #83 by @gnacho — open

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
35/100
Issue type
Bug
Clarity
Clearly specified
Activity status
Stale
Tech stack
android, kotlin
Domain
frontend, mobile

Research direction

Start at the sessions list and trace the swipe-to-delete and confirmation Cancel flow in the Android app. Reproduce by swiping a row fully, tapping Cancel, then scrolling it off screen and back; inspect how the row’s swipe state is retained or reset. Done means Cancel restores the row and later swipes work normally. An open pull request already addresses this issue.

Written by the indexing model from the issue text.

Description

What happened?

Swiping a session row all the way opens the delete confirmation. Tapping Cancel leaves the row stuck mid-swipe with part of the red delete background and the trash icon visible. The row ignores later swipes, and the only way I found to recover it is force-closing the app.

Scrolling the stuck row off screen and back opens the delete confirmation again without a gesture. I expected Cancel to return the row to its resting position and let me swipe it again.

Steps to reproduce
  1. Open the sessions list.
  2. Swipe a row all the way to open the delete confirmation.
  3. Tap Cancel.
  4. Scroll the stuck row off screen and back.
App version

0.6.0 (debug build)

OpenCode server version

2.1.4

Device and Android version

Android emulator, Android 16

Screenshots or screen recording

Not attached because they would show private sessions.

Dominant language
Kotlin
Stars
1
Forks
0
Avg merge
10h 22m
Merged PRs (30d)
38

Getting set up

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 beppe2880/opencode-mobile

All issues in beppe2880/opencode-mobile

Similar issues

More Kotlin issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.