调用目标异常:

我坚信，任何命名惯例都有勤奋的思想投入 在里面。而且，很有可能我们的问题都有他们的问题 答案就在名字里，如果我们试着找出名字背后的原因。

Let's break the name up into 3 parts. "Exception" has occurred when "Invoking" a "Target" method. And, the exception is thrown with this wrapper when, a method is invoked via reflection in Java. While executing the method, there could be any type of exception raised. It is by design, that the actual cause of the exception is abstracted away, to let the end user know that the exception was one that occurred during a reflection based method access. In order to get the actual cause, it is recommended that the exception is caught and ex.getCause() is called. Best practice is to, in fact throw the cause from the catch block that caught the InvocationTargetException

try{
    method.invoke();
} catch(InvocationTargetException ite) {
    throw ite.getCause();
} catch(Exception e) {
    // handle non-reflection originated exceptions
    throw e;
}

我知道它与其他答案类似，但我想更清楚地说明Java生成这种异常类型的“何时”，因此它对任何人来说都是一个谜。

这将打印特定方法中的精确代码行，当调用该方法时，会引发异常:

try {

    // try code
    ..
    m.invoke(testObject);
    ..

} catch (InvocationTargetException e) {

    // Answer:
    e.getCause().printStackTrace();
} catch (Exception e) {

    // generic exception handling
    e.printStackTrace();
}

问题还可能是targetSdkVersion升级了，并且您使用了已弃用的Gradle清单特性。尝试再次降低targetSdkVersion，看看它是否有效。在我的例子中，它是targetSdkVersion 31 -> 30

使用InvocationTargetException上的getCause()方法检索原始异常。

您可以使用getCause()方法与原始异常类进行比较，如下所示:

try{
  ...
} catch(Exception e){
   if(e.getCause().getClass().equals(AssertionError.class)){
      // handle your exception  1
   } else {
      // handle the rest of the world exception 
   }
} 

来自Method.invoke()的Javadoc

如果底层方法抛出异常，则抛出:InvocationTargetException。

如果调用的方法抛出异常，则抛出此异常。