Switch Account management bugs on V16.1.0.41

[AWS2P]

Hi,
i'm using V16.1.0.41 on huawei mate 10 Pro [BLA-L29] Android 9
have encountered several times app stay stuck related to management accounts

On my phone i've almost 10 differents accounts coming each from differents pbx, first case encountered, on account switch App doesn't change anything and stay stuck with account used , nothing else than rebooting the phone works to be able to switch account properly.

Today account swicth seems to work but in fact on right top corner square stay grey and App displays invalid password (of course nothing has been changed on password)
logged in 3CX console, have done scan QR code to refresh settings with no effect.

trying to switch from one to another account produce always this same behaviour with grey square on connection and invalid password displayed on all accounts tried.

 

[AWS2P]

@YiannisH_3CX , Hello is this behaviour something known ?

 

[nb]

Yes you are correct.
If you have 10 profiles to 10 pbx's and you stay moving them hundred times a day, google server might block you. Because your PHONE is constantly asking firbase to unsubscribe from one pbx, and subscribe to the next. this is one of the reasons why people complain that they do not receive push.

Re the issue you have with the password failure - that is a bug - basically it is an authentication issue that mistakenly uses "wrong password" notation but in reality it is related to FQDN and Aliases. This is fixed in the beta that there is right now online. So if you subscribe to the beta you will get the fix.

The app is not like whats app - where you have push from 1 central whats app server ( I mean not one specifically because there are many that are load balancing) but whats app is 1 to many. (1 server :: many users. 3cx needs push to be sent from MANY to MANY. (1 fire base account / push mechanism for EACH PBX in the word : The users in that pbx.

If you stay switching between accounts, you can imagine the events that will get fired by google seeing that you are subscribing to be pushed from push accounts dispersed nation wide.

I see a problem with people providing support to their customers. I actually experience this myself. I ask for a welcome email from different people 20 times a day. Imagine attempt 1 I subscribe to a pbx where the admin set a firebase account in Nevada, and the same phone 1 hour later subscribes to a pbx where the admin set a firebase account in Germany. That action triggers a heuristic in Android and Firebase internals.

A bit long but I wanted to explain what happens when we have multiple accounts on a phone.

A Note for people that have customers to support: I believe you need to have a dummy old work testing android phone and not do this on the phone you use for your work / personal. Because if you do this action, then you might break the trust to receive push for your work calls. Get an android, and reserve it for troubleshooting.

In the meantime we are studying more - because we keep a push subscription (actually we tell Firebase to keep the subscription) active for 7 days. The correct solution is to distinguish between a test push (a connection you need for a test only) and a production push (a connection you need all the time for work). So this is the dilemma.

If the 10 accounts you have are related to 1 enterprise, you should implement bridges between pbx's.
If the 10 accounts are not related to 1 enterprise, example you are a support guy or a partner, then its a problem. Look at it like this - every time you launch a profile, you are stealing the subscription you had before.

 

[nb]

S7 is a great phone to use for tests.
If you want a trick, another good way to "clear" the confusion at firebase level is to do this.
Say you go to a customer that has a problem.
1.Long press on accounts
2.Deactivate current existing account.
3.Then open QR Provision.
4.Exit app once. (at this point you just told push service that app is not in foreground and push subscription is now live.

1. Do the work you need to do. Fix the problem, check, speak to customer, done. Customer is happy and you are about to move to your next problem or customer. BUT you wish to keep this account in your records because might be this customer calls you again tomorrow for help.
2. So in this case, before you leave, or exit the app, long press on the account and deactivate it. Point I want to make - do not provision another account on top of an active one. Make it a habit to support the customer, and if you want to keep the account, long press and deactivate it.