I need to check a bug in Google Chrome for specific version like 14.0.802.30. How can I get the pervious version for that? Also, how can I switch off automatic update functionailty of Chrome?
Some old Chrome-Versions can be found on oldapps.com if you can't find the version there, you can maybe use the corresponding Chromium release? Its basically Chrome minus the Google-Spyware. For Operating Systems other than linux you have to build your own version tough (easy to follow instructions are published on the website).
Chromium-Releases can be found here
Related
App build with ActionScript3/Harman SDK but we don't even have REQUEST_INSTALL_PACKAGES declared in our xml.
Also, I already checked the APK via Android Studio, the AndroidManifest doesn't contain also REQUEST_INSTALL_PACKAGES.
Any fix or advice for this? Thank you.
We checked our SDKs/ANE DISTRIQT and none of them that we are using is using the REQUEST_INSTALL_PACKAGES.
Check all of the available APKs for your application.
Google will check all available versions of your application so even if your update doesn't have the permission an older build may have. When updating you may have an older version available for different users.
Go through and disable or remove all older versions as part of the update have this permission before releasing.
I want to use stable chrome version at pptr, so i search https://omahaproxy.appspot.com/ for finding chromium build.
but build 902210 is not in chromium browser snapshot( https://commondatastorage.googleapis.com/chromium-browser-snapshots/index.html)
is there something another way to find stable chromium build?
I had the same issue so here is what I found in case it helps:
On https://www.chromium.org/getting-involved/download-chromium, it is written "you can get a build of Chromium 44.x which should mostly match the stable release" and "sometimes you may have to decrement the commit number until you find one".
I searched the latest version number (which is currently 94.0.4606.81) on https://omahaproxy.appspot.com/ but cannot find its build number (911515, known as Branch Base Position on the previous link) on https://commondatastorage.googleapis.com/chromium-browser-snapshots/index.html?prefix=Linux_x64/.
So I decremented the number until I find one matching, like explained previously and I found 911494: https://commondatastorage.googleapis.com/chromium-browser-snapshots/index.html?prefix=Linux_x64/911494/
When I downloaded this Chromium version, in "About Chromium", it displayed "Version 94.0.4606.0 (Developer Build) (64-bit)". Which almost matches 94.0.4606.81.
On https://githubmemory.com/repo/Bugazelle/chromium-all-old-stable-versions/issues/2, I read "You cannot install a stable Chromium version downloaded from chromium-browser-snapshots because there are absolutely no Chromium stable versions there." and "It is recommended to compile Chromium yourself to have a similar stable version... or find third-parties builds.".
Linux distributions like Ubuntu provide a stable Chromium package. Otherwise if we don't want to compile the stable version, we can get the closest developer version like explained previously.
Is this possible? I think I may have missed something obvious here. I have a live UI scripts app, and I need to fix a bug. The potential bugfix has to be tested on multiple browsers, so it actually has to be published, instead of just trying out the "current version". This means that it has to be published to a new URL.
Thanks.
it actually has to be published, instead of just trying out the "current version" ?
There is no reason why using different browsers should prevent from using de 'dev' version of an app... you can login in many browser at the same time and play with the dev version on each browser (I do that very often using a couple of android and osX browsers simultaneously). Did you try and did you meet issues doing so ?
I can't seem to find a clear answer on this anywhere.
How far back is it backwards compatible? Do I have to be concerned about creating multiple versions of the extension?
Thanks
"manifest_version": 2 itself does not cause any incompatibility issues.
But you can easily make a mistake and create an extension which is backwards-incompatible, by using features/APIs which are introduced in Chrome 18 or later (manifest v2 came with Chrome 18).
I suggest to not worry about the old manifest version any more, because only Chrome 17- is affected. As of writing, the current stable version is 23. Hardly anyone is using Chrome 17 any more.
See also
How to upgrade extension to manifest v2 and remain backwards compatible? (Stack Overflow answer)
Tutorial: Migrate to Manifest V2 (Official documentation, apply the tips in the reverse order)
Manifest version 2 extensions have to use "background" instead of "background_page" (and the manifest cannot contain it or Chrome refuses to load the extension), but "background" is not supported in older versions of Chrome. This is the main problem.
The only work around I can think of is to publish multiple versions of your extensions and ask users to download and install the correct version.
Edit: The bug that caused this problem has been fixed. The #version tag now works in the stable release. See Issue 30760
Hey.
I've been wondering how I might set the version number displayed for user-scripts in Chrome's extension tab
(source: advefir.com)
So far the obvious methods have failed:
// ==UserScript==
// #version 1.1.5
// #uso:version 1.1.5
// ==/UserScript==
I know Greasemonkey for Firefox doesn't use a version value, but since Chrome actually displays a version number, I thought it might.
Perhaps this is a feature that has not been implemented?
Or maybe it was never intended to be there, but it is there because extensions have version numbers, and user-scripts are currently installed as extensions?
(I'm using the Linux beta, version: 4.0.249.43, by the way)
Thanks.
Ok, this appears to be a confirmed bug now. (Issue 30760)
Seems the standard #version meta-data is the correct usage, but it has not yet been implemented.
Edit: The #version tag now works in the stable release of Chromium (and, therefore, Chrome).
Or maybe it was never intended to be there, but it is there because extensions have version numbers, and user-scripts are currently installed as extensions?
I think so.
Version number used for updating extensions. User scripts currently can not update. "Update extensions now" button doesn't work for them.
Fixed, but apparently not yet released:
http://code.google.com/p/chromium/issues/detail?id=30760#c16