mirror of
https://github.com/nextcloud/talk-android
synced 2025-06-21 12:39:58 +01:00
7f86593bca
When a new participant is found and the layout for that participant is set up the participant data might have not been fetched yet. If that happens the user ID can not be got from the data and therefore a guest avatar would be shown for that participant, even if that participant is a normal user. However, the signaling message that is used to find new participants already includes the user ID, so it is now explicitly given and, if not, then it is got from the participant data (which is needed when handling the establishment of a connection, as in that case the event does not contain the user ID). Signed-off-by: Daniel Calviño Sánchez <danxuliu@gmail.com> |
||
|---|---|---|
| .. | ||
| activities | ||
| adapters | ||
| api | ||
| application | ||
| arbitrarystorage | ||
| callbacks | ||
| components/filebrowser | ||
| controllers | ||
| conversation/info | ||
| dagger/modules | ||
| data | ||
| events | ||
| interfaces | ||
| jobs | ||
| messagesearch | ||
| models | ||
| polls | ||
| presenters | ||
| receivers | ||
| remotefilebrowser | ||
| repositories | ||
| shareditems | ||
| ui | ||
| upload | ||
| users | ||
| utils | ||
| webrtc | ||