Closed
Bug 965047
Opened 11 years ago
Closed 11 years ago
Cannot debug Browser app with App Manager
Categories
(DevTools Graveyard :: WebIDE, defect)
Tracking
(Not tracked)
RESOLVED
DUPLICATE
of bug 958002
People
(Reporter: botond, Unassigned)
Details
This used to work earlier today (in fact I was successfully debugging the Browser app when I ran into and filed bug 965000). I'm really not sure what changed. If others can't reproduce it, I would be grateful for some ideas on how I could diagnose the issue.
STR:
1. Connect App Manager to a B2G device that has the pref for
debugging certified apps enabled.
2. Start the Browser app (either from the phone or from App Manager).
3. Press 'Debug' on the Browser app's entry under "Installed Apps".
Expected:
A new tab (under "Apps" and "Device") appears for the Browser app and
the developer tools are shown for that tab.
Actual:
The "Device" tab is de-selected, but no new tab appears. The main
view of App Manager is empty.
We talked about this briefly on IRC. It also works fine for the 1.3 simulator, so I'm suspecting recent change in Gaia master, but maybe we'd need to get a regression window to figure it out since there weren't any log messages to go on.
Botond, did you have local Gaia changes applied when you saw this, or should I be able to replicate with a fresh Gaia clone?
Flags: needinfo?(botond)
| Reporter | ||
Comment 2•11 years ago
|
||
(In reply to J. Ryan Stinnett [:jryans] from comment #1)
> Botond, did you have local Gaia changes applied when you saw this, or should
> I be able to replicate with a fresh Gaia clone?
I didn't have local Gaia changes.
Flags: needinfo?(botond)
| Reporter | ||
Comment 3•11 years ago
|
||
Just tried with App Manager running in a newer Nightly (Jan 24 vs. Jan 08) and now it is working again. Maybe that was the problem?
Updated•11 years ago
|
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → DUPLICATE
Updated•7 years ago
|
Product: Firefox → DevTools
Updated•5 years ago
|
Product: DevTools → DevTools Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•