Issue metadata
Sign in to add a comment
|
Local Crash Id is not displayed (or incorrect) in chrome://crashes |
||||||||||||||||||||
Issue descriptionApp Version: 60.0.3112.38 beta iOS Version: 10.3, 11 Device: iPhone, iPad URL: chrome://crashes Steps to reproduce: 1. Launch Google Chrome 2. Navigate to about://inducebrowsercrashforrealz in a new tab to generate a crash 3. Relaunch the app and navigate to about:crashes Observed results: Observe that under the list of crashes LocalCrashId is displayed as Chrome Chrome Desktop shows a local id of the form "9a37a27f-7133-4c44-af3e-f2de63c22ede" Expected results: Either show a valid local crash id if available or hide the Local Crash Id if local id is not applicable in iOS. Number of times you were able to reproduce: 5/5 Bug reproducible after clean install: Yes Bug reproducible after clearing cache and cookies: Yes Bug reproducible on Chrome Mobile on Android: YES (Tested on Chrome Canary on Nexus5) Bug reproducible on Safari/Firefox: Firefox: NA, Safari: NA Bug reproducible on current stable build (App Version, iOS Version): M59 NO Bug reproducible on the current beta channel build (App Version, iOS Version): M60 Yes Shared Auth bugs: Bug reproducible in SSO1/SSO2 apps? NA Autofill bugs: Bug reproducible on Chrome desktop? NO Link to video/image: https://docs.google.com/drawings/d/12cC-u2mbJWLuTDV00McWUH05ieSN2ah23CfyUv6Pzgs/preview
,
Jun 21 2017
This is behaving correctly from the UI perspective because "Chrome" is being provided as the local ID. (That's why it says "Crash ID Chrome" in M59). I don't know how this is supposed to work on iOS.
,
Jun 22 2017
rsesek@/rohitrao@ does local crash id even mean anything on mobile? It's not like the user can easily access them. I wonder if we should hide this for mobile? Or perhaps I misunderstand what this is for.
,
Jun 22 2017
We probably have a unique id for non-uploaded crashes, but I don't know if it's useful to expose to users. If the "Send now" button works on mobile that would be cool, though.
,
Jun 22 2017
I don't know if there is an equivalent Local ID on mobile, but you're right that it probably doesn't make sense to display as users don't have access to the crash reports directory.
,
Jun 22 2017
Marking as WontFix since it seems like we don't want to show the Local ID on Chrome iOS. Please feel free to re-open if that's not the case. |
|||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||
Comment 1 by justincohen@chromium.org
, Jun 21 2017Labels: OS-Android
Owner: rsesek@chromium.org
Status: Assigned (was: Untriaged)