Closed Bug 1129816 Opened 10 years ago Closed 10 years ago

[Loop] Room can't be saved When the call has the maximum length allowed in subject

Categories

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

ARM
Gonk (Firefox OS)
defect
Not set
normal

Tracking

(Not tracked)

VERIFIED FIXED

People

(Reporter: lolimartinezcr, Assigned: crdlc)

Details

(Whiteboard: [Room1.1.1_Regression2][In 1.1.1][loop approved for 1.1.1])

Attachments

(2 files)

Attached image 2015-02-05-09-17-12.png
Fire E 2.0 Loop 1.1.1/bd1a553 Prerequisites: 1. User A logged in Mobile Loop application with FxA 2. User A has contact B saved. 3. Contact B isn't logged in Mobile Loop application STRs: 1. User A clicks in "New call" button. 2. User A writes subject with maximum lenght allowed and taps on "call" button. 3. After a few seconds "Dialing", user A sees "Unavailable" status. 4. User A taps on "New room" Actual result: "Saving room failed" message is shown. See attached image. I think the problem maximum lenght allowed in calls is 124 characters in subject and in room has 100 characters allowed Expected result: Room should be saved.
Whiteboard: [Room1.1.1_Regression2]
Good catch E/GeckoConsole(18123): Content JS ERROR at app://loop.stage.mozaws.net/js/screens/create_room.js:151 in newRoom/<: {"code":400,"errno":107,"error":"roomName should be shorter than 100 characters"} So we have two solutions: 1) Same limit for calls and rooms (100 chars) 2) Limit the call subject to 100 when it is longer behind scene in the fallback scenario
Assignee: nobody → crdlc
Status: NEW → ASSIGNED
Flags: needinfo?(oteo)
I would say option 2; in case of creating the new Room in the fallback scenario, I think it makes sense limit the Room name to 100 characters.
Flags: needinfo?(oteo)
Attached file Github pull request
Attachment #8559665 - Flags: review?(borja.bugzilla)
Attachment #8559665 - Flags: review?(borja.bugzilla) → review?(josea.olivera)
Comment on attachment 8559665 [details] [review] Github pull request LGTM, r=me Clean and safe, thanks for taking care of it Cristian!
Attachment #8559665 - Flags: review?(josea.olivera) → review+
Status: ASSIGNED → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
Whiteboard: [Room1.1.1_Regression2] → [Room1.1.1_Regression2][Not in 1.1.1]
As the last Telemetry patch has already been uplifted to 1.1.1 branch, let's merge this patch to 1.1.1 branch now. Thanks a lot Cristian!!
Flags: needinfo?(crdlc)
Whiteboard: [Room1.1.1_Regression2][Not in 1.1.1] → [Room1.1.1_Regression2][Not in 1.1.1][loop approved for 1.1.1]
Whiteboard: [Room1.1.1_Regression2][Not in 1.1.1][loop approved for 1.1.1] → [Room1.1.1_Regression2][In 1.1.1][loop approved for 1.1.1]
Verified on fireE, v2.0 comercial version. Loop version 1.1.1/39a5284
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: