Hacktoberfest 2026: le issue che i maintainer hanno segnato per ottobre, aperte e adatte ai principianti. Sfoglia le issue Hacktoberfest

AbstractMethodError for abstract Widget class - since migration to byte-buddy

Aperta
  • Qualcosa non va?
#2,372 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 5 giorni

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
4/5
Tempo stimato
3-5 giorni
Idoneità per principianti
50/100
Tipo di issue
Bug
Chiarezza
Abbastanza chiara
Stato di attività
Ferma
Stack tecnologico
android, ios, java
Ambito
mobile-dev, testing-qa

Direzione di ricerca

Inizia con l’esempio di Widget astratto in Page-objects.md e segui come OverrideWidget, WidgetInterceptor e field.getType() selezionano la classe del widget. Riproduci i casi Android e iOS dell’issue, quindi verifica che le chiamate alle implementazioni della piattaforma non sollevino più AbstractMethodError quando si usa Byte Buddy.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

bug
Is there an existing issue for this?
  • I have searched the existing issues
Appium Version

2.0.1

Appium Host Type

Command Line

Are you using Appium components not maintained by the Appium team?

No response

Is this issue reproducible using the latest components?
  • I confirm the issue is still reproducible with the latest component versions
Current Behavior

Currently my repo(Android & iOS combined) is using java-client version: 8.3.0
I did not update my version since I got issues with the new byte buddy library. I tried to update to the latest java client version(10.0.0) and still, I get the same issue.
The issue:
I am working according to this docs: PO - abstract Widget class.
When I run my tests using a java client with byte buddy I get AbstractMethodError.

Expected Behavior

To work as it did with cglib.

Appium Log

No response

Environment Details
  • Debug details (appium --show-debug-info):
  • Last component version(s) which did not exhibit the problem: appium 2.0.1, java-client 10.0.0
  • Platform and version of device under test: android
  • Real device or emulator/simulator: emulator
Minimal Reproducible Example

Reproduction:
Consider the following setup in your PO:

public class MyPO {

  @OverrideWidget(androidUIAutomator = CustomWidget.AndroidCustomWidget.class, iOSXCUITAutomation = CustomWidget.IOSCustomWidget.class)
  private CustomWidget myCustomWidget;

}

Your Widget class:

public abstract class CustomWidget extends Widget {

public abstract void abstractTest();

  public static class AndroidCustomWidget extends CustomWidget {
          @Override
          public void abstractTest() {
              //android implementation
          }
  }

  public static class IOSCustomWidget extends CustomWidget {
          @Override
          public void abstractTest() {
              //iOS implementation
          }
  }

}

Then in the test class just call:
myPO.getCustomWidget().abstractTest();
You'll get AbstractMethodError since byte buddy tries to call the original abstract method signature

Further Information

I also managed to find the issue and fix it locally. I will detail my steps here.
First, acording to this Callable implements no-abstract methods by default ByteBuddy's proxies(which are essentially just subclasses) subclass the Widget class and passing calls to the Interceptor(in our case Appium's WidgetInterceptor) for non-abstract methods. The issue is that it subclasses the original CustomWidget and thus it cannot call myWidget.abstractTest() and throwing AbstractMethodError. Instead, it needs to subclass AndroidCustomWidget or IOSCustomWidget according to the platform we are currently using. Since the abstractTest method is non-abstract in AndroidCustomWidget and IOSCustomWidget, byte buddy will override and intercept those methods as well - resulting in the desired behavior.

Fix example:

Image

I was just testing and found out that the java client passes widgetType = (Class<? extends Widget>) field.getType(); which in our case is the abstract class CustomWidget, I added a check for android OverrideWidget and it worked perfectly(since the widgetType is now of type AndroidCustomWidget). In cglib it used to work but I guess byte buddy implements things differently so the the code needs to take into consideration the current platform and the Widget class that overrides it.

Lingua principale
Java
Stelle
1.3k
Fork
755
Merge medio
5g 14h
PR unite (30g)
8

Preparare l'ambiente

  • Nessun Dockerfile né file Docker Compose
  • Ha un modello di pull request
  • Nessuna guida per i contributori

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di appium/java-client

Tutte le issue di appium/java-client

Issue simili

Altre issue su Java

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.