1030811 - CallScreen app debugging not working

Status: RESOLVED WONTFIX

(DevTools Graveyard :: WebIDE, defect)

Description

[Germán Toro del Valle (:gtorodelvalle)]

Hi guys,

First off, awesome work regarding this WebIDE thing :p

I was trying to debug the CallScreen app using the WebIDE and it seems that it does not work as expected. To start with, the CallScreen app is started when a (2.0) Firefox OS device is started (just like the system one) but the WebIDE does not detect it as running (or it seems so). For example the "pause"/"debugging" button is not active. In fact, if I select it from the list it tries to start it but it seems to fail. From this point on, the "pause"/"debugging" button becomes active and I can click it to get the Dev Tools. Anyhow, the element selection functionality and live editing do not work. It seems the WebIDE "is connected" to a "different instance" of the CallScreen app.

I tried it also using the App Manager and everything works as expected. The App Manager detects the CallScreen app as running and offers the "Debug" button. After clicking on it and opening the Dev Tools, the element selection, live editing, etc., works as expected.

All this testing was using 2014-06-24's Nightly build.

Thanks!

Comment 1

[Germán Toro del Valle (:gtorodelvalle)]

Some corrections:
  1. If no call is going on, each time I select the "CallScreen" app from the list, the WebIDE tries to start it (although already running) and it seems to fail to do it. The "pause"/"debugging" is enabled during the starting up but get backs to disabled once the starting fails.
  2. If a call is ongoing, the behavior mentioned in the description takes place, this is: if I select the CallScreen app from the list it tries to start it but it seems to fail. From this point on, the "pause"/"debugging" button becomes active and I can click it to get the Dev Tools. Anyhow, the element selection functionality and live editing do not work. It seems the WebIDE "is connected" to a "different instance" of the CallScreen app. Kind of weird ;)

Comment 2

[Paul Rouget [:paul]]

I think I ran into the same issue with the homescreen at some point. I'll look at this.

Comment 3

[Germán Toro del Valle (:gtorodelvalle)]

Nice, thanks! BTW, I just tested it using todays's Nightly build (2014-06-26) and it reproduces.

Comment 4

[Paul Rouget [:paul]]

Germán, is it still happening to you? I can't reproduce with the homescreen anymore.
I tried with a 2.1 device though. Might be a 2.0 specific issue.

Comment 5

[Germán Toro del Valle (:gtorodelvalle)]

Hi Paul, sadly I am still observing some weird behaviour using today's build (Gecko-10853dd.Gaia-c6a6ac5, this is 2.1):
1. After flashing the build to the device and going through the FTU, connect the WebIDE to the device.
2. Select the CallScreen app. The "Debug" button is properly enabled and the the "Install and run" is not, which is also correct.
3. Click on the "Debug" button. In the device it seems it tries to start the app which is already running. After some time an "Operation timed out: opening toolbox" error is shown in the WebIDE.
4. Click on the "Debug" button again. Everything seems to work as expected and it is possible to debug the app normally and even select elements via tapping on the device screen.
5. BTW, I also observed that if I click on the "Debug" button to close the Dev Tools and click on it again to reopen them, although I can see how the elements change in the inspector and I can change CSS values, the selection of elements via tapping on the device screen no longer works :(

Hope that helps! ;) If you need further testing, please do not hesitate to ask :)

Comment 6

[Paul Rouget [:paul]]

So how does the callscreen app work? Does it have entry points? What is the window that the inspector shows?

I don't get the timeout here. Beside the FTU, I do what you say, and it appears to work for me. But I can't "stop" the callscreen for some reason (clicking the stop button does nothing). About step "3", I get something similar (trying to start the app), but at step 2.

Can you check if your STRs are still valid on your side?

Comment 7

[Anthony Ricaud (:rik)]

The Callscreen app is a dedicated app (apps/callscreen/manifest.webapp) but launched in the system process.
See https://github.com/mozilla-b2g/gaia/blob/0918e40d19e2bc1e8cc6be70f864aca64dbe3b3d/apps/system/js/dialer_agent.js and https://github.com/mozilla-b2g/gaia/blob/0918e40d19e2bc1e8cc6be70f864aca64dbe3b3d/apps/system/js/attention_screen.js.

The callscreen app is restarted after each call session. When we close the attention screen, we empty the iframe (line 249) before reloading.

Comment 8

[J. Ryan Stinnett [:jryans] (Use needinfo, replies may be slow)]

Filter on TEAPOT-SPLINES.

Given FxOS announcements, it seems unlikely we'll make an app-specific fix at this time.