Signal domains and delayed messaging

Open
#14,282 11 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
38/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Active
Tech stack
android, kotlin
Domain
mobile-dev, networking

Research direction

No source files, tests, or entry points are mentioned. Start by reproducing delayed delivery while switching between Wi‑Fi and LTE on GrapheneOS, then compare behavior with the listed Pi-hole domains allowlisted. Done means identifying whether DNS or a missing dependency causes the delay and documenting the confirmed required domains.

Written by the indexing model from the issue text.

Description

acknowledged
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

Still impacted by Issue 14172 and 14180 while keeping both sides of the conversation on recent to most recent pre-release.

I do believe the issue stems from switching between wifi and LTE. Messages are received when the app is opened but are pending for tens of minutes or more until the app is opened... I think it's gone longer than an hour... A text to prompt opening signal is the work around...

I do have pihole running and am using GrapheneOS. I found a allowlist for pihole that includes a signal section... Could DNS somehow a contributing factor? Or not having some Google dependency? We didn't have this problem many months ago....

https://discourse.pi-hole.net/t/commonly-whitelisted-domains/212

Are all these domains needed by Signal? Any others? I'd only want to allow list confirmed domains and we can see if that resolves the issue?

pihole allow ud-chat.signal.org
pihole allow chat.signal.org
pihole allow storage.signal.org
pihole allow signal.org
pihole allow www.signal.org
pihole allow updates2.signal.org
pihole allow textsecure-service-whispersystems.org
pihole allow giphy-proxy-production.whispersystems.org
pihole allow cdn.signal.org
pihole allow whispersystems-textsecure-attachments.s3-accelerate.amazonaws.com
pihole allow d83eunklitikj.cloudfront.net
pihole allow souqcdn.com
pihole allow cms.souqcdn.com
pihole allow api.directory.signal.org
pihole allow contentproxy.signal.org
pihole allow turn1.whispersystems.org

Sorry for letting the previous bug reports go stale.

Dominant language
Kotlin
Stars
29.4k
Forks
6.9k
No merged PRs in 30d

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 signalapp/Signal-Android

All issues in signalapp/Signal-Android

Similar issues

More Kotlin issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.