Hi i have serius problem
I have done a job with uipath that works manuell execution on Test server and prod servern
But when i use the orchestrator it crashes anyone else have got this problem?
UiPath.Core.SelectorNotFoundException: Could not find the UI element corresponding to this selector
And how it get it fixed?
It is a selector issue through the orchestrator it won't be possible to fix it permanently, you need to use the UiPath Studio to repair the selector. selector screenshot
I found that the target was to static and id inserted a
tag=gen-57
to become
tag=gen-*
Related
I created a login sequence and my selectors for the input email, password, click login and element exists are valid. But only when I have the Internet Explorer page open on the website I'm working with.
I did that sequence again, and I ran it, initially it worked but when I ran the hole project it broke again, I tried "repair" and "indicate", I tried to eliminate the title but nothing is working.
As far as I can see, you are using selector attribute:
"title=ACME System 1 - Dashboard"
Try using a wildcard: title='ACME System 1*', so it can work when you leave the dashboard.
This worked for me when I took those UiPath Academy courses.
In order to automate tasks within a browser with UiPath, the browser must be open. There is an activity called Open Browser that's included in the default activities for every project. You need to add this activity to the beginning of your sequence and pass in the appropriate parameters, (ie. URL, browser type) you can then pass the outputted browser variable to an attach browser sequence and execute your browser automation acivities within that.
Browser activity sceenshot
In addition, the selector that you have shared does not look like a stable selector. There may be other 'H1' elements on the screen that will cause your automation to fail. I would use the UI explorer to help you build a better, more stable selector.
Did you initially use IE to indicate screen elements and then changed the BrowserType property to use a different browser? Please share the sequence to suggest you a fix for your issue.
I would also suggest you to modify the selector to 'title='ACME System *'.
In order for selector to work the application needs to be open and the desired element needs to be available. So when you close the browser the selector disappears.
You may consider swithching to 'Modern Design Experience' and use 'Use Application/Browser' scope to make this more intuitive, and it will also automatically open the browser for you if it is closed.
I'm trying to figure out a CPU performance problem using PerfView, my application is an Asp.Net Core 2.2 running on IIS. According to this video https://channel9.msdn.com/Series/PerfView-Tutorial/PerfView-Tutorial-2-A-Simple-CPU-Performance-Investigation the "Caller" is the main point to find the performance problem, but in my collections it's showing just a "ROOT" entry and it's not expandable, see:
Any help?
Tks
The view in your screenshot is showing "Methods that call module coreclr <<coreclr?>>" so as you expand the tree, it's showing you what called the current item. ROOT is the end of the line because nothing called that, which is why you can't expand beyond that.
The item above ROOT is the dotnet process that started your assembly.
I released an upgrade to my VB6 application and I get this error on some screens at run time. The problem seems to depend on the data. The problem does not happen on the previous version of my application. Thus I am wondering what the error means
The problem is to do with listview.
I had item declared as a MSComctlLib.ListItem
the code failed at
item.ListSubItems("Deliver").Bold = True
because I had no such column heading.
I have a Windows Phone 8.1 WinRT application. I am using SemanticZoom + ListView combination to display a grouped list through a CollectionViewSource. When I remove all items from all the groups (which are ObservableCollections) and start putting the items back to these empty groups the debugger breaks and shows up with "agip.*" something at a point where it reads DISABLE_XAML_GENERATED_BREAK_ON_UNHANDLED_EXCEPTION; This used to happen for a while but now for a reason I do not know my app just exits and debugging stops without any error message; This is why I cannot remember the exact filename.
I have two questions:
1) How can I get the debugger work again i.e. to display that "agip.*" something page and not just silently quit?
2) By trial and error I managed to track down the cause of this by changing
<ListView.GroupStyle><GroupStyle HidesIfEmpty="true"
to <ListView.GroupStyle><GroupStyle HidesIfEmpty="false".
And voila my app works without any problems. Could this be a bug in the WinRT?
PS: I can achieve HidesIfEmpty behaviour by binding group header visibility to .items.count through a converter so that's not an issue here.
Answering your questions
1) How can I get the debugger work again i.e. to display that "agip.*" something page and not just silently quit?
Try this. Open the Exception settings window: menu Debug -> Windows -> Exception settings. Check all the exception categories.
However, I didn't get it to work. It simply breaks with an unhandled win32exceptions, not giving any idea of where did it occur and doesn't give any details on the exception, even when attaching another Visual Studio instance to debug the devenv.exe process with all exceptions handled.
2) By trial and error I managed to track down the cause of this by changing <ListView.GroupStyle><GroupStyle HidesIfEmpty="true" to <ListView.GroupStyle><GroupStyle HidesIfEmpty="false". And voila my app works without any problems. Could this be a bug in the WinRT?
Looks like it is a bug.
Your workaround
I can achieve HidesIfEmpty behaviour by binding group header visibility to .items.count through a converter so that's not an issue here.
This approach doesn't look good on Windows 10, for example, where the group header has a border on the bottom. So hiding the TextBlock doesn't hide the group header completely. (Maybe I'm doing something wrong).
I solved the problem in a different way.
Another workaround
After clearing each group of the grouped collection, try to make a delay. Like this:
foreach(var group in GroupsCollection)
{
group.Clear();
await Delay(1); // this is workaround
group.Add(newItem);
}
This has helped in my case.
I get the infamous "Dialogs must be user-initiated" Security Exception when I try to print some stuff in Silverlight. As you can see, the dialog is as user-initiated as can be:
John Papa couldn't help me much out neither, because I don't have any breakpoint set. Mr MSDN thinks it could also be that I'm just taking too long, but this is a demo application just as simple as can be.
Any ideas? I guess it's a Visual Studio quirk, maybe some extensions interfering, as things seems to work when I launch the application outside of it. I first thought maybe the Code Contracts are interfering with their IL weaving, but they are deactivated for this project.
Update: This is just a simple Silverlight application that runs locally from the file system. When I do "Start debugging", Visual Studio creates a hosting HTML file containing the Silverlight app in the Debug resp. Release folder of the project, launches the Internet Explorer with that HTML file and attaches the debugger to it.
Update 2: I also get the same error when I create a web project to host the Silverlight app and create a virtual directory for it on IIS.
I might also want to add that I don't have problems with printing in other Silverlight projects regardless of their hosting scenarios.
Update 3: I downloaded FireFox and it works, I don't get the error when I debug with it. So it seems to have to do with my IE8. I uploaded the solution:
http://dl.dropbox.com/u/10401470/Code/Demos/PrintingDemo.zip
I wonder if anyone can reproduce?
Anyone got an idea to which team I should file a bug report? Silverlight team? IE team? VS Debugger team?
I'm able to reproduce this. You have handled the Click twice, once in XAML another time in code. See your MainPage.xaml
<Button x:Name="PrintButton"
Content="Gotta print 'em!" Margin="8"
Click="PrintButton_Click" />
Don't feel bad about it. I did it last time through a misplaced Print inside a loop.
I've also experienced this strange behaviour. A standard button click event immediately invoking an OpenFileDialog. It would frequently generate the same error when being debugged but would eventually be coaxed in to working when the button is clicked several times.
However when built as a release (or perhaps simply by running the same Xap without a debugger attached to the browser) the problem would go away.
Try to remove
if(SightPaleceListBox.Items.Count > 0)
I had the same problem and found out that the reason was this following line:
cnvsMain.Children.Remove(PrintPagePlaceHolder);
cnvMain is on the page that the user pushed the Print button on (I was trying to remove it from that page in order to add it to the canvas that I was going to print).
My tip: try to comment rows one by one, until you find what row causes the problem. Than try to work around it.