1131545 - [Loop][Telemetry] Different behavior in telemetry's trace between rooms with and without subject.

Status: RESOLVED WORKSFORME

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

Description

[Loli (:lolimartinezcr)]

Fire E 2.0
Loop 1.1.1/253ebde

Prerequisites:
User logged in Mobile Loop application.

STRs:
1. User has created and shared a room without subject via SMS with a contact.
2. User has deleted the room without subject via SMS. AR1
3. User has created and shared a room with subject via SMS with a contact.
4. User has deleted the room with subject. AR2

Actual result:
AR1: Telemetry trace:
"smsNotificationOnCreation":{"1":1},"smsNotificationOnCreationWithSubject":{"0":1}

AR2: Telemtry trace:
"smsNotificationOnCreation":{},"smsNotificationOnCreationWithSubject":{"0":1}

Expected result:
With or without subject,should show or {} or {"0":1} but similar traces.

Comment 1

[Loli (:lolimartinezcr)]

Also, it is reproducible in case of Email.

Comment 2

[Carmen Jimenez Cabezas]

If you create a room (with or without subject), share it (via mail or SMS) and before the report is sent you erase the room, then the report sent will have (only the case where the room is create with subject and shared via mail is shown, but in my tests all the other cases behave similarly): 

"createdWithSubject":1,"smsNotification":{},"smsNotificationWithSubject":{},"smsNotificationOnCreation":{},"smsNotificationOnCreationWithSubject":{},"emailNotification":{},"emailNotificationWithSubject":{},"emailNotificationOnCreation":{},"emailNotificationOnCreationWithSubject":{"1":1}

The {} values are there because at the report sending time there's no room.

If you create the room, share it and the report is sent before the room is erased then you'll get values of the kind:

<parametro>: {"0":1}

Because when the report is sent there's a room that hasn't generated any values for that parameter. 

What makes this report different from the previously shown one is the existence or not of a room at the report sending moment. 

For both cases, this is he expected behavior. 


Could you please supply more data about the error you're seeing?