Closed
      
        Bug 1090306
      
      
        Opened 11 years ago
          Closed 11 years ago
      
        
    
  
[Loop] Loop remains blocked in screen "Opps! That didn't work....", calling from call log entry  previously generated by an URL-browser call.  
    Categories
(Firefox OS Graveyard :: Gaia::Loop, defect)
Tracking
(Not tracked)
        VERIFIED
        FIXED
        
    
  
People
(Reporter: javier.deprado, Assigned: jaoo)
References
Details
(Whiteboard: [mobile app][blocking][tef-triage][loop in v1.1])
Attachments
(3 files)
ENV:
Flame-A: user.v2.0.184based.B-49.Gecko-675d616.Gaia-2183b4f
Flame-B: eng.v2.0.184based.B-43.Gecko-675d616.Gaia-2183b4f
RAM: 5132M
Loop Version 1.1: ofbfc03
STR:
1.- Generate an URL from device-B to device-A, and send it by email
2.- Open mail from device-A, and click on link included. -> Browser in device-A is opened.
3.- Push in start loop call in the Browser, and Loop app is opened, and establish the call with device-B
4.- Hang up the call from device-B and call log entry in both devices is generated.
5.- From call log in device-A, (see attachment(1)), make (repeat) the same call. (long tapping and selecting "Call"m or tapping directly on the entry).
ACTUAL RESULT: Loop remains blocked in screen "Opps! that didn't work..." (see Attachment(2)), and It's necessary to reset the device.
| Reporter | ||
          Updated•11 years ago
           
         | 
      
Severity: normal → blocker
| Reporter | ||
          Updated•11 years ago
           
         | 
      
| Reporter | ||
          Comment 1•11 years ago
           
         | 
      ||
| Reporter | ||
          Comment 2•11 years ago
           
         | 
      ||
          Updated•11 years ago
           
         | 
      
          Updated•11 years ago
           
         | 
      
Whiteboard: [mobile app][blocking][tef-triage]
| Assignee | ||
          Comment 3•11 years ago
           
         | 
      ||
I'm seeing this:
E/GeckoConsole(19623): Content JS ERROR at app://loop.services.mozilla.com/js/helpers/call_screen_manager.js:369 in _launchAttention/</onLoaded/</onFallback/<: Unable to retrieve link to share Error: Invalid peer id
| Assignee | ||
          Comment 4•11 years ago
           
         | 
      ||
There you got the bits we need to close the call screen after showing the error.
| Assignee | ||
          Updated•11 years ago
           
         | 
      
Assignee: nobody → josea.olivera
          Comment 5•11 years ago
           
         | 
      ||
Jose Antonio, please, uplift the patch after landing in master
Whiteboard: [mobile app][blocking][tef-triage] → [mobile app][blocking][tef-triage][loop approved for 1.1]
| Assignee | ||
          Updated•11 years ago
           
         | 
      
        Attachment #8512955 -
        Flags: review?(crdlc)
          Comment 6•11 years ago
           
         | 
      ||
Comment on attachment 8512955 [details] [review]
Pointer to Github PR https://github.com/mozilla-b2g/firefoxos-loop-client/pull/258
Perfect as always, 10x
        Attachment #8512955 -
        Flags: review?(crdlc) → review+
| Assignee | ||
          Comment 7•11 years ago
           
         | 
      ||
Landed on master branch at:
https://github.com/mozilla-b2g/firefoxos-loop-client/commit/6f38b74936769c757174649e79e50c3cf26fe34b
Landed on 1.1 branch at:
https://github.com/mozilla-b2g/firefoxos-loop-client/commit/e01ef767f8099e324ac19fc66669fa48f9727b27
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
| Assignee | ||
          Updated•11 years ago
           
         | 
      
Whiteboard: [mobile app][blocking][tef-triage][loop approved for 1.1] → [mobile app][blocking][tef-triage][loop in v1.1]
| Reporter | ||
          Comment 8•11 years ago
           
         | 
      ||
Pending to be verified on production environment. (5th November)
| Reporter | ||
          Comment 9•10 years ago
           
         | 
      ||
Verified on Flame & FireE, loop version 1.1: 2e7c3c2
Status: RESOLVED → VERIFIED
          You need to log in
          before you can comment on or make changes to this bug.
        
Description
•