How can a Microsoft Edge content script be debugged? - microsoft-edge

Microsoft has some decent documentation on debugging Content Scripts for an Edge Extension and the top of the page even includes a Channel 9 video on the subject.
Unfortunately, the techniques no longer seem to work, as even when following the debug instructions and using the the sample Text Swap extension, the extension and content script never show up in the debugger.
As you can see from the screenshot, the content script has run (and changed the font on the page) but it and the extension itself are nowhere to be seen in the debugger.
Anyone figured out how to get the content script to show up in the debugger?

You can see below screenshot. I have the css under "extension" folder" and js under "no domain" folder. I hope you have the manifest file correct. Looks like your console have errors. you can check check it and correct if necessary.
enter link description here

It appears that the debugger is not consistent in loading the extensions. The script is running, however, the debugger does not always show the extension and the content script.
This is what I have done to ensure visibility of the content script:
Close all open Edge windows.
Launch Edge
Wait for prompt about extensions from unknown sources being turned
off and select 'Turn on anyway.'
Navigate to the URL to debug. In this case it is:
https://developer.microsoft.com/en-us/
Open the debugger (F12)
Right click on the Extension's Icon on the top right of the browser,
to the right of the address bar.
Select 'Manage' and then 'Reload extension.'
Refresh the page.

I was having the same issue. The solution which helped in my case is so obvious that it's nearly embarrassing...:
I mistakenly alsways pressed F12 in any arbitrary tab. That brought up the developer tools for the site that was opened in that particular tab. Just as Ken describes his issue.
Now what helps to get the developer tools for the extension to be debugged, is following the instructions listed in the docs here:https://learn.microsoft.com/en-us/microsoft-edge/extensions/guides/debugging-extensions#background-script-debugging
You simply have to click the Background page link. Then you'll be able to debug your extension.

This was a bug that has been fixed in an upcoming version, see https://developer.microsoft.com/en-us/microsoft-edge/platform/issues/13829248/ for details.

Related

How to view the content of a Xamarin.* library referenced in a project

In VS2019 I want to browse the classes contained in a library included in my project, for example Xamarin.Android.Support.Core.Utils but instead, when double clicking the package, I get the following error message:
"This project cannot be viewed in the object browser because it is unavailable or not yet built. ..."
Is there any other way to browse its content?
Edit: After read the answer of Leo Zhu, I realized that the content of each library can be found in the object browser (as in the following screenshot)
I accept it as a workaround, but it would be better if one can call the Object Browser by right clicking the package, as usual with other libraries.
you could do like this
click tab View -> Object Browser,then you could see the libraries referenced.
you could quickly find the library you want to read by typing keywords in search

Delphi XE7: Debug points not appearing, Breakpoints not getting hit on debugging and CPU window opens up

