New issue
Advanced search Search tips

Issue 923191 link

Starred by 1 user

Issue metadata

Status: Untriaged
Owner: ----
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 1
Type: Bug



Sign in to add a comment

Unhandled KeyError: 'Cannot find an extension with id=behllobkkfkfnphdnhnkndlbkcpglgmj'

Project Member Reported by wzang@chromium.org, Jan 18 (5 days ago)

Issue description

While creating a Chrome instance in Autotests, this error is always shown with the following arg combinations:

auto_login==False && autotest_ext==True   [1]

or 

auto_login==False && arc_mode=arc_common.ARC_MODE_ENABLED

This error comes from [2]. The extension the ID refers to is [3].

Currently there're no auto tests using this combination, but this is necessary for Demo Mode tests, because auto_login should be disabled in order to examine OOBE, and autotest_extension should be used for launching ARC apps. 

Not sure this should be more related to ARC or extensions. Any pointers are appreciated!


[1] https://cs.corp.google.com/aosp-master/external/autotest/client/common_lib/cros/chrome.py?type=cs&q=autotest_ext&g=0&l=117

[2] https://cs.chromium.org/chromium/src/third_party/catapult/telemetry/telemetry/internal/backends/chrome/extension_backend.py?type=cs&q=%22Cannot+find+an+extension+with+id%22&g=0&l=36

[3] 
https://cs.corp.google.com/chromeos_public/src/third_party/autotest/files/client/common_lib/cros/autotest_private_ext/?q=autotest_private_ext+file:%5Esrc/third_party/+package:%5Echromeos_public$&dr
 

Comment 1 by wzang@chromium.org, Jan 18 (5 days ago)

Thanks achuith@ for pointing out that I could create another Chrome instance (with auto_login==True) and launch arc app there.

I tried this but the problem is the second Chrome instance will no longer be in demo session, so I'll only be able to test that a random Android app can be launched in a normal user session (which the current ARC autotests already covered), but not the "force-installed" apps can be launched in a demo session.

Can we somehow get access to the profile under which the extension is available?

Comment 2 by wzang@chromium.org, Jan 19 (4 days ago)

There may be a race. The error is not shown about 10% of the time, and it goes away entirely if we wait for a few seconds after login, before accessing the extension. Although all the current auto tests assume the extension always exist without polling, and they seem to be working fine.

Sign in to add a comment