appium / appium/java-client

Getting the exception in latest Appium Library for get("logcat") for Android device

Open
#1,666 7 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Java
Stars
1.3k
Forks
752
Avg merge
6d 21h
Merged PRs (30d)
8

Description

Description

When we try to get the logs from manage().logs().get("logcat") we are getting 404 errors, till 7.5.1 version this method was working fine, but when we have switched to 8.0.0 Java client this is throwing the error.

Environment

  • Java client build version : Java client library 8.0.0
  • Real device or emulator/simulator: Real Device
  • Cloud Platform : Sauce Labs
  • App : Native App

Details

We have tried the below steps :
AndroidDriver mobileAndroidDriver = new AndroidDriver ();
mobileAndroidDriver.manage().logs().get("logcat") throws 404 error
mobileAndroidDriver.manage().logs().getAvailableLogTypes() Also throws errors

AppiumDriver driver = new AndroidDriver();
driver.manage().logs().get("logcat") throws 404 error.
driver.manage().logs().getAvailableLogTypes() Also throws errors

As we cannot call now AppiumDriver driver = new AndroidDriver(); in new Java clent, we tried with AndroidDriver mobileAndroidDriver = new AndroidDriver (); still no luck.

We couldnt see any doc mentioning there is a change of this logs as its not deprecated.

Link To Appium Logs

(https://gist.github.com/krnnarayan/e1e7f8ea446b2a25c69ab86a53c52a11)

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with AndroidDriver and the manage().logs().get("logcat") and getAvailableLogTypes() calls described in the issue, comparing Java client 7.5.1 with 8.0.0. Review the linked Appium logs and the W3C logging behavior to determine whether the 404 is a client regression or an unavailable endpoint. Done means identifying the cause and documenting or fixing the behavior, with a regression check for Android log retrieval.

Written by the indexing model from the issue text.

Assessment

Tech stack
android, java
Domain
mobile, testing-qa
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.