Image recognition is the last approach to automating applications if nothing else works to identify UI elements on the screen (like selectors or keyboard shortcuts). Because image matching requires elements to be fully visible on the screen and that all visible details are the same at runtime as during development when resorting to image automation extra care should be taken to ensure the reliability of the process. Selecting more/less of an image than needed might lead to an image not found or a false-positive match.
Here are a few examples of common challenges:
Different web-browsers and operating systems render texts and images differently , resulting in different UI element images in each execution environment.
The application’s UI layout usually adapts to the size of the application’s window , causing the size or location of UI elements such as buttons, text boxes and images to change. This is especially problematic for full-screen applications because their size is dynamically determined by the screen resolution of the hosting device.
Identical UI controls may appear multiple times in a single application screen (e.g., multiple text boxes in a form). Further tuning is required to identify a specific image occurrence.
Do read the best practices UiPath documentation for better understanding.