Device: Flame Mobile ID: c0243a0 As per US (https://bugzilla.mozilla.org/show_bug.cgi?id=1009886), the AC says "In case the call is rejected, the other party is notified about the rejection" STR 1. Device B, open contact app 2. Make a Loop call from Device A to Device B 2. Device B reject the call ACTUAL RESULT Device A is not notified that the call was rejected EXPECTED RESULT Device A should be notified that the call was rejected
This will be also be the case if I don't answer the call during the configured answering time.
This issue still occurs on the latest 2.0 build with the v165 KK base. The call is ended abruptly without a notification when the call is rejected or not answered. Environmental Variables: Device: Flame 2.0 BuildID: 20140819030000 Gaia: 287a2c725a5c14e5dc1d48e3158ffc79c7d1ea33 Gecko: 6329352ca531b977979451e77e5862af485388b2 Version: 32.0 (2.0) Firmware Version: v165 User Agent: Mozilla/5.0 (Mobile; rv:32.0) Gecko/32.0 Firefox/32.0 Loop version: 32219a2
Assignee: nobody → josea.olivera
Created attachment 8481610 [details] [review] Pointer to Github PR https://github.com/mozilla-b2g/firefoxos-loop-client/pull/105
Attachment #8481610 - Flags: review?(borja.bugzilla)
Pending confirmation from Rafa about the string showed. "Call Declined", "Declined" or other...
Whiteboard: [mobile app][blocking] → [mobile app][blocking][patch available]
I think "Declined" is the best one; it's polite and informative, and keeping it as short as possible helps with space on localizations.
Attachment #8481610 - Flags: review?(borja.bugzilla) → review+
Thanks for your massive help on debugging this. Landed at: https://github.com/mozilla-b2g/firefoxos-loop-client/commit/15aa2b176172af234fef38a62d41efc999612956
Status: ASSIGNED → RESOLVED
Last Resolved: 4 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.