Dimillian / Dimillian/IceCubesApp
Bug: Fulle timeline fetch can loses your position if app is used while fetch happens
Nobody has claimed this yet.
- Dominant language
- Swift
- Stars
- 7.1k
- Forks
- 720
- PR merge metrics
- No merged PRs in 30d
Description
Environment:
- OS:
iOS 26.1 - IceCubesApp version:
2.1.2
Description
- Active full timeline fetch
- Go to bed
- Open the app and tap any post
- Give timeline fetch some time to complete, look through the replies maybe
- Back of from the post, the timeline is now updated but you're at the top of it instead of the last position.
I noticed the issues specifically when viewing post details and have confirmed it is repeatable. It is possible that other things that hide the timeline like switching tabs or opening settings would have the same result.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Reproduce the issue by starting a full timeline fetch, opening a post, waiting for the fetch to complete, and returning to the timeline. Trace the timeline update and position restoration around post details and other views that hide the timeline. Done means returning to the previous timeline position instead of the top after the fetch completes.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- ios, swift
- Domain
- mobile
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100