Absolutely, this is totally doable! You don’t need Appium Inspector to capture real user taps and pull element identifiers like resource ID or XPath—here are two solid approaches to make this work with Appium and Android’s native capabilities.

Option 1: Use Android Accessibility Service (Real-Time Capture) #

This is the best approach for real-time tracking of actual user clicks, since Android’s Accessibility Service can listen system-wide for interaction events and extract element details directly from the UI hierarchy.

How to implement it: #

1. Build a simple Accessibility Service
   Create a basic Android service that listens for TYPE_VIEW_CLICKED events, filters for your target app’s package name, and extracts element info (resource ID, XPath, etc.). Here’s a core snippet:

   public class TapCaptureService extends AccessibilityService {
       private static final String TARGET_PACKAGE = "com.your.target.app";
   
       @Override
       public void onAccessibilityEvent(AccessibilityEvent event) {
           if (event.getEventType() == AccessibilityEvent.TYPE_VIEW_CLICKED 
               && TARGET_PACKAGE.equals(event.getPackageName())) {
               
               AccessibilityNodeInfo tappedNode = event.getSource();
               if (tappedNode != null) {
                   // Get resource ID
                   String resourceId = tappedNode.getViewIdResourceName();
                   // Generate XPath for the element
                   String xpath = generateXPath(tappedNode);
                   
                   // Log the info (we'll pick this up in Appium later)
                   Log.d("TapTracker", String.format("ID: %s | XPath: %s", resourceId, xpath));
                   
                   tappedNode.recycle(); // Don't forget to recycle nodes to avoid memory leaks
               }
           }
       }
   
       // Helper method to build an XPath string for the element
       private String generateXPath(AccessibilityNodeInfo node) {
           StringBuilder xpathBuilder = new StringBuilder();
           AccessibilityNodeInfo currentNode = node;
           
           while (currentNode != null) {
               int siblingIndex = 0;
               AccessibilityNodeInfo parent = currentNode.getParent();
               
               if (parent != null) {
                   // Count siblings with the same class name to handle indexing
                   for (int i = 0; i < parent.getChildCount(); i++) {
                       AccessibilityNodeInfo sibling = parent.getChild(i);
                       if (sibling.equals(currentNode)) {
                           xpathBuilder.insert(0, String.format("/%s[%d]", currentNode.getClassName(), siblingIndex + 1));
                           break;
                       }
                       if (currentNode.getClassName().equals(sibling.getClassName())) {
                           siblingIndex++;
                       }
                   }
                   currentNode = parent;
               } else {
                   xpathBuilder.insert(0, "/" + currentNode.getClassName());
                   break;
               }
           }
           return xpathBuilder.toString();
       }
   
       @Override
       public void onInterrupt() {
           // No action needed here for our use case
       }
   }
   

   Don’t forget to declare the service in your AndroidManifest.xml with the required permissions and filters.

2. Deploy and enable the service

   • Package this service into a small APK and install it on your test device/emulator.
   • Go to Settings > Accessibility and enable the service (you’ll need to grant permission for it to monitor interactions).

3. Capture logs in your Appium script
   Use adb logcat to listen for the logs our service generates, while running your Appium session. Here’s a Python example:

   import subprocess
   import time
   from appium import webdriver
   
   # Start logcat to listen for our TapTracker logs
   logcat_proc = subprocess.Popen(
       ["adb", "logcat", "-s", "TapTracker:D"],
       stdout=subprocess.PIPE,
       stderr=subprocess.PIPE,
       text=True
   )
   
   # Initialize Appium session
   desired_caps = {
       "platformName": "Android",
       "deviceName": "YourDeviceName",
       "appPackage": "com.your.target.app",
       "appActivity": ".MainActivity",
       "noReset": True
   }
   driver = webdriver.Remote("http://localhost:4723/wd/hub", desired_caps)
   
   # Real-time log parsing
   try:
       print("Listening for user taps...")
       while True:
           line = logcat_proc.stdout.readline()
           if line:
               print(f"Captured Tap: {line.strip()}")
           time.sleep(0.1)
   finally:
       logcat_proc.terminate()
       driver.quit()
   

Option 2: Appium + Coordinate-Based Lookup (Non-Real-Time) #

If real-time isn’t a strict requirement, you can combine Appium’s element querying with coordinate capture (via adb or the Accessibility Service) to find elements after a tap occurs.

Quick example (Python): #

1. First, capture the tap coordinates (you can use adb shell getevent or the Accessibility Service above to get these).
2. Use Appium to find the element at those coordinates:

   # Assume we have tap coordinates (x, y)
   tapped_element = driver.find_element_by_android_uiautomator(f"new UiSelector().clickable(true).point({x}, {y})")
   
   # Extract element details
   resource_id = tapped_element.get_attribute("resourceId")
   # Get XPath using Appium's mobile command
   xpath = driver.execute_script("mobile: getXpath", {"elementId": tapped_element.id})
   
   print(f"Tapped Element - ID: {resource_id}, XPath: {xpath}")
   

Key Notes: #

• Permissions: The Accessibility Service requires user consent—make sure to guide testers through enabling it on the device.
• Package Filtering: Always filter events to your target app’s package name to avoid capturing taps from other apps.
• XPath Accuracy: The custom XPath generator may need tweaks for complex UI hierarchies (like handling elements with unique content descriptions).
• Compatibility: Accessibility API behavior can vary slightly across Android versions, so test on your target OS versions.

内容的提问来源于stack exchange，提问作者t1daz