I am having this same issue with a few Chromebooks in our school. I did find that if you pin the app to the shelf it will open. If using the launcher it will not. Another possible workaround until the issue is resolved. 

Tried that as well. It didn't work for me :(

Logs/policies from test environment after replicating the issue:

https://drive.google.com/open?id=1dn-Kk87zw9qN-FtoxoHryo0ja_vbL6cp

Thanks for reporting the issue. Could you let us know if the users having the issue enabled Google Play Store?

ykrychala@,
After reproducing the issue, could you file a feedback report and link the report here? Thanks.

@jcliang No, Google Play is disabled for their OU. But, other users in the same OU don't have this issue.
Should I try to enable it and see if that will fix the problem?

amardale@,
Could you reproduce the error and send a feedback report from that device?
It will be really helpful in debugging.
And yes, you can try to turn on Google Play to see if that fixes the problem for the user, but before that, could you please send the feedback report?

The issue happens regardless of Google Play being enabled or not.Here is some background information from my test enviroment:

--Steps to reproduce-- 
1.Sign in to Chromebook running Chrome OS 69.0.3497.120 or higher 
2.Launch the camera app from the apps launcher (First time it works) 
3.Close the app, and try to launch it from the apps launcher a second time. 

--Expect result-- 
Camera app should launch on subsequent launch attempts. 

--Actual result-- 
Camera app fails to launch. 

Workaround 
-Launch the app from the Chrome Web Store page at https://chrome.google.com/webstore/detail/camera/hfhhnacclhffhdffklopdkcgdhifgngh 

--Additional Notes-- 
-The issue can be replicated on Beta (70.0.3538.69) 
-Camera app works fine on 68.0.3440.118 
-The issue can be replicated on any Chromebook with an integrated camera. 
-Issue cannot be replicated on Chromebox with external camera connected to it. 
-If the user profile is recreated, the app launches successfully for the first time again. 

Logs can be found here:
https://drive.google.com/open?id=1dn-Kk87zw9qN-FtoxoHryo0ja_vbL6cp

I also submitted feedback today at 11:44 AM CST time Here is the link to the report:

https://support.google.com/chromebook/answer/3142217?visit_id=636761726529132114-3802207932&p=feedback_confirmation&rd=1

Hi llinares@
Re #12, the link to feedback report seems not working?

What king of link are you looking for? That is the one I got when I submitted feedback. If you can specify what you are looking for, I probably get it, as the issue can be easily replicated on any Chromebook.

Hi
The place where we locate a specific report is in:
https://listnr.corp.google.com/product/208/reports?dateRange=30
Could you paste the link to one of the report there?
Maybe you can type some special strings (like your ldap) in the feedback report description, so that we can search later. Really thanks for your help. 

Oh nvm. I found it:
https://listnr.corp.google.com/product/208/report/85746423026

I can't find any relevant logs in the feedback. And I also tried caroline 70.0.3538.69 (11021.58.0) and it works fine.

 Issue 901186  has been merged into this issue.

I successfully reproduced the bug on google.com account. I think this bug happens on all N devices for all managed accounts. The cause of it is that GCA package is stripped out for managed accounts. "pm list packages -f" does not contain GCA.

Since this is a ARC++ issue, I created b/118860552. Please track that bug for further updates.

Yes, this exact same issue is highly impacting our entire K-12 district since OS 69+ - hoping for a quick resolution! 

To add more context:
Starting with Chrome OS 69, we've rolled out a change that would set the default camera app to the newly released Android Google Camera App (or GCA).
GCA was incorrectly removed from the preinstalled packages due to a provisioning error. Therefore, our camera launcher could not locate and launch GCA.

We're working with corresponding team to address this.
Sorry for the inconvenience.

In the mean time, if you do need a camera app,
1. You can still open our original Chrome Camera App from our Chrome Web Store page at: https://chrome.google.com/webstore/detail/camera/hfhhnacclhffhdffklopdkcgdhifgngh
2. If this is a possibility, disable Play store and you should be able to start the camera app (Chrome Camera App) again.
3. Install a third-party camera app from Chrome Web Store or Play Store.

Thank you! Very helpful information. Hopefully the fix can be implemented soon now that the root cause has been identified.  

Any new updates on this one in getting the preinstalled packages rebundled into an update? 

 Issue 902726  has been merged into this issue.

We have a CL out that will switch N device to CCA as default.

Ok, so that will get CCA working again by default - and GCA will come later and be the default?

GCA will only be default on P devices

