Closed
Bug 1082517
Opened 10 years ago
Closed 10 years ago
[Loop] Can't make outgoing calls on 2.1 or later
Categories
(Firefox OS Graveyard :: Gaia::Loop, defect)
Tracking
(blocking-b2g:2.1+, b2g-v2.1 fixed, b2g-v2.2 verified)
People
(Reporter: ferjm, Assigned: amac)
References
Details
(Keywords: regression, Whiteboard: [mobile app][Loop not in v1.1][blocking])
Attachments
(1 file)
Bug 1069500 fixed incoming calls on 2.2 but we are still having the same issue for outgoing calls.
Reporter | ||
Comment 1•10 years ago
|
||
Reporter | ||
Updated•10 years ago
|
Blocks: Loopmov_1_1
Reporter | ||
Updated•10 years ago
|
Summary: [Loop] Can't make outgoing calls on 2.2 → [Loop] Can't make outgoing calls on 2.1 and 2.2
Reporter | ||
Updated•10 years ago
|
Summary: [Loop] Can't make outgoing calls on 2.1 and 2.2 → [Loop] Can't make outgoing calls on 2.1 or later
Comment 3•10 years ago
|
||
[Blocking Requested - why for this release]: broken functionality
blocking-b2g: --- → 2.1?
Updated•10 years ago
|
blocking-b2g: 2.1? → 2.1+
Updated•10 years ago
|
Keywords: regression
Comment 5•10 years ago
|
||
oteo, is this something that you can help find an assignee on ? Not sure if this falls on gecko folks yet given the bug is filed in gaia:loop, so will be helpful to know and we can redirect to gecko/gaia folks on our side as needed.
Flags: needinfo?(oteo)
Comment 6•10 years ago
|
||
(In reply to bhavana bajaj [:bajaj] from comment #5)
> oteo, is this something that you can help find an assignee on ? Not sure if
> this falls on gecko folks yet given the bug is filed in gaia:loop, so will
> be helpful to know and we can redirect to gecko/gaia folks on our side as
> needed.
It's a gecko/gaia issue, similar to Bug 1069500 but for outgoing calls, this one was already fixed by System team and I think they should handle this too.
Flags: needinfo?(oteo)
Comment 8•10 years ago
|
||
ferjm, I need your help for the outgoing call flow. What's different from the incoming?
Flags: needinfo?(alive) → needinfo?(ferjmoreno)
Updated•10 years ago
|
Assignee: nobody → alive
Comment 9•10 years ago
|
||
Note: I am able to make outgoing call and grant the permission successfully. (master)
Is this still reproduced?
Keywords: qawanted
Reporter | ||
Comment 10•10 years ago
|
||
I still can reproduce this issue. I uploaded a short video to [1]. As you can see the permissions dialog appears for less than a second, which makes impossible for the user to allow or deny the permission.
To reproduce it, you need to add a contact to the Contacts app and trigger a direct Loop call, from the Contacts (contacts details -> Audio or Video buttons from the Firefox Hello section) or Loop app (from the call log if you have previously done a call, like in the video at [1], or clicking in the contacts logo at the bottom of the call log which should trigger the activity to allow you to pick a contact).
[1] https://vimeo.com/110985991
Flags: needinfo?(ferjmoreno)
Comment 11•10 years ago
|
||
(In reply to Fernando Jiménez Moreno [:ferjm] from comment #10)
> I still can reproduce this issue. I uploaded a short video to [1]. As you
> can see the permissions dialog appears for less than a second, which makes
> impossible for the user to allow or deny the permission.
>
> To reproduce it, you need to add a contact to the Contacts app and trigger a
> direct Loop call, from the Contacts (contacts details -> Audio or Video
> buttons from the Firefox Hello section) or Loop app (from the call log if
> you have previously done a call, like in the video at [1], or clicking in
> the contacts logo at the bottom of the call log which should trigger the
> activity to allow you to pick a contact).
>
> [1] https://vimeo.com/110985991
I am doing the same thing, and my permission dialog does not disappear :(
Comment 12•10 years ago
|
||
Here is mine: pvt v2.1 build
https://www.youtube.com/watch?feature=youtube_gdata_player&v=DAdLrA3dujk&app=desktop
Comment 13•10 years ago
|
||
Sorry, I am not able to work on this since I cannot reproduce. qa-wanted.
Reporter | ||
Comment 14•10 years ago
|
||
As mentioned via IRC, it seems that Alive was using an old version of Loop on 2.1 while I tried the latest version on the latest 2.2 build. I can reproduce it, but he can't so maybe something changed on Loop that causes this issue.
Could any of you take a look at this, please? Thanks!
Flags: needinfo?(josea.olivera)
Flags: needinfo?(crdlc)
Flags: needinfo?(borja.bugzilla)
Comment 15•10 years ago
|
||
I was unable to reproduce this issue on 2.1 Flame KK or 2.2 Flame KK using the latest loop build available to qanalysts that works. Loop build: 2e7c3c2
Environmental Variables:
Device: Flame 2.1
BuildID: 20141106071119
Gaia: aa63911ae979ed1e3eab2ba23a6e7d6a59085854
Gecko: 780af6b71bf2
Gonk: Could not pull gonk. Did you shallow Flash?
Version: 34.0 (2.1)
Firmware Version: v188-1
User Agent: Mozilla/5.0 (Mobile; rv:34.0) Gecko/34.0 Firefox/34.0
Loop build: 2e7c3c2
Environmental Variables:
Device: Flame 2.2
BuildID: 20141106122022
Gaia: 1b974ce130eed3988ff5d012c7bd8431c4aba93b
Gecko: 678dd5860cce
Version: 36.0a1 (2.2)
Firmware Version: v188-1
User Agent: Mozilla/5.0 (Mobile; rv:36.0) Gecko/36.0 Firefox/36.0
Loop build: 2e7c3c2
QA Whiteboard: [QAnalyst-Triage?]
Flags: needinfo?(jmitchell)
Updated•10 years ago
|
Updated•10 years ago
|
Component: Gaia::Loop → Gaia::System::Window Mgmt
Comment 16•10 years ago
|
||
Per comment 15, this seems WORKSFORME?
Comment 17•10 years ago
|
||
Borja or Cristian will have a look at it. Thanks!
Flags: needinfo?(josea.olivera)
Comment 18•10 years ago
|
||
Hi, I am reproducing exactly the same bug that Fernando shows in his video in comment 10.
I am using the same Loop version than Jayme, Loop build: 2e7c3c2, and the latest 2.1 build
device:flame
KK.user.v2.1.188based
Build ID: 20141107131326
Version: 34.0 (2.1)
Gecko-7fede3f
Gaia-6295f6a
Loop build: 2e7c3c2
Comment 19•10 years ago
|
||
Tried again but no luck. I am going to drop this bug and switch component back to loop.
Assignee: alive → nobody
Component: Gaia::System::Window Mgmt → Gaia::Loop
Comment 20•10 years ago
|
||
(In reply to Alive Kuo [:alive][NEEDINFO!] from comment #19)
> Tried again but no luck. I am going to drop this bug and switch component
> back to loop.
I think that more people is reproducing it, see bug 1095221
Updated•10 years ago
|
Comment 21•10 years ago
|
||
Yes, I believe this was the same issue I was seeing for bug 1095221
I was running loop Version: 2e7c3c2
in these devices:
Flame 2.1(319mb)(KitKat)(Shallow Flash)
Environmental Variables:
Device: Flame 2.1
BuildID: 20141106001204
Gaia: 9658b93b412bdcc0f953d668e8c8e68318c99fb8
Gecko: 76880403db44
Version: 34.0 (2.1)
Firmware: V188-1
User Agent: Mozilla/5.0 (Mobile; rv:34.0) Gecko/34.0 Firefox/34.0
Flame 2.2(319mb)(Kitkat Base)(Shallow Flash)
Device: Flame 2.2 Master
BuildID: 20141105160209
Gaia: 7918024c737c4570cacd784f267e28737ae05dea
Gecko: 2114ef80f6ae
Gonk:
Version: 36.0a1 (2.2 Master)
Firmware: V188-1
User Agent: Mozilla/5.0 (Mobile; rv:36.0) Gecko/36.0 Firefox/36.0
I could not get the issue to repro on Flame 2.0, though
Flame 2.0(319mb)(Kitkat Base)(Shallow Flash)
Device: Flame 2.0
BuildID: 20141105183012
Gaia: 5ee26701a4d8db266bfb203b2179f686ce14d8b6
Gecko: dbf49343e889
Version: 32.0 (2.0)
Firmware: V188-1
User Agent: Mozilla/5.0 (Mobile; rv:32.0) Gecko/32.0 Firefox/32.0
Assignee | ||
Updated•10 years ago
|
Assignee: nobody → amac.bug
Assignee | ||
Comment 23•10 years ago
|
||
This fixes the problem in 2.1 (which was introduced by fixing bug 1050423) removing ensureGUM. Since we're again asking for a gUM to show the local video, and when we reject that we show the correct error, it isn't needed. And besides it doesn't work.
Flags: needinfo?(crdlc)
Flags: needinfo?(borja.bugzilla)
Attachment #8522309 -
Flags: review?(borja.bugzilla)
Updated•10 years ago
|
Attachment #8522309 -
Flags: review?(borja.bugzilla) → review+
Updated•10 years ago
|
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
Updated•10 years ago
|
Whiteboard: [mobile app][Loop not in v1.1][blocking]
Comment 24•10 years ago
|
||
This issue still reproduces on Flame 2.1 and 2.2.
Result: The App Permission dialog disappears immediately, and the user cannot make an outgoing call.
Device: Flame 2.1 (319mb, KK, Shallow Flash)
Build ID: 20141119001205
Gaia: 1b231b87aad384842dfc79614b2a9ca68a4b4ff3
Gecko: 95fbd7635152
Version: 34.0 (2.1)
Firmware Version: v188-1
User Agent: Mozilla/5.0 (Mobile; rv:34.0) Gecko/34.0 Firefox/34.0
Device: Flame 2.2 (319mb, KK, Shallow Flash)
BuildID: 20141119040205
Gaia: e64428c5b2dce5db90b75a5055077a04f4bd4819
Gecko: bc2c36dda0a9
Version: 36.0a1 (2.2)
Firmware Version: v188-1
User Agent: Mozilla/5.0 (Mobile; rv:36.0) Gecko/36.0 Firefox/36.0
QA Whiteboard: [QAnalyst-Triage+] → [QAnalyst-Triage+][failed-verification]
status-b2g-v2.1:
--- → affected
status-b2g-v2.2:
--- → affected
Flags: needinfo?(ktucker)
Assignee | ||
Comment 25•10 years ago
|
||
What Loop Mobile version are you using, Yeojin? This bug didn't land anything on Gecko or Gaia, but on Loop, and so you need a recent loop version (later than last friday) to test it out.
Flags: needinfo?(ychung)
Comment 26•10 years ago
|
||
(In reply to Antonio Manuel Amaya Calvo (:amac) from comment #25)
> What Loop Mobile version are you using, Yeojin? This bug didn't land
> anything on Gecko or Gaia, but on Loop, and so you need a recent loop
> version (later than last friday) to test it out.
I used version 2e7c3c2, and installed it using App Manager on Firefox Browser on my computer. The file from the link https://github.com/mozilla-b2g/firefoxos-loop-client did not work properly when installed with the same way. Is there any other method I can install the app, and where can I get the latest version?
Thanks a lot!
Flags: needinfo?(ychung)
Comment 27•10 years ago
|
||
Please, download latest version in Loop 1.1 branch (in master branch we are developing future Loop version based on Rooms) and follow the instructions included in the readme (we are using grunt command to install the application)
https://github.com/mozilla-b2g/firefoxos-loop-client/tree/1.1
Flags: needinfo?(ychung)
Comment 28•10 years ago
|
||
(In reply to Maria Angeles Oteo (:oteo) from comment #27)
> Please, download latest version in Loop 1.1 branch (in master branch we are
> developing future Loop version based on Rooms) and follow the instructions
> included in the readme (we are using grunt command to install the
> application)
>
> https://github.com/mozilla-b2g/firefoxos-loop-client/tree/1.1
Sorry, please, try with master branch, I've just realized that the patch was not uplifted to 1.1 branch (1.1 version will be available only for 2.0 release) but follow the instructions in the readme, please.
https://github.com/mozilla-b2g/firefoxos-loop-client/
Updated•10 years ago
|
Flags: needinfo?(ktucker)
Comment 29•10 years ago
|
||
I was able to make an outgoing call with Flame 2.2, after the App Permission dialog stayed properly until the user selects an option.
Loop version: b1e1edb
Device: Flame 2.2 (319mb, KK, Shallow Flash)
BuildID: 20141119040205
Gaia: e64428c5b2dce5db90b75a5055077a04f4bd4819
Gecko: bc2c36dda0a9
Version: 36.0a1 (2.2 Master)
Firmware: V188-1
User Agent: Mozilla/5.0 (Mobile; rv:36.0) Gecko/36.0 Firefox/36.0
Status: RESOLVED → VERIFIED
QA Whiteboard: [QAnalyst-Triage+][failed-verification] → [QAnalyst-Triage?]
Flags: needinfo?(ychung) → needinfo?(ktucker)
Comment 30•10 years ago
|
||
By the way, I just noticed that the back camera is activated during the call on the device, not the front camera. Is this a known bug, or should I file a new one?
Comment 31•10 years ago
|
||
Thanks Yeojin, that's the correct behaviour, It's part of a new feature requested by Product team for next Loop Mobile Client versión where we are movíng to the "share what I see" concept.
Updated•10 years ago
|
QA Whiteboard: [QAnalyst-Triage?] → [QAnalyst-Triage+]
Flags: needinfo?(ktucker)
Comment 33•10 years ago
|
||
Does something need to land somewhere for B2G v2.1 still?
Flags: needinfo?(amac.bug)
Target Milestone: --- → 2.1 S9 (21Nov)
Comment 34•10 years ago
|
||
(In reply to Ryan VanderMeulen [:RyanVM UTC-5] from comment #33)
> Does something need to land somewhere for B2G v2.1 still?
No Ryan, the fix was already landed in the Loop mobile client. It's not necessary any patch in platform.
Flags: needinfo?(amac.bug)
You need to log in
before you can comment on or make changes to this bug.
Description
•