UserAgent: Mozilla/5.0 (X11; CrOS armv7l 9334.58.0) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/58.0.3029.89 Safari/537.36
Platform: 9334.58.0 (Official Build) beta-channel veyron_minnie

Steps to reproduce the problem:
This pertains to Android apps downloaded from the Play store, not Chrome apps downloaded from the Chrome web store.

1. Install a file manager from the Google Play store. I reproduced the issue with both AndroZip Pro and Ghost Commander file management programs.

2. Open the file management program, and allow it to access storage if prompted. Navigate to any file with (I believe) an extension lacking a default app association.

3. Observe the error dialogue: "Parse error / there was a problem parsing the package."

I can reproduce this behavior with .lua and .conf files, as well as files with no file extension. Common files with .jpg, .pdf, etc will open successfully with their default viewers, though. And multiple file management apps cause the issue, which leads me to think that this is probably an issue with the system's 'app picker' rather than any one app.

What is the expected behavior?
A dialog should open asking which program should open the file, with 'Just Once' and 'Always' options.

What went wrong?
The system seems to run into a problem, displaying an error message: "Parse error / there was a problem parsing the package."

A screenshot is attached.

Did this work before? Yes Stable channel release

Chrome version: 58.0.3029.89  Channel: beta
OS Version: 9334.58.0
Flash Version:
 

Deleted: Screenshot 2017-05-03 at 10.28.06 AM.png 123 KB

	Screenshot 2017-05-03 at 10.28.06 AM.png 123 KB View Download