DimensionDev / DimensionDev/Flare
[Bug] Twitter Mentions tab does not sync automatically until opened on official web
Nobody has claimed this yet.
- Dominant language
- Kotlin
- Stars
- 1.5k
- Forks
- 67
- Avg merge
- 11h 8m
- Merged PRs (30d)
- 84
Description
Summary
Twitter "Mentions" tab does not refresh automatically unless manually visited on the official web client.
Environment
- App Version: 1.7.4(5172)
- OS / Platform: Android 16
- Account Type: Twitter (via Web API login)
Steps to Reproduce
- Receive a new reply/mention on Twitter.
- Open Flare and check the Notifications section.
- The "All" tab receives the notification correctly, but the "Mentions" tab does not show the new mention (remains stale even after pull-to-refresh).
- Open the official Twitter web client in a browser and navigate to the "Mentions" tab once.
- Go back to Flare and pull to refresh — the missing mentions now appear immediately.
Expected Behavior
The "Mentions" tab should automatically poll and sync new mentions alongside the "All" notifications stream, without requiring manual activation via the official web client.
Suspected Root Cause
It seems the background polling or refresh worker only queries the global notifications endpoint (notifications/all) and lacks independent periodic polling or unread cursor synchronization for the notifications/mentions endpoint.
Contributor guide
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
Start by locating the Android notification polling or refresh worker and the code handling the notifications/all and notifications/mentions endpoints. Reproduce the stale Mentions tab behavior, then verify that new mentions appear after background polling or pull-to-refresh without visiting the official web client.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- kotlin
- Domain
- mobile
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 52/100