nextcloud / nextcloud/talk-android
No push notifications on Talk app
Nobody has claimed this yet.
- Dominant language
- Kotlin
- Stars
- 739
- Forks
- 321
- Avg merge
- 14h 59m
- Merged PRs (30d)
- 151
Description
Steps to reproduce
- Sign in
- Endless loading screen (only stoppable when force stop app)
- After force stop, all chats are there; able to write and recieve messages
- Turn on all needed settings for push notifications without success
Expected behaviour
Push notifications when receiving messages
Actual behaviour
No notifications at all
Device brand and model
samsung SM-S918B
Android version
34
Nextcloud Talk app version
19.0.1
Nextcloud server version
29.0.6
Talk version
19.0.8
Custom Signaling server configured
None
Custom TURN server configured
None
Custom STUN server configured
None
Android logs
Meta information
Generation of system report
13 Sept 2024 13:25:27
Phone
Device
samsung SM-S918B
Android version
34
Google Play services
Google Play services are available
App
App name
Nextcloud Talk
App version
v19.0.1
Build flavor
gplay
Battery settings
Battery optimization is ignored, all fine
Notification permissions
Notifications are granted
Calls notification channel enabled?
Yes
Messages notification channel enabled?
Yes
Firebase push token
No firebase push token set. Please create a bug report.
Latest firebase push token generation
Unknown
Latest firebase push token fetch
Unknown
Registered users
1
Current account
Server
https://nc.iqo.uni-hannover.de
User
Kevin Rempel (kevin.rempel@stud.uni-hannover.de)
User status enabled?
Yes
Server notification app installed?
Yes
Latest push registration at server
Not yet registered at server
Latest push registration at push proxy
Not yet registered at push proxy
Server version
29.0.6
Server Talk version
19.0.8
Signaling Mode
External
Server log
No response
Additional information
No response
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 reproducing the sign-in and force-stop sequence on the reported Android configuration, then inspect the system report fields for the Firebase push token and server registration status. Done means the account registers successfully for push notifications and receiving a message produces a notification.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- android, firebase, kotlin
- Domain
- mobile
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100