Dimillian / Dimillian/IceCubesApp

Bug: Only very rarely see notification count badges on the bottom buttons?

Open
#1,197 0 comments 3 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

bug
Dominant language
Swift
Stars
7.1k
Forks
720
PR merge metrics
No merged PRs in 30d

Description

Environment:

  • OS: 16.3.1
  • IceCubesApp version: 1.6.3

Description

Once in a rare while I see a bright red notification count badge on the bottom messages or notifications buttons, but usually not. Just now I had both replies and stars waiting with no hint of their existence.

Does scrolling past a DM in my timeline clear the notification for it? But shouldn't the badge show up when it is loaded, before I scroll to it?

Does viewing a notification for a DM un-notify the message version of it?

Does switching instances clear notifications about the previous instance?

Is there some other way I could be mostly hiding them?

Related Issues

  • Search that this bugs don't already exist before creating it.

Contributor guide

No contributing guide indexed for this repository

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.

Research direction

No source files, tests, or entry points are named. Start by reproducing the missing bottom-button badges using the reported iOS 16.3.1 and IceCubesApp 1.6.3 scenarios, including replies, stars, direct messages, scrolling, and instance switching. Done means the notification count behavior is understood and consistently reflects pending notifications.

Written by the indexing model from the issue text.

Assessment

Tech stack
ios, swift
Domain
mobile
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.