Steps to reproduce the problem:
1. Share any content from chrome to an Android app that uses ClipData.coerceToText()
2. In the Android app activity that handles the share intent, pull the first clip item from the intent passed by chrome and pass it to coerceToText()
3. Android app crashes with a nullpointerexception

What is the expected behavior?
CoerceToText() successfully returns a text representation of the clip item data passed int the intent from Chrome.

What went wrong?
The change to ChromeFileProvider that is rolling out as part of Chrome 55 (https://chromium.googlesource.com/chromium/src.git/+/lkcr/chrome/android/java/src/org/chromium/chrome/browser/util/ChromeFileProvider.java) breaks fundamental assumptions in Android's ClipData.coerceToText().  If you take the clipData from the share Intent that Chrome 55 produces and pass the first item contained in the clipData to coerceToText() a NullPointerException will be thrown when coerceToText() attempts to create an InputStream from the provided URI.  The URI provided in this same manner from Chrome 54 works fine.  This is a breaking change to Android apps that rely on this functionality.

Did this work before? Yes Any 54 version

Chrome version: 55.0.2883.91  Channel: stable
OS Version: Any
Flash Version: