[Bug]: Android project filter omits recognized project favicons

Open Beginner friendly
#7,981 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
72/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Active
Tech stack
android, typescript
Domain
mobile

Research direction

Start in apps/mobile at the Android custom project filter, then compare its project rows with the existing mobile thread list and desktop behavior described in the issue. The fix is complete when each recognized project favicon appears in the filter while the selected check remains visible.

Written by the indexing model from the issue text.

Description

Before submitting
  • I searched existing issues and did not find a duplicate.
  • I included enough detail to reproduce or investigate the problem.
Area

apps/mobile

Steps to reproduce
  1. Connect the Android app to an environment with two or more projects that have recognized favicons.
  2. Open Home.
  3. Open the project filter from the Home header or persistent sidebar.
  4. Compare the project rows with the same projects on desktop or in the mobile thread list.
Expected behavior

Each project row should show the favicon T3 already resolved for that project, matching desktop and existing mobile project rows. The selected check should remain visible.

Actual behavior

Android's custom project filter shows only project labels. The recognized project favicon is absent, so visually distinct projects become a text-only list.

Impact

Cosmetic issue

Version or commit

main @ 2433f4c1c

Environment

Android mobile app, 1080 x 1920, dark mode

Logs or stack traces
No logs. UI-only issue.
Screenshots, recordings, or supporting files
Before Expected behavior
Android project filter without favicons Android project filter with recognized favicons
Workaround

No in-menu workaround. Projects can only be identified by name in this filter.

Dominant language
TypeScript
Stars
23.2k
Forks
5.9k
Avg merge
10h 57m
Merged PRs (30d)
365

Contributor guide

Open the contributing guide

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 pingdotgg/t3code

All issues in pingdotgg/t3code

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.