No notifications on a multiple server configuration, at the 2nd account configured on the Talk app

[migulen]

Scenario:

Server_A and Server_B are two differents servers (VM) with a Nextcloud instance installed each. That servers share the same external public IP because they are behind an apache reverse proxy that routes every http/https connection. Each server (server_A and server_B) have different internal hostname and IP.

I don't think the problem it's in the Scenario, because at older Nextcloud Talk android app client versions the notifications worked. Not always, but normally, worked.

Steps to reproduce

Fresh intallation of android Talk app client.

1.1 - Configure account_A of server_A on Talk app.
1.2 - Send a message from other user of server_A to account_A of server_A.
1.3 -The message arrive to account_A and I receive a notification.

2.1 - Configure account_B of server_B on Talk app.
2.2 - Send a message from other user of server_B to account_B of server_B.
2.3 - The message arrive to account_B but I DON'T receive a notification.

Expected behaviour

Fresh intallation of android Talk app client.

1.1 - Configure account_A of server_A on Talk app.
1.2 - Send a message from other user of server_A to account_A of server_A.
1.3 -The message arrive to account_A and I receive a notification.

2.1 - Configure account_B of server_B on Talk app.
2.2 - Send a message from other user of server_B to account_B of server_B.
2.3 - The message arrive to account_B and I receive a notification.

Actual behaviour

The second account configured don't receive notifications.

If I delete the account_A of server_A, being after that the account_B of server_B, the unique account configured, then the account_B of server_B starts to receive correctly notifications.

If after that, I reconfigure account_A of server_A, being this the last configured account, this account don't receive notifications.

Device brand and model

S24

Android version

14

Nextcloud Talk app version

18.x.x and 18.1.0-RC2

Nextcloud server version

25.0.12

Talk version

15.0.8

Custom Signaling server configured

None

Custom TURN server configured

Yes

Custom STUN server configured

Yes

Android logs

No response

Server log

No response

Additional information

No response

[migulen]

I've more info about this bug. It only happens with my account on the 2nd server. The account username is exactly the same on the 1st server and 2nd server where I don't get notifications.

If I configure an account with different "username" on the 2nd server, I receive notifications correctly, so the problem it's a missunderstod with the username. I don't know if it's problem from "nextcloud talk android client", "nextcloud spreed server" or "FCM (Firebase cloud messaging) from google".

I'm going to test the "not working configuration" with an Nextcloud Talk IOS client to see if the problem is from "nextcloud talk android client".

@mahibi , it is possible this helps to find the problem ?

[migulen]

@mahibi... can you give me a hint where to look for how Talk client handle the "notifications" when the "account username" is the same on two accounts on two different nextcloud servers ? And more difficult, two virtualized nextcloud servers behind a http proxy, with same proxy external IP but different hostname/url ?

Could be on some of this files:

talk-android/app/src/main/java/com/nextcloud/talk/models/json/notifications/Notification.kt

Line 8 in 9a3702d

package com.nextcloud.talk.models.json.notifications

talk-android/app/src/main/java/com/nextcloud/talk/adapters/ParticipantDisplayItem.java

Line 26 in 9a3702d

* Shared handler to receive change notifications from the model on the main thread.

talk-android/app/src/main/java/com/nextcloud/talk/jobs/NotificationWorker.kt

Line 57 in 9a3702d

import com.nextcloud.talk.models.json.notifications.NotificationOverall

talk-android/app/src/main/java/com/nextcloud/talk/utils/NotificationUtils.kt

Line 258 in 9a3702d

val notifications = notificationManager.activeNotifications

I've the impression that Talk client is handling the notifications directed to the 2on account (on the 2on server), how if they were sent to the first account, (on the 1st server ) and for some reason they are "discarded" silently...

[mahibi]

I will have a closer look and come back with more questions or hopefully a solution

[migulen]

@mahibi ,

On my case I'm trying to isolate if the problem of the notifications only comes because I've the same user login on the two servers, and if them are not relayed because the Nextcloud Talk App can't manage itself, or because FCG (Firebase Cloud Messaging) it's not informing correctly to the Nextcloud Talk App.

I can confirm that with Android based mobiles that support "duplicated apps" (like Xiaomi are) I'm able to configure the 2 accounts on the "duplicate Nextcloud Talk app", with the same username , but diferent Nextcloud server, and both receive the notificacions correctly. So I think that Nextcloud Talk App isn't able to manage this situation, but I'm not 100% sure.

By other way, when you share a file (like an image) from other app (like firefox) to Nextcloud Talk App, it's impossible to "switch the user account if you have 2 (or more) accounts configured", it always shows the last checked account.

The version of Nextcloud Talk Android App is: v20.0.1
The version of Nextcloud Server is: v28.0.10
The version of Nextcloud Talk/Spreed (Server side): v18.0.11

I hope it helps.

NOTE: Samsung Android mobiles don't have the "Duplicate Apps" like Xiaomi have, so it's more important for the first mobiles, the second one, you can do a little workaround for 2 accounts, but not for more.

#4039