Just to verify, would this also affect camera usage for SSO login from the login screen?  Some schools utilize Clever (https://clever.com/) to allow students to log into the device using QR codes.

No this shouldn't affect any third-party camera applications, only the builtin camera apps and the Android apps that use GCA.

Hmm... Sorry I spoke too soon.

From b/118860552, it seems like Clever is affected, though I'm not sure why.
It looks like they're using a web app which should not be affected.

bigo@,
Is Clever an android app? If not, it should not be affected by this. We will need a separate bug to track any issues Clever is encountering.

Clever isn't an android app. It is an sso solution that utilizes the the camera for logging in with QR codes. This is the relevant policy: "Single Sign-On Camera Permissions"

https://support.google.com/chrome/a/answer/1375678?hl=en

Does it utilize the builtin camera app for taking pictures (presumably for QR code scanning)?

If it isn't an Android app and it's not using the builtin (Android) Google Camera App, then that would be a different issue that needs to be looked at.

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

commit c028d7085fdc469ffdf4efec3f9ae8d22d1e3640
Author: Sheng-Hao Tsao <shenghao@google.com>
Date: Fri Nov 09 10:59:55 2018

Only open GCA if ARC is P or above

This CL changes the consolidated camera app icon logic so that it
launches GCA/GCA migration app only if ARC is P or above. This is to
address 2 problems:

1. Android N and below do not support external cameras. We would like
users to use CCA so that they can still utilize external cameras.
2. Managed users in Android N still have the problem where GCA could be
stripped out.

Bug: b:118860552, chromium:896140 
Test: Used N devices (caroline) with google.com account and verified
that CCA is opened.

Change-Id: I7836d2b4256856028901e5e542f460e7107fc8db
Reviewed-on: https://chromium-review.googlesource.com/c/1316982
Commit-Queue: Sheng-hao Tsao <shenghao@google.com>
Reviewed-by: Steven Bennetts <stevenjb@chromium.org>
Reviewed-by: Tao Wu <wutao@chromium.org>
Cr-Commit-Position: refs/heads/master@{#606795}
[modify] https://crrev.com/c028d7085fdc469ffdf4efec3f9ae8d22d1e3640/chrome/browser/ui/app_list/internal_app/internal_app_metadata.cc

#30, I can't find a specific bug RE the Clever issue, but their support team seems to be aware of the issue
https://www.reddit.com/r/k12sysadmin/comments/9spnqn/psa_clever_and_chromeos_v71/

The clever bug should be
https://bugs.chromium.org/p/chromium/issues/detail?id=900323 which I think
we've fixed (awaiting verification).

Am Fr., 9. Nov. 2018, 14:24 hat wgibson via monorail <
monorail+v2.2974353477@chromium.org> geschrieben:

Do we know what version will the fix be merged into?

I was told the camera issue was resolved yesterday. This is what my Google ticket states:

"Thank you for your kind response.  The fix has been applied to the current Chrome OS version 70.0.3538.76"

However, I'm not seeing that it's been resolved and have responded to let them know. 

We will need to also cherry-pick the fix to the release branches.

Ok, I will hold off again on testing until I hear from you all. 

I tested on 72-11258.0.0 nautilus that camera icon opens CCA.
I would like to request to merge the fix to 71 and 70.
This bug is blocking all managed account users from opening camera app through launcher icon. I think it worth pushing out stable release of M70 again.

This bug requires manual review: M71 has already been promoted to the beta branch, so this requires manual review
Please contact the milestone owner if you have questions.
Owners: benmason@(Android), kariahda@(iOS), kbleicher@(ChromeOS), govind@(Desktop)

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

+kbleicher

Can you review this merge request?

Merge Approved for ChromeOS M71

Hi geohsu@,
Could you also approve for M70?

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

commit a3791ae2dfd02223b0398a140c6bfaeae11f3fa7
Author: Sheng-Hao Tsao <shenghao@google.com>
Date: Fri Nov 16 06:05:10 2018

Only open GCA if ARC is P or above

This CL changes the consolidated camera app icon logic so that it
launches GCA/GCA migration app only if ARC is P or above. This is to
address 2 problems:

1. Android N and below do not support external cameras. We would like
users to use CCA so that they can still utilize external cameras.
2. Managed users in Android N still have the problem where GCA could be
stripped out.

Bug: b:118860552, chromium:896140 
Test: Used N devices (caroline) with google.com account and verified
that CCA is opened.

Change-Id: I7836d2b4256856028901e5e542f460e7107fc8db
Reviewed-on: https://chromium-review.googlesource.com/c/1316982
Commit-Queue: Sheng-hao Tsao <shenghao@google.com>
Reviewed-by: Steven Bennetts <stevenjb@chromium.org>
Reviewed-by: Tao Wu <wutao@chromium.org>
Cr-Original-Commit-Position: refs/heads/master@{#606795}(cherry picked from commit c028d7085fdc469ffdf4efec3f9ae8d22d1e3640)
Reviewed-on: https://chromium-review.googlesource.com/c/1338591
Reviewed-by: Ricky Liang <jcliang@chromium.org>
Cr-Commit-Position: refs/branch-heads/3578@{#727}
Cr-Branched-From: 4226ddf99103e493d7afb23a4c7902ee496108b6-refs/heads/master@{#599034}
[modify] https://crrev.com/a3791ae2dfd02223b0398a140c6bfaeae11f3fa7/chrome/browser/ui/app_list/internal_app/internal_app_metadata.cc

Rejecting for M70. We are not taking P1 fixes now that M70 has gone to 100%. M71 Stable is a few weeks away, let's address this there.

Hi team, just to confirm, will this be fixed on M71?

Yes, it will be fixed on M-71.

Yes, the fix has been merged to M71.

Not reproducible: Tested on Eve, Nocturne, Nautilus, Basking, with build 11316.29.0, 72.0.3626.22 (dev) channel. (CCA 5.3 canery)