Closed Bug 1126750 Opened 10 years ago Closed 10 years ago

[Loop] No notification is sent to the guest user, when user is the first one in room and owner deletes the room

Categories

(Firefox OS Graveyard :: Gaia::Loop, defect)

ARM
Gonk (Firefox OS)
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED WONTFIX

People

(Reporter: lolimartinezcr, Unassigned)

Details

(Whiteboard: [Room1.1.1_TestRun2])

Fire E 2.0
Loop 1.1.1/d4d6d37

Pre-requisites
User A logged in Mobile Loop application with FxA
User B logged in Destkop Loop application.
User A has created and shared a room with contact B


STRs:
1. User B, taps on URL shared and joins to room -> Message is shown about User is the first one in room.
2. User A long-taps in the room (where user B is the first one).
3. User A taps on "delete Room" button.
4. User A taps on "Delete" button.

Actual result:
The room is deleted in rooms list in User A, and user B is joined the room. User B doesn't receive any notification about room is deleted.

Expected result:
User B should be notificated about the room has been deleted or User B shouldn't be in the room.
The expected result should be defined by UX.
Whiteboard: [Room1.1.1_TestRun2]
Summary: [Loop] No notification is sent to the guest userr, when user is the first one in room and owner deletes the room → [Loop] No notification is sent to the guest user, when user is the first one in room and owner deletes the room
Your STRs are OK but the server does not send notifications to participants, just only to owners. So if you are joining a room as a participant you are not aware of this scenario. There is not mechanism to know this situation on invited side. Of course, if you leave the room and you try to enter again, the message will be shown because when we request to the server for joining a room it'll tell us what the room is no longer available. But if you are already joining a room, bad luck :)
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.