New issue
Advanced search Search tips

Issue 638901 link

Starred by 1 user

Issue metadata

Status: Fixed
Owner:
Closed: Aug 2016
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 3
Type: Bug



Sign in to add a comment

Starting the sandboxed renderer with WebView as the provider fails

Project Member Reported by tobiasjs@chromium.org, Aug 18 2016

Issue description

Version: master

Caused because of a missing proguard rule for webview:

08-17 13:51:30.297  5234  5234 E AndroidRuntime: android.os.BadParcelableException: Parcelable protocol requires a Parcelable.Creator object called CREATOR on class org.chromium.content.browser.FileDescriptorInfo

 
Project Member

Comment 1 by bugdroid1@chromium.org, Aug 18 2016

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/e339d7ccee8a30818ed8d7c511ca0df01b8342c3

commit e339d7ccee8a30818ed8d7c511ca0df01b8342c3
Author: tobiasjs <tobiasjs@chromium.org>
Date: Thu Aug 18 22:02:07 2016

Don't let proguard rename the CREATOR static of any Parcelable

Currently Clank's proguard config does this, but WebView also
needs it. The most expedient solution appears to be to move the
declaration to the base proguard config.

BUG= 638901 

Review-Url: https://codereview.chromium.org/2251213003
Cr-Commit-Position: refs/heads/master@{#412948}

[modify] https://crrev.com/e339d7ccee8a30818ed8d7c511ca0df01b8342c3/base/android/base_proguard_config.flags
[modify] https://crrev.com/e339d7ccee8a30818ed8d7c511ca0df01b8342c3/chrome/android/java/proguard.flags

Status: Fixed (was: Started)

Sign in to add a comment