I can not open chrome dev-tools by url when using nativescript via angular:
chrome-devtools://devtools/bundled/inspector.html?experiments=true&ws=localhost:40000
But when copied the link and paste to google chrome, the result is just search
I tried to reinstall google chrome. Delete node_modules folder, package-lock file, and reinstall npm. But can't resolve problem
Chrome 83 broke the devtools url. There's a fix to the NativeScript CLI in 6.7.4 but in the meantime you can just use this url instead:
devtools://devtools/bundled/inspector.html?ws=localhost:40000
Related
I've tried forking and cloning the three.ar.js GitHub repo, then cd'ing in and running 'npm run dev' as suggested in the README, but no matter what I do, I get all kinds of problems. Any help would be great!
npm install http-server
run http-server in the examples folder.
What i did was just copy the example project to my domain, install the WebARonARCore browser on my phone with ADB, paste the URL to the html file in your webARonARCore browser and it works like a charm.
I can even do remote debugging with my chrome browser (only seems to work while my android studio is running and the phone is attached via USB ofcourse).
But this is on an external/remote server though. Don't know about local.
Is there a way in which I can open Firefox and force it to load a temporary add-on (webextension) on startup? Normally I have to manually go to about:debugging and select the extension on my hard drive. I'm looking for a flag I can pass when I load Firefox so that this is done automatically.
If this is not possible, is there a recommended extension I can install to simulate that a user opens this URL and adds this extension?
Yes, you can use the command web-ext run from the directory in which the extension exists. This will start Firefox with the WebExtension installed using a temporary profile. web-ext run is intended for testing your WebExtension add-on during development, not for normal use of Firefox. By default, the web-ext run command will watch your WebExtension's files and automatically reload the extension when any of the files are changed. You can disable this feature by using the --no-reload option.
If you are using a Firefox version below 49, you will need to specify the --pre-install option which uses a different method of installing the extension in the profile. However, if you use the --pre-install, your WebExtension will not be operational if you are trying to use a release or beta version of Firefox and the extension is not signed. This basically means that using --pre-install is not useful for Firefox versions below 49 unless you are using a Developer Edition build. Using --pre-install can be useful for Developer Edition versions of Firefox above 49 if you are wanting to test how your extension behaves during Firefox startup. If you do not use the --pre-install option, your extension is installed as a temporary extension and does not need to be signed to be tested in release versions of Firefox.
If you want to use a specific profile, then you need to specify the profile using the --firefox-profile option. MDN says:
When using a custom profile, web-ext first copies the profile. The custom profile will not be altered.
Installing web-ext
You will need to install web-ext. You can do so by following the instructions in Getting started with web-ext. The instructions are to, after you install node/npm, run the following command:
npm install --global web-ext
References
Getting started with web-ext
web-ext command reference
want to install chrome extension when mac app is installed.
i followed the instructions on the developer site of chrome Other Deployment Options
Tried both the methods
Local file url
Created file external_extensions.json at path /Users/Sadiq/Library/Application Support/Google/Chrome/External Extensions with contents
{
"external_crx": "/home/share/extension.crx",
"external_version": "1.0"
}
But when i restarted chrome the extension at that path is not installed on chrome.
Store Installation:
Created file fhbjgbiflinjbdggehcddcbncdddomop.json at path
/Users/Sadiq/Library/Application Support/Google/Chrome/External Extensions
with contents
{
"fhbjgbiflinjbdggehcddcbncdddomop": {
"external_update_url": "http://test.com/extension_info.xml"
}
}
Created extension_info.xml file at hosting with following code
<?xml version='1.0' encoding='UTF-8'?>
<gupdate xmlns='http://www.google.com/update2/response' protocol='2.0'>
<app appid='fhbjgbiflinjbdggehcddcbncdddomop'>
<updatecheck codebase='https://clients2.googleusercontent.com/crx/blobs/QgAAAC6zw0qH2D JtnXe8Z7rUJP0d-cjv- 4fr0OfD1rZlXmwxm1zzQqbU1RRtbPRUspFh5VJIFInV7jQnzNI5Ax7-tVFFNKUqiQdoiA- 43Tdd46i1AMZSmuUS-XRXhbdPB5d5cMLUhLCthCuF7g/extension_1_0_0_26.crx' version='1.0.0.26' />
</app>
</gupdate>
But when i relaunch the chrome it must install the extension given in the manefest file .At first time it works but when i uninstall the extension and relaunch the browser it doesn't install it again. no oter changes are done
I want to install firefox extension on my mac app install .
Thanks
Sadiq
At first time it works but when i uninstall the extension and relaunch the browser it doesn't install it again.
This is intentional. When programmatically installed extension is uninstalled by the user, it becomes blacklisted and will not trigger installation again.
The user can still manually install it from the store, but there's nothing you can do if it was denied.
I want to install Firebug manually and update configuration settings on my own. I followed below steps:
Downloaded firebug-2.0b1.xpi file (3 MB)
Extracted the content by using winRAR.
put this extracted folder "firebug-2.0b1" inside "C:\Program Files\Mozilla Firefox\extensions"
Now, I run Firefox, but It seems firebug is not installed. This doens't work because some configurations are not done or Profile is not updated. I could like to know if any changes I need to do in folder.
I am doing this because, I couldn't install by drag & drop .xpi file on firefox or install through browser itself.
To install Firebug manually you have to do it differently. There are two ways to run extensions manually:
1. Extract the XPI
Download the XPI file that contains the extension
Locate the 'extensions' folder within your profile (e.g. via Firefox menu > Help > Troubleshooting Information > Show Folder)
Create a new folder within the 'extensions' folder and call it like the add-on's id (for Firebug this is firebug#software.joehewitt.com)
Extract the XPI into that folder
2. Get the sources from the git repository
A detailed description for how to do that can be found on the development setup description on the Firebug wiki. It's similar to the description above with the addition that you'll be able to always get the latest sources.
Two notes:
The folder name must be the same as the addon's ID (look in install.rdf of the addon) In your case it's not firebug-2.0b1 , but firebug#software.joehewitt.com
The directory where the addon should be placed is not where the
Firefox itself is installed, but into your Firefox's profile. By default it's in %APPDATA%\Mozilla\Firefox\Profiles\XXXXX\extensions\ (where XXXXX is name of your profile folder. More info about profiles you can find here)
I've made an extension using the addon sdk, and it works as expected when running with cfx run. But when I pack it in to an xpi using cfx xpi and install it - it stops working - no scripts are injected and I'm not even getting any errors :(
Any ideas on how to fix this, or how can I debug this kind of issue?
Found a solution. I'm simply using the .xpi that Firefox packs automatically for testing. In order to use it, run the cfx run with the -p parameter pointing to a profile you've created, like this:
cfx run -p <your path to firefox>\profiles\someprofile
After running, go the that profile's folder, and find in there the extensions folder, it should be something like this:
<your path to firefox>\profiles\someprofile\extensions
In there you'll have your addon with a weird file name and an .xpi file extension. Rename it to anything you want, leaving the .xpi file extension intact.
EDIT:
Apparently the cfx xpi command strips by default what it thinks to be unused modules and .js files. To avoid this you need to run it with a special flag, like this: cfx xpi --no-strip-xpi
try to uninstall and then reinstall the addon you developed
try installing the addon on another firefox build(aurora, nightly, beta)
What I do in such a case:
Disable extension from Addon Manager.
Restart Firefox.
Open Console Window (Ctrl+Shift+J)
Enable extension and watch for errors in Console.
Sometimes startup errors do not appear in Console window unless it is already opened.
Resetting firefox worked for me.
Type about:troubleshooting in your address bar
Click the reset firefox button in the upper-right hand corner of the Troubleshooting page
(source: mozilla.net)
Confirm your action