Logcat & Video: https://pantheon.corp.google.com/storage/browser/chromiumos-test-logs/bugfiles/cr/669631/

+feature owner 
+tpm 
+morning planners

Not being able to access files seems like a reason to block dev on ARC++ boards.

WDYT tpms?

Is this only seen with ES file explorer? What about other file management apps?

Not specific to one app. None of the ARC++ apps can access files from Downloads folder.

It is because M56 branch for Android is not cut yet.

For b/32103402 I submitted changes to both Chrome OS and Android. Android change depends on Chrome OS change. Unfortunately Chrome OS change did not make it to Chrome OS M56 branch cut, but Android change is currently included because we still use ToT Android image for M56.

Possible solutions are:
1. Correctly cut Android M56 branch at the same point as Chrome OS M56 branch.
2. Cherry-pick my Chrome OS change to M56 branch.
3. Roll-back my Android change on ToT.

I hoped (1) is done soon, but it's almost two weeks since the branch cut date. I'm also requesting merge approval for (2) in b/32103402 but I got no response for a week.

Hm, I was not accurate; it seems mnc-dr-arc-m56 branch already exists at this moment, but it contains my Android change (which depends on missing Chrome OS change). Assuming that we are not going to align Chrome OS / Android branch cut point in M56, remaining solutions are:

2. Cherry-pick my Chrome OS change to M56 branch.
3. Roll-back my Android change on M56 branch.

Actually  you are still right, it looks like the place we define what branch for the PFQ to pull from has moved and is duplicated, so a change went in to point at the new branch but we appear to be uprevving on the old branch.

https://chromium-review.googlesource.com/#/c/414617/ should fix that if everything else is set up. 

At this moment, release-R56-9000.B does NOT contain my Chrome OS change, but mnc-dr-arc-m56 contains my Android change. So even after we start buliding Chrome OS M56 with mnc-dr-arc-m56 Android, this issue will continue.

If we will forcibly reset mnc-dr-arc-m56 branch to the same timing as release-R56-9000.B it should be fine, but I guess we won't. Then we still need to do either (2) or (3) in #10.

I would say which ever you feel is most appropriate, consider the merge of either solution approved. 

Sure, I'll go with (2).

Cherry-pick has been done. I tried to build Chrome OS M56 locally, but it did not finish before I left office today. I will try verification tomorrow.

dhaddock@ please verify that this fix landed and working as intended, thanks.

gkihumba@ Issue exists. Fix is not yet available in today's M56 build 9000.11.0, 56.0.2924.11. 

test are now passing.
https://cros-goldeneye.corp.google.com/chromeos/console/listBuild?
milestone=57#/details

+sdantuluri to do a bit more testing before mark as verify

wait, there hasn't been a new M56 build yet.

https://cros-goldeneye.corp.google.com/chromeos/console/listBuild?milestone=56#/
the next one would be 9pm today.

Verified that Downloads is working on M56 branch, after cros_workon start chromeos-cheets-scripts.

I assume next bot run will uprev ebuild, am I right?

You mean the android container? It should be updating itself on a regular basis now. 

Verified fix on ChromeOS  9000.12.0, 56.0.2924.12 samus, minnie, cyan

Marking as fixed.

Marking verified (from comment #25)