tools-chunk.js:1 Uncaught (in promise) TypeError: Cannot read properties of undefined (reading 'isBetaEnabled')
at _callee5$ (tools-chunk.js:1:36102)
at tryCatch (dc-core.js:2:269829)
at Generator.invoke [as _invoke] (dc-core.js:2:269568)
at Generator.next (dc-core.js:2:270312)
at asyncGeneratorStep (bootstrap.js:1:218361)
at _next (bootstrap.js:1:218643)
2Navigated to chrome-extension://efaidnbmnnnibpcajpcglclefindmkaj/viewer.html?pdfurl=http%3A%2F%2Fmydomain%2Fmyfile.pdf%0A
This was initially reported by our users on the latest version of Chrome running under Windows 10 x64.
I was not able to recreate this on Chrome 101.0.4951.64 (Official Build) (x86_64) on a Mac (MacOS Montery 12.3.1)
I WAS able to recreate this on Chrome 101.0.4951.67 (Official Build) (64-bit) running on Windows 10 on Parallels VM.
I WAS also able to recreate this on Chrome 102.0.5005.63 (Official Build) (64-bit) running on Windows 10 on Parallels VM.
The version of the extension is: Adobe Acrobat: PDF edit, convert, sign tools, 126.96.36.199
I'm not sure why you're asking about "Acrobat Pro DC".
This is happening in the Adobe Acrobat Chrome Extension, NOT in a standalone Adobe Acrobat app.
I do NOT have any version of the Acrobat app installed in the Windows VM.
If I load these files directly into Chrome, they don't appear to be loaded into the Adobe Acrobat Chrome Extension, but by Chrome itself. At least, I do not see the displayed PDF surrounded by the Adobe Acrobat Chrome Extension toolbars.
Can you indicate how I can get the Adobe Acrobat Chrome Extension to handle a file loaded from the filesystem? The extension appears active when PDF files are loaded into Chrome from a web server, but not from the filesystem.