Closed
Bug 764955
Opened 12 years ago
Closed 12 years ago
Please add information in the App notes for crashes indicating if a crash occurred from a webapp
Categories
(Firefox for Android Graveyard :: Web Apps (PWAs), defect, P2)
Tracking
(firefox16 affected, firefox17 affected, fennec-)
RESOLVED
DUPLICATE
of bug 780972
People
(Reporter: nhirata, Unassigned)
Details
(Whiteboard: [blocking-webrtandroid1-])
Web app crashes would be harder to tell within fennec without some sort of indication that it's a web app.
Will the URL also be included? I'm not sure if there would be any URL mentioned with a Web App crash in Fennec Native...
Comment 1•12 years ago
|
||
Wes or Mark - What can we do here to make sure that if a crash occurs that we know if it happened within a web app or not?
Component: General → Web Apps
QA Contact: general → web-apps
Updated•12 years ago
|
Blocks: Blocking-FFA-WebRT1+
Updated•12 years ago
|
No longer blocks: Blocking-FFA-WebRT1+
Updated•12 years ago
|
Priority: -- → P2
Updated•12 years ago
|
QA Contact: aaron.train
Updated•12 years ago
|
OS: All → Android
Hardware: All → ARM
Comment 2•12 years ago
|
||
Ping?
tracking-fennec: --- → ?
status-firefox16:
--- → affected
status-firefox17:
--- → affected
Version: Firefox 14 → Trunk
Comment 3•12 years ago
|
||
(In reply to Aaron Train [:aaronmt] from comment #2)
> Ping?
I think this problem might be solved by bug 772968. Should we dup on that bug?
Comment 4•12 years ago
|
||
If we really go down that way, probably.
Comment 5•12 years ago
|
||
Given that bug 772968 is officially landing, the problem in this bug is solved by that bug. Duping on that bug.
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → DUPLICATE
Comment 6•12 years ago
|
||
Near as I can tell, we need to pass in a serverUrl parameter during startup that will eventually get passed to the crash reporter here:
http://mxr.mozilla.org/mozilla-central/source/toolkit/xre/nsAppRunner.cpp#2957
And then passed back to java when we actually crash. I need to dig more, but I don't believe that changing the blocklist id fixes this.
Status: RESOLVED → REOPENED
Resolution: DUPLICATE → ---
Updated•12 years ago
|
tracking-fennec: ? → -
Updated•12 years ago
|
Whiteboard: [blocking-webrtandroid1-]
Comment 7•12 years ago
|
||
serverUrl is just where crashes get submitted. What application ID are we sending for web app crashes?
Comment 8•12 years ago
|
||
WebappRuntimeMobile.
We're adding that as a new product to Socorro in bug 780972, so I'm marking as a dupe of that.
Status: REOPENED → RESOLVED
Closed: 12 years ago → 12 years ago
Resolution: --- → DUPLICATE
Comment 9•12 years ago
|
||
I don't understand. So the client implementation sends enough information of to socorro to know whether the crash came from a webapp with the app ID being evident then? comment 6 says otherwise.
Comment 10•12 years ago
|
||
(In reply to Jason Smith [:jsmith] from comment #9)
> I don't understand. So the client implementation sends enough information of
> to socorro to know whether the crash came from a webapp with the app ID
> being evident then? comment 6 says otherwise.
Bug 772968 provided enough information that Socorro can tell, it's just not using that info until bug 780972 lands.
Updated•4 years ago
|
Product: Firefox for Android → Firefox for Android Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•