Created attachment 8472739 [details] Logcat.txt Description: If the user shares their link with another device, then clicks on the link they just sent to another user and proceed to tap the call button that follows, their own DUT will ring as if with an incoming call. Prerequisites: 1) Have Loop installed on the DUT. Repro Steps: 1) Update a Flame device to BuildID: 20140811000210 2) Launch Loop 3) Contacts > Select a contact with a phone number > Tap Firefox Hello: Video 4) On the Share link page, select messages 5) Send the message 6) After the message has sent, click the newly-sent link in the thread 7) Click 'Start the call' button Actual: The DUT rings as if in an incoming call when the user clicks the link they sent. Expected: The user is not able to call themselves from the same DUT. Environmental Variables: Device: Flame 2.0 BuildID: 20140811000210 Gaia: de28796a8956a48bb98ca67df6a33e0622d642d1 Gecko: 5256345f62bd Version: 32.0 (2.0) Firmware: V123 User Agent: Mozilla/5.0 (Mobile; rv:32.0) Gecko/32.0 Firefox/32.0 Notes: Repro frequency: 100% See attached: Video, logcat
This issue also occurs on the Flame v2.1 (319MB) and the Flame v2.0 (512MB). Device: Flame Master (319MB) Build ID: 20140813040202 Gaia: 9f35fca9d818b26c06aa6b7e5c0bef25886f8f20 Gecko: 7fc96293ada8 Version: 34.0a1 (Master) Firmware Version: v122 User Agent: Mozilla/5.0 (Mobile; rv:34.0) Gecko/34.0 Firefox/34.0 Device: Flame 2.0 (512MB) BuildID: 20140811000210 Gaia: de28796a8956a48bb98ca67df6a33e0622d642d1 Gecko: 5256345f62bd Version: 32.0 (2.0) Firmware: V123 User Agent: Mozilla/5.0 (Mobile; rv:32.0) Gecko/32.0 Firefox/32.0 The DUT rings as if with an incoming call when the user clicks the link they sent.
QA Whiteboard: [QAnalyst-Triage?]
Could you provide the Loop version (Loop Settings). Thanks
Sure thing, Loop Version: 609ec57
QA Whiteboard: [QAnalyst-Triage?] → [QAnalyst-Triage+]
QA Whiteboard: [QAnalyst-Triage+] → [QAnalyst-Triage+][lead-review+]
This should not happen once the US described in bug 1010168 is implemented and for that we need bug 1008990. Based on that I am marking this as not blocking.
Whiteboard: [2.0-exploratory] → [not blocking][2.0-exploratory]
Whiteboard: [not blocking][2.0-exploratory] → [not blocking][2.0-exploratory][tef-triage]
Issue already resolved after the implementation of the pending work, right now when the user clicks on the URL sent to another unavailable contact, the call tries to be established but it failed with "busy" error what it's the expected behavior. Resolving the bug as worksforme. Rachel, be free to reopen it if you see something wrong, thanks a lot!
Status: NEW → RESOLVED
Last Resolved: 3 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.