About the Issues/Bugs category

Post bugs or issue here

Please mark your post with the following tags:##

  • Platform you are automating (iOS or Android)
  • Appium version
  • Simulator/Emulator or Real Device
  • The language you are using for writing tests (client binding)
  • Your OS

If you have any server logs, please include them at the bottom of your post inside a code block ( ``` )

1 Like

Hi Jonahss,

Could you answer to my post. I am getting error while running junit test using appium on Android Emulator.
I have posted my error in detail.

Hi Jonahss,

Can you please help me in installing Appium server on android studio.? Is it compatible for android studio? or do I prefer eclipse?

any quick help will be appreciable.

Hi Jonahss,

Can you please help me in launching android app by using AndroidDriver constructor .
Actually i am trying to launch android app by using following code.

void launchApp()

{
     try {
      
         DesiredCapabilities capabilities = new DesiredCapabilities();
         capabilities.setCapability("platformVersion", "4.4");
         capabilities.setCapability("platformName", "Android");
         capabilities.setCapability("app", "D:/ETPortfolio/app/ET_V2.0.0.apk");
         capabilities.setCapability("appActivity", "com.et.reader.activities.StartPageActivity");
         capabilities.setCapability("appPackage", "com.et.reader.activities");
         capabilities.setCapability("deviceName", "Android")
         AndroidDriver driver =  new AppiumDriver(new URL("http://127.0.0.1:4723/wd/hub"), capabilities);
       } catch(Exception e){
            e.printStackTrace();
      
       }          

But i get an error ie. ā€˜Driver can not be resolved a variableā€™. Please tell me ,Can i launch the app using AndroidDriver or not??? Any quick help will be appreciable.

Perhaps my main post is unclear. Please post in the general forum, and give your post the ā€œIssues/Bugsā€ category. Thanks.

Not able to automate scroll down in windows universal application.

Appium version: 1.6.0
Application: windows

Hi Jonahss,
Could you help me solving the following bug, thanks!

Please help me to reslove this issue

  • Platform you are automating (Android)
  • Appium version:-1.22.3
  • Real Device
  • The language you are using for writing tests (client binding):Java
  • Your OS :-10
    C:\Users\Roopa.BS>appium
    [Appium] Welcome to Appium v1.22.3
    [Appium] Appium REST http interface listener started on 0.0.0.0:4723
    [debug] [HTTP] Request idempotency key: 79379f7b-a07e-4abc-91c4-ce15ca563e60
    [HTTP] --> POST /wd/hub/session
    [HTTP] {ā€œdesiredCapabilitiesā€:{ā€œappā€:ā€œC:\Users\Roopa.BS\eclipse-workspaces\UpiAutomation\src\upi2.apkā€,ā€œplatformVersionā€:ā€œ10ā€,ā€œautomationNameā€:ā€œuiautomator2ā€,ā€œplatformNameā€:ā€œAndroidā€,ā€œudidā€:ā€œGQPZUW854LMJROGEā€,ā€œdeviceNameā€:ā€œRedmi 9 Activā€},ā€œcapabilitiesā€:{ā€œfirstMatchā€:[{ā€œappium:appā€:ā€œC:\Users\Roopa.BS\eclipse-workspaces\UpiAutomation\src\upi2.apkā€,ā€œappium:automationNameā€:ā€œuiautomator2ā€,ā€œappium:deviceNameā€:ā€œRedmi 9 Activā€,ā€œplatformNameā€:ā€œandroidā€,ā€œappium:platformVersionā€:ā€œ10ā€,ā€œappium:udidā€:ā€œGQPZUW854LMJROGEā€}]}}
    [debug] [W3C] Calling AppiumDriver.createSession() with args: [{ā€œappā€:ā€œC:\Users\Roopa.BS\eclipse-workspaces\UpiAutomation\src\upi2.apkā€,ā€œplatformVersionā€:ā€œ10ā€,ā€œautomationNameā€:ā€œuiautomator2ā€,ā€œplatformNameā€:ā€œAndroidā€,ā€œudidā€:ā€œGQPZUW854LMJROGEā€,ā€œdeviceNameā€:ā€œRedmi 9 Activā€},null,{ā€œfirstMatchā€:[{ā€œappium:appā€:ā€œC:\Users\Roopa.BS\eclipse-workspaces\UpiAutomation\src\upi2.apkā€,ā€œappium:automationNameā€:ā€œuiautomator2ā€,ā€œappium:deviceNameā€:ā€œRedmi 9 Activā€,ā€œplatformNameā€:ā€œandroidā€,ā€œappium:platformVersionā€:ā€œ10ā€,ā€œappium:udidā€:ā€œGQPZUW854LMJROGEā€}]}]
    [debug] [BaseDriver] Event ā€˜newSessionRequestedā€™ logged at 1662367132446 (14:08:52 GMT+0530 (India Standard Time))
    [Appium] Appium v1.22.3 creating new AndroidUiautomator2Driver (v1.70.1) session
    [debug] [BaseDriver] W3C capabilities and MJSONWP desired capabilities were provided
    [debug] [BaseDriver] Creating session with W3C capabilities: {
    [debug] [BaseDriver] ā€œalwaysMatchā€: {
    [debug] [BaseDriver] ā€œplatformNameā€: ā€œandroidā€,
    [debug] [BaseDriver] ā€œappium:appā€: ā€œC:\Users\Roopa.BS\eclipse-workspaces\UpiAutomation\src\upi2.apkā€,
    [debug] [BaseDriver] ā€œappium:automationNameā€: ā€œuiautomator2ā€,
    [debug] [BaseDriver] ā€œappium:deviceNameā€: ā€œRedmi 9 Activā€,
    [debug] [BaseDriver] ā€œappium:platformVersionā€: ā€œ10ā€,
    [debug] [BaseDriver] ā€œappium:udidā€: ā€œGQPZUW854LMJROGEā€
    [debug] [BaseDriver] },
    [debug] [BaseDriver] ā€œfirstMatchā€: [
    [debug] [BaseDriver] {}
    [debug] [BaseDriver] ]
    [debug] [BaseDriver] }
    [BaseDriver] Session created with session id: 738b0b04-e1ff-49a0-a374-04aff1c45fa3
    [BaseDriver] Using local app ā€˜C:\Users\Roopa.BS\eclipse-workspaces\UpiAutomation\src\upi2.apkā€™
    [debug] [UiAutomator2] Checking whether app is actually present
    [ADB] Found 3 ā€˜build-toolsā€™ folders under ā€˜C:\Users\Roopa.BS\AppData\Local\Android\Sdkā€™ (newest first):
    [ADB] C:/Users/Roopa.BS/AppData/Local/Android/Sdk/build-tools/32.1.0-rc1
    [ADB] C:/Users/Roopa.BS/AppData/Local/Android/Sdk/build-tools/32.0.0
    [ADB] C:/Users/Roopa.BS/AppData/Local/Android/Sdk/build-tools/30.0.3
    [ADB] Using ā€˜adb.exeā€™ from ā€˜C:\Users\Roopa.BS\AppData\Local\Android\Sdk\platform-tools\adb.exeā€™
    [debug] [ADB] Running ā€˜C:\Users\Roopa.BS\AppData\Local\Android\Sdk\platform-tools\adb.exe -P 5037 start-serverā€™
    [AndroidDriver] Retrieving device list
    [debug] [ADB] Trying to find a connected android device
    [debug] [ADB] Getting connected devices
    [debug] [ADB] Connected devices: [{ā€œudidā€:ā€œGQPZUW854LMJROGEā€,ā€œstateā€:ā€œdeviceā€}]
    [AndroidDriver] Using device: GQPZUW854LMJROGE
    [ADB] Using ā€˜adb.exeā€™ from ā€˜C:\Users\Roopa.BS\AppData\Local\Android\Sdk\platform-tools\adb.exeā€™
    [debug] [ADB] Running ā€˜C:\Users\Roopa.BS\AppData\Local\Android\Sdk\platform-tools\adb.exe -P 5037 start-serverā€™
    [debug] [ADB] Setting device id to GQPZUW854LMJROGE
    [debug] [ADB] Running ā€˜C:\Users\Roopa.BS\AppData\Local\Android\Sdk\platform-tools\adb.exe -P 5037 -s GQPZUW854LMJROGE shell getprop ro.build.version.sdkā€™
    [debug] [ADB] Current device property ā€˜ro.build.version.sdkā€™: 29
    [ADB] Getting device platform version
    [debug] [ADB] Running ā€˜C:\Users\Roopa.BS\AppData\Local\Android\Sdk\platform-tools\adb.exe -P 5037 -s GQPZUW854LMJROGE shell getprop ro.build.version.releaseā€™
    [debug] [ADB] Current device property ā€˜ro.build.version.releaseā€™: 10
    [debug] [ADB] Device API level: 29
    [UiAutomator2] Relaxing hidden api policy
    [debug] [ADB] Running ā€˜C:\Users\Roopa.BS\AppData\Local\Android\Sdk\platform-tools\adb.exe -P 5037 -s GQPZUW854LMJROGE shell ā€˜settings put global hidden_api_policy_pre_p_apps 1;settings put global hidden_api_policy_p_apps 1;settings put global hidden_api_policy 1ā€™ā€™
    [debug] [AndroidDriver] Parsing package and activity from app manifest
    [debug] [ADB] Error: end of central directory record signature not found
    [debug] [ADB] at C:\Users\Roopa.BS\AppData\Roaming\npm\node_modules\appium\node_modules\yauzl\index.js:187:14
    [debug] [ADB] at C:\Users\Roopa.BS\AppData\Roaming\npm\node_modules\appium\node_modules\yauzl\index.js:631:5
    [debug] [ADB] at C:\Users\Roopa.BS\AppData\Roaming\npm\node_modules\appium\node_modules\fd-slicer\index.js:32:7
    [debug] [ADB] at FSReqCallback.wrapper [as oncomplete] (node:fs:660:5)
    [debug] [UiAutomator2] Deleting UiAutomator2 session
    [UiAutomator2] Restoring hidden api policy to the device default configuration
    [debug] [ADB] Running ā€˜C:\Users\Roopa.BS\AppData\Local\Android\Sdk\platform-tools\adb.exe -P 5037 -s GQPZUW854LMJROGE shell ā€˜settings delete global hidden_api_policy_pre_p_apps;settings delete global hidden_api_policy_p_apps;settings delete global hidden_api_policyā€™ā€™
    [debug] [BaseDriver] Event ā€˜newSessionStartedā€™ logged at 1662367137766 (14:08:57 GMT+0530 (India Standard Time))
    [debug] [W3C] Encountered internal error running command: Error: Cannot extract a manifest from ā€˜C:\Users\Roopa.BS\eclipse-workspaces\UpiAutomation\src\upi2.apkā€™. Is it a valid Android application?
    [debug] [W3C] at ADB.packageAndLaunchActivityFromManifest (C:\Users\Roopa.BS\AppData\Roaming\npm\node_modules\appium\node_modules\appium-adb\lib\tools\android-manifest.js:38:11)
    [debug] [W3C] at Object.getLaunchInfo (C:\Users\Roopa.BS\AppData\Roaming\npm\node_modules\appium\node_modules\appium-android-driver\lib\android-helpers.js:347:5)
    [debug] [W3C] at AndroidUiautomator2Driver.startUiAutomator2Session (C:\Users\Roopa.BS\AppData\Roaming\npm\node_modules\appium\node_modules\appium-uiautomator2-driver\lib\driver.js:369:21)
    [debug] [W3C] at AndroidUiautomator2Driver.createSession (C:\Users\Roopa.BS\AppData\Roaming\npm\node_modules\appium\node_modules\appium-uiautomator2-driver\lib\driver.js:229:7)
    [debug] [W3C] at AppiumDriver.createSession (C:\Users\Roopa.BS\AppData\Roaming\npm\node_modules\appium\lib\appium.js:387:35)
    [HTTP] <-- POST /wd/hub/session 500 5502 ms - 843
    [HTTP]
Summary
  1. List item