New issue
Advanced search Search tips

Issue 752517 link

Starred by 1 user

Issue metadata

Status: WontFix
Owner: ----
Closed: Apr 2018
Components:
EstimatedDays: ----
NextAction: ----
OS: Android
Pri: 3
Type: Task



Sign in to add a comment

Add WebView Support Library version to crash reports

Project Member Reported by gsennton@chromium.org, Aug 4 2017

Issue description

When we have implemented the WebView Support library we should ensure we report the current version used in micro- and minidumps.

Note that an app could use several different versions of the support library at the same time (from the same process), we should take this into account when fetching the support library version locally.
 
I'm not against this in general, but I'm not certain what cases we would need it in. The App version and the GMSCore version are collected currently, but I'm not aware of any stand-out case where we've used it in resolving a bug.

As you point out, there could be multiple versions of the support library to capture; will we be able to attribute a stack trace to one or the other (or the framework)? That seems hard, especially for native crashes.
Labels: -Type-Bug Type-Task
Status: WontFix (was: Available)
Yeah, I'm not sure this would be helpful.. I'm gonna close this for now - if we feel the need to add this in the future we can do so then.

Sign in to add a comment