You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
Recipient is one user (M) having a public username (eg. Mpublic), the second recipient (K) doesn't have a public username.
See **Expected behavior": I expected to be able to mix username and firstname (when no username exists).
To Reproduce 'Store username not firstname' active.
Send message to "Mpublic; K"
But when "store username" is active, only Mpublic gets the message. When "store username" is deactivated, only K gets the message.
So I expected to be able to mix username and firstname, since I use the username for M with Mpublic and K as firstname (no username existent). When "store username" is active, both Mpublic and K should get the message.
Versions:
Adapter version: v3.9.0
JS-Controller version: 6.0.9
Node version: v20.17.0
The text was updated successfully, but these errors were encountered:
Describe the bug
Recipient is one user (M) having a public username (eg. Mpublic), the second recipient (K) doesn't have a public username.
See **Expected behavior": I expected to be able to mix username and firstname (when no username exists).
To Reproduce
'Store username not firstname' active.
Send message to "Mpublic; K"
But when "store username" is active, only Mpublic gets the message. When "store username" is deactivated, only K gets the message.
Expected behavior
So I expected to be able to mix username and firstname, since I use the username for M with Mpublic and K as firstname (no username existent). When "store username" is active, both Mpublic and K should get the message.
Versions:
The text was updated successfully, but these errors were encountered: