Closed
Bug 1320153
Opened 8 years ago
Closed 6 years ago
There is no way to see crash report id on unrooted android if Firefox is not usable itself
Categories
(Firefox for Android Graveyard :: General, defect)
Tracking
(Not tracked)
RESOLVED
INVALID
People
(Reporter: phazon, Unassigned)
References
Details
User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:53.0) Gecko/20100101 Firefox/53.0
Build ID: 20161123030208
Steps to reproduce:
Currently i have android device (without root) on which Firefox crashes constantly. Crash reports sent by i cannot file bug because firefox crashes prior me getting to about:crashes and i have no obvious way to see these id without root which is not option for that device.
Actual results:
Just crashes on any attempt to interact with browser and firefox profile is not accessible without root.
Expected results:
At least some auxiliary way to get at least that ids, like text file on SD or something accessible.
Sorry if there is such way, fast googling didnt show any.
Comment 1•8 years ago
|
||
Hello and thank you for your report.
Can you please provide information about the device and OS that you are using to reproduce the issue?
Also, I noticed that you specified that Firefox Beta 51 is the version that keeps crashing, please correct me if I'm wrong. Which Beta 51 build are you using?
Can you try with a clean profile and see if the issue is still reproducing? Go to your device settings -> Applications -> Application manager -> choose the Firefox that you are using (Firefox Beta in your case) -> Storage -> Clear Data
Flags: needinfo?(phazon)
Comment 2•8 years ago
|
||
Hi!
I want to work on this bug as my first bug. If nobody is working on it..Can I work?
Comment 3•8 years ago
|
||
The way to do this is/was to create an account with the email address matches the email you submitted with the crash report at https://crash-stats.mozilla.org
The reason I say is/was is that crash-stats login process changed about a month ago and I don't know if this is still possible. The other option is to submit with an email address and I can search on that address for crashes that are related.
Sorry for delay.
So, it seems that crashes started to appear from Firefox for Android 51 beta 3. With current beta 5 its still crashes almost instantly once i start to type in urlbar.
About device - its Dell Venue 7 tablet, quite old, with Android 4.4.2. Need to mention its Atom (x86) based device.
I used wipe option and cleaned everything, didnt help.
I will use option in comment 3 and put crash reports as soon as possible.
OS: Unspecified → Android
Hardware: Unspecified → x86
Ok, it seems that so clearing data for Firefox Beta made it crashing with little bigger delay then before, so i managed to get several crash reports
https://crash-stats.mozilla.com/report/index/b4912898-fd19-4737-9ae8-a48fc2161203
https://crash-stats.mozilla.com/report/index/22e9e03a-6619-4444-be28-d6d602161203
They both leads to https://bugzilla.mozilla.org/show_bug.cgi?id=1318667 so feel free to mark as duplicated.
Flags: needinfo?(phazon)
Ah, sorry for bugspam again, but actual problem is persists - its hard to access crash data on Android without root. Sadly, even on adb there is no access to /data even to directory listings and email-in-crashreport option from comment 3 is not obvious either.
Maybe crashreporter should allow standard android "sharing" of crash-id to other app after submitting or something like that, its would be much easier.
Updated•8 years ago
|
(In reply to miralobontiu from comment #7)
> Hi,
>
> Can you still reproduce the issue?
>
> Thanks!
Those crashes is gone long ago, but as far as i understand problem of not having obvious way to see info about crashes without root access or working firefox on android is still persists.
This probably should be new bug if someone going to work on it, so i close this one.
Status: UNCONFIRMED → RESOLVED
Closed: 6 years ago
Flags: needinfo?(phazon)
Resolution: --- → INVALID
Assignee | ||
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
•