This topic provides information on how to resolve the common issues you may encounter while working on web and mobile applications automation.

General Issues

This topic provides information about the general issues that you may see while working with Qualitia Studio.

...

Version Control Error: Object Reference not set to an instance of an object.

Image Modified

This error occurs when SharpSVN is used as version control tool for the Qualitia test assets. Few SharpSVN components require Microsoft Visual C++ 2010 SP1 Redistributable package.

...

Unable to Switch to Mobile Web-View

Problem: In the Qualitia Mobile Recorder, you might not be able to open a web application or web-view context of a hybrid application if chrome has more than 20 open tabs. Unable to switch to Mobile Web View and Loader keeps on Loading the screen.

...

1. Stop the agent.

2. Go to Applications > MOSAgent > Right click >Show package content > Contents > MacOS.

3. Double-click RunAgent.
   A terminal opens to start the agent.

4. In the logs, find the following message using the WDA path:
   /var/folders/vt/f2c8mcz536x6d9_vbgs7dh740000gn/T/QualitiaMOSAgent/WDATemp
   Note: This path differs for every user.

5. Copy that path and open in finder.

6. Delete all the content inside the WDATemp folder.

7. Download WDA v2.20.0 for your Xcode version from the following location:
   https://github.com/appium/WebDriverAgent/releases
   Note: Download the WDA version that best matches to your Xcode Version.

8. Extract the downloaded file, copy all the contents, and paste
   them in the WDATemp folder in the following location: /var/folders/vt/f2c8mcz536x6d9_vbgs7dh740000gn/T/QualitiaMOSAgent/WDATemp
   Note: This path differs for every user, you must find the WDATemp folder path as explained in step. 4.

9. Open WebDriverAgent.xcodeproj in Xcode and make sure you set proper Team and check Automatically manage signing in the Signing and Capabilitiessection for WebDriverAgentLib, WebDriverAgentRunner and IntegrationApptargets.

10. Click Product > Build for >Testing.
11. After the build is succeeded, click Product > Build.
12. Close Xcode.
13. In the agent, connect to a device and select an application. 
    Note: You might have toperform this step every time you restart the machine as the temp folders are deleted and recreated whenever the machine restarts. 

Unable to Boot Emulator in MOS Session.

Problem: The following error message "View For the device is failed. Please connect again" appears when you try to launch an emulator in an MOS Session is created with Cold Boot.

...

Qualitia Configuration File does not exist, can you please save Qualitia Configuration

Image Modified

This issue occurs when the configuration file is missing. The file is created when you save the configuration settings for the first time.

This issue may occur when creating offline package (from File > Offline Package) as well.

Solution:

1. Log on to Qualitia Automation Studio.
2. On the Setting menu, click Configuration Setting.
3. Click OK.
4. Now create an offline package from File > Offline Package.

...

• Generate the PAT with a user that is part of the Project Administrators group.
  Qualitia recommends this option for generating a PAT.

• Allow Bypass Rules on Work Items Updates
  Perform the following steps:

  • In TFS/Azure DevOps project, ensure that the user that is used to generate PAT is member Contributors group / Project Team members group.

  • Click Project Settings > Permissions.

  • Select the user group that has the user to whom you want to provide access (Contributors/Project Team members).

  • From the Bypass rules on work items updates list, select Allow.
    Refer to the following screenshot.

Qualitia does not recommend this option for PAT generation as it changes the access levels for all the users in the group.

Note: Please connect with your Azure DevOps Admin team to discuss the PAT generation and access level management.

...

Teamcity Agent Running Headless Execution on Window Server System

Sometimes users are unable to view the test case execution on the designated TeamCity build agent. 

It is observed that setting the right Java path resolves this problem. You can try below:

...