Tap command fails

If the Tap command fails, there are several possible causes. 

Please start by identifying the cause using the Failure Analysis feature, then attempt fixes based on the suggestions from MagicPod Autopilot. 

If the issue still cannot be resolved, please follow this help page for troubleshooting.

Table of Contents

• When the failure is caused by the target element not being found
• When the failure is caused by a different element being tapped instead of the target
• When the execution log shows success but the tap is not actually performed
  • Does it also fail when switching from the Tap command to the Tap specified position command?
  • Does it also fail when changing the locator?
  • Does it also fail when executed manually?
  • Does it also fail when executed in a different environment?
• When the cause of failure is unknown

When the failure is caused by the target element not being found

When encountering a case like the screenshot above, the following are possible causes:

• There is a problem with the specified locator, or the target element's locator has changed due to a screen update
• An AI locator is being used
• The target element does not exist on the page because a screen transition in a previous step failed
• The target element took too long to appear

For maintenance methods, please refer to this guide.

When the failure is caused by a different element being tapped instead of the target

The following warning may appear in the execution log before the failure occurs:

tap([“Register” button], {}) 
[WARNING] As operation on the specified element failed, will retry by specifying coordinates. If the target element is covered by another element, the element above will be clicked.
the target position: (1099, 799)

In this case, a different element is overlapping the target element, causing the unintended element to be tapped, leading to failure.
For more details, please refer to this guide.

When the execution log shows success but the tap is not actually performed

To isolate the issue, please check the following:

• Does it also fail when switching from the Tap command to the Tap specified position command?
• Does it also fail when changing the locator?
• Does it also fail when executed manually?
• Does it also fail when executed in a different environment?

Does it also fail when switching from the Tap command to the Tap specified position command?

Switch the Tap command to Tap specified position and run the test again. If the Tap specified position also fails, please try the Tap command instead.

Does it also fail when changing the locator?

Check if changing to an alternative locator suggested in the locators list resolves the issue.
Additionally, try temporarily hide feature to reveal alternative elements for selection.

Does it also fail when executed manually?

Check whether the failure occurs when tapping manually on the cloud device (the device on the right side of the MagicPod test case edit screen). Please verify this through manual operation, not through "Run" options such as partial execution.

Does it also fail when executed in a different environment?

Please investigate from the following three angles:

1. Different app

• If testing in a development environment, check whether the failure also occurs in the production environment or a different development environment. 
  • If it fails in development but succeeds in production, the issue is likely a bug in the app in the development environment — please consult your app developer.

2. Different execution environment

• If it also fails on a real device, the issue is likely a bug in the app itself — please consult your app developer. 
• If it also fails on a simulator/emulator, the issue is likely related to the app's behavior in that environment — please consult your app developer. 
  • For instructions on how to test with a simulator/emulator, refer to: Test app behavior differs between iOS/Android cloud devices and physical devices

3. Different OS

• Check whether the failure also occurs on a different iOS/Android OS version. 
  • Sharing the execution results across OS versions with MagicPod Support will help resolve the issue more quickly.

When the cause of failure is unknown

If none of the steps above resolve the issue, please contact us via the inquiry button on the test results page, including the following information. The more detail you provide, the faster we can help resolve the issue.

// Manual execution result
Success or Failure

// Execution results in different environments (different app, execution environment, OS)
* If you tested multiple environments, please list all results
Environment tested:
Result: Success or Failure