signalapp / signalapp/Signal-Android
Message notification delay, might expect a checking messages notification
Nobody has claimed this yet.
- Dominant language
- Kotlin
- Stars
- 29.4k
- Forks
- 6.9k
- PR merge metrics
- No merged PRs in 30d
Description
Guidelines
- I have searched searched open and closed issues for duplicates
- I am submitting a bug report for existing functionality that does not work as intended
- This isn't a feature request or a discussion topic
Bug description
Received a notification while there was a message send > 1hr before and one > 30m before. Looking through the logfile it seems there was an FCM notification around the original timestamp of the message. To me it seems Signal might not have network access at that time (don't know why because background access is allowed) but shouldn't this result in a "checking messages" notification to get the app in the foreground?
In the attached log the 2 messages are:
1750352347824
1750354394306
For both timestamps there was an FCM notification but I guess it didn't try to fetch the message due to a network restriction. The messages were finally fetched at 8:19 pm.
Screenshots
No response
Device
Pixel 7
Android version
15
Signal version
7.46.0
Link to debug log
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
No source file or test is named. Start with the linked Android debug log and trace the FCM notification handling around timestamps 1750352347824 and 1750354394306, including the delayed fetch at 8:19 pm. Done should establish whether a missed fetch reliably produces the expected checking-messages notification and document or verify the resulting behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- android, firebase, kotlin
- Domain
- mobile-dev
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100