I wanted to upgrade my Chrome app to support offline_enabled flag in CRX manifest. However, when I test it with Chrome 14, it gives me the following error message and it stop downloading the crx.
"Package is invalid. Details: Hosted Apps Cannot use the extension feature 'offline_enabled'"
Any idea how to resolve this problem for Chrome version lower than 15?
Seems to be a Chrome bug.
http://code.google.com/p/chromium/issues/detail?id=98537
Related
For Android Version, less than 11 My app is working fine. But for the versions of Android 11, it shows a message " Please install Chrome Stable 72 or later" when I try to open the app.
Change dependency from
implementation 'com.github.GoogleChrome:custom-tabs-client:a0f7418972'
to
implementation 'com.google.androidbrowserhelper:androidbrowserhelper:2.2.0'
Also make sure Launcher activity in manifest imported from androidbrowserhelper
com.google.androidbrowserhelper.trusted.LauncherActivity
More migration details you can found here
Trusted Web Activity was introduced in Chrome version 72. The issue there is not related to the Android version, but that the version of Chrome installed on the devices showing this message is earlier than 72.
installing the latest version of Chrome from Google Play should solve the issue.
On my local machine i have been using --disable-web-security --user-data-dir
to disable the web security. After upgrading to Chrome Version 66 i have started getting Blocked current origin from receiving cross-site document at ... warning. How to disable the web security for this version of chrome ?
Found a workaround mentioned in https://www.chromium.org/Home/chromium-security/site-isolation
C:\Program Files (x86)\Google\Chrome\Application>chrome.exe --disable-web-securi
ty --user-data-dir --disable-features=CrossSiteDocumentBlockingIfIsolating
This has apparently been fixed in Chrome 67. You can find the bug I reported and a workaround here. The command-line workaround requires you to start Chrome with the following argument:
--disable-features=CrossSiteDocumentBlockingIfIsolating,CrossSiteDocumentBlockingAlways
Simply add
--disable-site-isolation-trials
This works in Chrome 68.
I've read about the Chrome Headless from developers.google said we can run the Google without UI. Quote from that link :
Headless Chrome is shipping in Chrome 59. It's a way to run the Chrome
browser in a headless environment. Essentially, running Chrome without
chrome! It brings all modern web platform features provided by
Chromium and the Blink rendering engine to the command line.
Why is that useful?
A headless browser is a great tool for automated testing and server
environments where you don't need a visible UI shell. For example, you
may want to run some tests against a real web page, create a PDF of
it, or just inspect how the browser renders an URL.
This is really great feature, so I do some experiment with this cool feature. The idea is to taking snapshot as the document site by do call of chrome.exe from Windows Command Prompt, as follow :
chrome --headless --disable-gpu --screenshot https://www.chromestatus.com/
After do several times and following the instruction from these site. I got nothing. I don't get any picture or screenshot with name screenshot.png as document mention it before Running with --screenshot will produce a file named screenshot.png in the current working directory.
From this document also said about version,
Caution: Headless mode is available on Mac and Linux in Chrome 59.
Windows support is coming in Chrome 60. To check what version of
Chrome you have, open chrome://version.
after do some check with suggested before, I run chrome://version on my Chrome on Windows x64 Machine and got some result :
Google Chrome 62.0.3202.94 (Official Build) (64-bit) (cohort: Stable)
Revision 4fd852a98d66564c88736c017b0a0b0478e885ad-refs/branch-heads/3202#{#789}
What wrong? What i missed?
Thanks
After do some experiments. for --screenshot will save the image on the same level as chrome.exe location and that will be mean save on Program Files.
So we need need to combine parameter names and arguments with a =
--screenshot="D:\screen.png" will work, otherwise Chrome writes to it's installation folder. Big design flaw, no software should use it's installation folder as a working directory.
Here are the complete argument :
chrome --headless --enable-logging --disable-gpu --screenshot="D:\screen.png" "https://www.chromestatus.com/"
After upgrading to Chrome 56 on Mac, it seems that inline Chrome extensions no longer prompt an installation anywhere on the web.
Does anyone know why?
Console gives the following error message:
Uncaught Error: A Chrome Web Store installation is already pending.
at Installer.install (extensions::webstore:20)
at Object.install (extensions::webstore:82)
at installChromeExtensionm ((index):643)
at HTMLAnchorElement.onclick (VM1380 :1)
This seems to be an issue for all websites that have inline Chrome extensions (try grammarly.com, or momentumdash.com) - tested with multiple macbooks using Chrome 56.0.2924.87
I had a couple of user script that worked in version 3.5 by adding command line option --enable-user-script, after I upgraded to version 4.0, all those scripts stop working. Chrome browser is promoting its extension, some of user script can be replace by a chrome extension. Can anybody confirm if latest chrome browser stop supporting user script?
The latest Chrome builds allow you to install a user script as an extension with no modification. Just open the .user.js in the browser.