I can not configure the notification by settings to make it enable/disable

@jin - What are the requirements for this bug?

If I delete the cache and config folders, launch telegram and enter the number details (Account A) then the Notification number appears in the Settings (Cutegram.pushNumber == telegram.phoneNumber == number for Account A)

If I then add a 2nd account (Account B) and check the Settings for the account just added, there is no Notification button. This is because Cutegram.PushNumber is still set to Account A and telegram.phoneNumber == Account B. However, if I switch accounts to Account A and check Settings, then the notification button is present.

If I then delete Account A and check Settings for Account B the notification button is displayed. So the Cutegram.pushNumber is now set to Account B.

I've tried it with 3 accounts too and it works in the way described above. Is this the expected behaviour?

I am not pretty sure we support multi-accounts notifications of framework,
need to double check current Unity space to see if this is a feature or not.
(Jin will check there)

So for the requirements of this bug,
I agree what you investigated we have a "major" account,
and the Cutegram.pushNumber need to be assigned with.

For case "have only Account A",
there is no doubt the Cutegram.pushNumber need to be assigned to the one,
so we can trigger the notifications and get the messages with app. is in background.

For case "have Account A and B",
the major one must be Account A since it make sense to popup the "Notifications" dialog,
when user logged in the first account successfully without the support for multi-accounts notifications as current design.

For case "have Account A, B and C then logout A",
in such the case we set the Cutegram.pushNumber to Account B automatically?
I am thinking is it possible to popup the "Notifications" dialog to user for Account B,
to let users know the major one is shifted.

On the other side,
about the subject of this bug,
we met the symptom in testing the bug:
    https://bugs.launchpad.net/telegram-app/+bug/1555440
but how come it could not be seen or how we reproduce such the symptom...

So it looks like the app is behaving the way it should be, and I cannot reproduce this issue as yet. Perhaps there is a sequence of actions that have led to this symptom, but they are not so straightforward. In which case how would you like to proceed with this one?

Hello Paz,

I think so, then for now,
please leave it to me(reporter),
will try to confirm the symptom again,
and manage a way to make it reproducible.

Now it will be an "Incomplete",
at least it is not a blocker of our notification bugs hacking,
really thanks for your investigation on this.