I have created a new project in UiPath Studio Community Edition v.2021.10.4, and created a new 'Test Automation' project. And created the steps to open a browser, go to specified address and type in login/password and click OK button.
The issue is when I try to run the script that I created not debug, it runs on debug mode in Chrome, and this navbar pops up in Chrome which says : UiPath Web Automation 21.10 has started debugging this browser. , and when it ends the browser closes automatically :
What I want is to execute this script normally, not in a debug mode, and the browser stays open, so I can implement the next steps in my developments.
I managed to solve this by changing the input method of the Activity "Use Application/Browser" from Chromium API to Hardware Events.
Related
I have created a personal Tabs app and deployed the same on MS teams.
Things are working as expected, but at 1 stage of time, my application goes back to the original "contentUrl" page as defined in the manifest.json file.
This might be an issue with my frontend code, so i wanted to understand how can we debug the frontend developer console to check if there's any error being thrown from my application?
The only way to figure out what is going on is to use the DevTools. To use DevTools in the desktop client, you must:
Ensure you have enabled developer preview.
Open up a tab so you have something to inspect with the DevTools.
Open the DevTools one of the following ways:
On Windows, you open DevTools via the Microsoft Teams icon in the
desktop tray.
The following example shows DevTools open and inspecting a tab configuration dialog:
Ref Doc-https://learn.microsoft.com/en-us/microsoftteams/platform/tabs/how-to/developer-tools
I have a react native android app that i am currently debugging on a windows machine with a android emulator.
I can hit http://localhost:8081/debugger-ui
And it tells me that
React Native JS code runs inside this Chrome tab.
Press ⌘⌥J to open Developer Tools. Enable Pause On Caught Exceptions for a better debugging experience.
Status: Waiting, press ⌘R in simulator to reload and connect.
When I open up the chrome developer tool, I do not see my react code being loaded into the "source" of that tab.
So my question is, how do I make it so that my phone loads the react stuff into the chrome tab? I wish to at least see the console.log stuff appearing in my chrome developer tool.
OK. Found what to do:
Ctrl + M to open up some "developer menu"
click on enable remote JS debugging
Depending on your react native version, chrome may or may not open up the debugging tab. But in any case, go to localhost:8081/debugger-ui should do it.
I have a web application that uses IIS, but when I try to debug it VS just locks up and gives me the hour glass cursor icon. No browser window opens, nor does an instance pop up in the Task Manager. VS says its Running / not "Not Responding", but I cannot interact with the IDE. Can't Ctrl-Break to stop or anything.
I was able to run it before, and I'm not aware of any system or IIS changes that could cause this. I've disabled source control and I've tried launching the app in both Chrome and IE but it still behaves the exact same way as described above.
Has anyone else encountered this? The only threads I could find just describe general slowness in the IDE but otherwise its functional. The recommended fix was to disable the source control functionality, which as I said I already tried.
I should note that I don't seem to have an issue running & debugging winforms applications. I also just created a web application and was able to launch it in Chrome and get to the homepage. Also, it doesn't make a difference if I have a breakpoint set or not.
This solution has 4 different projects. If I set a different project as the Startup Project, it does run and launches the browser but it just gives me a 'file explorer' sort of view where it just lists the files in that project's directly which is obviously not what I want.
Edit; If I manually open a browser tab, try to navigate to http://localhost/myApplication, VS pops up and asks if I want to attach process w3wp.exe to IIS APPPOOL\myAppPool. If I attach, it opens a new tab in Chrome and my application runs. But unless I do these 2 steps, it does not run.
I am working on a .NET 4.5.1 project in Visual Studio and have Web Essentials installed and functioning in all other ways except finding unused CSS. When I test with a new project, it works as expected.
Is there a known situation in which Unused CSS will not work?
Environment:
VS2013 Pro
Win7 Pro
Steps to reproduce:
Start debugging the app in Chrome
Once the site opens in a new tab, select Start Recording in the Browser Link Dashboard
Change content by clicking through the site
Results:
Recording has started and Stop Recording is now available
There are no messages sent to the output window
Clear CSS Usage Data option in the Browser Link toolbar (in the top menu) is disabled. It never is enabled whether recording or not.
Expected:
Messages in the output view
Ability to clear CSS usage data
Attempts to troubleshoot:
Installed prior version of extension - same result
Verified the issue exists on Chrome, Firefox and IE
Other features of Browser Link work as expected
Creating a new project works as expected and "Clear CSS usage data" is not greyed out
Browser Link drop down menu
I know it's a long time since you asked this, but this solution might actually help someone else...You can identify unused CSS using Chrome Dev tools
Open your chrome Dev tools
Click on the Audits tab
Click on Run at the bottom, wait for the audit to finish
You will get unused CSS under Remove unused CSS rules in the Web Page Performance section
I have a solution which contains the following:
Website Project (using local IIS 7
server) with a Default.aspx page
Console app (sends request to Default.aspx page in Website Project
When I place debug points in the Default.aspx page and run the console app, the debugger does not start. I know the code in there is executed because it returns the proper response.
Why is the debugger not working?
You need to start the web project from within Visual Studio or attach the debugger to the running process before starting your console application. I'd recommend the former.
Then when you start the console application your break points should be hit.