On building my code i cannot see the debug points in the pages.Only the page which is open while building shows the debug points.Also, The breakpoint is not getting hit and CPU window is opening by default where debug is set. I searched for the same and found this following statement on Embarcadero page (http://docwiki.embarcadero.com/RADStudio/Tokyo/en/CPU_Windows_Index):
The CPU window also opens automatically whenever program execution stops at a location for which source code is unavailable. For example, the debugger cannot open the source file if you link a DLL (Windows) built with debug information but do not include its source file in your project, or if you place the source file in a directory not specified in your project.
I also tried following things:
When I create a new project, put a breakpoint, it hits (no CPU
window opens up in this case).
When I modify the original code (like just put ShowMessage('Hello World');) where debug point is not
hitting, message dialog appears but debug is not hitting.
I
uninstalled and installed XE7 again, but problem persists.
Tried
cleaning the project, but did not work.
Please help me in fixing this problem. Thanks in advance!
As i also had a lot of problems with getting my debugger to work, so i made myself a list of what has to be checked. So here are some things you could try:
use the "debug" buildconfiguration of your project, which should be configured like this
searchpath matches your actual sources
"local symbols" is true
"with debug dcus" is true
"debug-information" is debug-information
"optimization" is false
one time i also had to check "remote debugging symbols"
try to close the ide and reopen it with just one project
if you use devextension, go to devextensions options
under compilation -> check "release compiler unit cache of other projects before compiling"
under extended ide settings -> check "disable package cache"
in delphi options under "debugger options", "integrated debugging" has to be true
(but sometimes it helps to uncheck this, close the ide, reopen and check again)
I hope, this also helps you

Android Studio 3.0 - SDK path not specified

I tried to update Android Studio to 3.0 but got some crazy error, so I uninstalled AS and installed AS 3.0, but now when I try to open a file, I get an "SDK path not specified" error and nothing I select is accepted.
I cannot find any file called "android-sdk" or something similar, which is what most of the other solutions on Stack Overflow suggest selecting.
How do I fix this?
Right now I'm trying this, but no clue if it will help:
1. I went to File -> Settings -> System Settings -> Android SDK
2. I specified C:\ProgramFiles\Android and it's installing.
UPDATE: This more or less worked. I had to install a million updates afterwards, but it solved the problem.
This is halfway there. I found going through the File -> Settings tree that even though I hadn't selected NDK (Native) options, the folder names must not contain spaces. I created an Android/SDK folder tree on a spare drive all its own to alleviate this concern by AS.
Then without a space in the name, I was able to choose SDKs to download, and so it has begun.
Your question and self-confirmation of a work around got me there after I, myself was looking for a couple weeks. Thanks
This is the MOP (Method of Procedure) for this:
Took me a while to figure this out as the documentation is not clear on this at all. Cancel the dialogue box asking for the Android SDK path and do the following:
Open Android Studio IDE. Find the down arrow icon, should be second last icon in the toolbar. Click that. You will see a path for Android SDK Location:. Click the edit link to the right of that. This will bring up the SDK Components Screen. If you can check the boxes there, check them. They may already be checked or they may be disabled. You can leave the path as is, for me its:
C:\Users\<user name>\AppData\Local\Android\Sdk
Depending on whether you had Android Studio before it may say it has detected a previous version and it will only download the components it needs. This is normal. Now click the NEXT button. A confirmation screen will come up with Setup Type and SDK Folder. If you want to change your SDK Folder this is your last chance, if not, click NEXT again.
It may bring up a Terms & Conditions screen, click the Accept radio button then NEXT. It will go and download the Android base SDK. When it's completed click FINISH.
You will then be taken to the Platforms screen where you can select which Android platforms you want to support. ie, Android 9.0 (Pie), Android 8.1 (Oreo). Select all the platforms you need then click APPLY.
The downloader will grab all those packages for you. Next, click the SDK Tools tab. Check the boxes of the tools you want and click APPLY. It may bring up a Terms & Conditions screen again, click the Accept radio button then NEXT. When completed just click FINISH and you're good to go.

uploading firmware to particle io's photon

I am receiving an "Error 1" when using particle io relay - I am using the same exact firmware found here: https://github.com/spark/relayshield. What do I need to change?
1_Blink_a_Relay.cpp:2:37: fatal error: RelayShield/RelayShield.h: No such file or directory
#include "RelayShield/RelayShield.h"
It looks like your code can't find the library you're trying to import. Often (and especially when adapting Arduino code for Particle), the folder name for a library needs to be removed. Try #include "RelayShield.h instead.
If that doesn't work, please provide a little more information, such as your development environment. (Are you using Particle's web-based IDE? Did you import the library from there?)
Cheers!
If you are using the web ide, the one at build.particle.io, then you have to include the library. You have to go to the fifth item on the left menu bar, after flash, compile, save, and code. It should say library, and looks like a bookmark. Click on that. It will pop out a view. Scroll down until you see the Community Library search bar. And search for RelayShield. It will show you the "RELAYSHIELD", which currently is used by 520 people (or something like that). Click on that, and it will open the library. Scroll down on the left side (the one that pops up) until you see the button "Include in App". Click on that, and select your app. After you click on that, it will bring up your app. Then scroll down on that popped out view, until you see "Add to this App". Just click on this button, and then it will include that library in your project.
For Particle Dev on Desktop, it is a lot harder. If you are using Particle Dev, please reply, and I will give you the solution for that. It is very hard to manage libraries with Particle Dev. However, if you want to use the Serial Monitor while using the Particle Build on the internet, what you can do is that you do the regular serial commands on the Particle Build (build.particle.io), and open the Serial monitor on Particle Dev after also connecting to your Particle photon

how to identify path for android using appium

This is for iOS to find all the elements:
driver.findElementsByXPath("//UIAApplication[1]/UIAWindow[1]/UIACollectionView[1]/UIACollectionCell");
I need the similar path for android, I tried:
driver.findElementsByXPath("//android.view.View[1]/android.widget.GridView[1]")
But it's not working. Please help
Please post the log from Appium console, so that we will be able to find out the exact issue.
From :
//android.view.View[1]/android.widget.GridView[1]
It seems there are multiple GridViews are available on that particular screen. Please try to put some constraints.
e.g
//android.view.View[#id='Id_of_the_View']/android.widget.GridView[#something here too]
If you are on a native application, just use the inspector or hierarchy viewer to get the Xpath but I would advise you use driver.findElement(s)ById to get specific elements. Hope this helps.
If you could give a bit more detail maybe I could help.
If you are using Eclipse as editor, then you can open an emulator where you have the app installed, then open DDMS perspective from Eclipse.
Go into your app at the view you want to inspect, and then click the button Dump View Hierarchy for UI Automator in the DDMS perspective.
This will give you a snapshot and you can hover over elements and find their properties.

Resources