org.mockito.exceptions.misusing.PotentialStubbingProblem:Strict stubbing argument mismatch

org.mockito.exceptions.misusing.PotentialStubbingProblem:
Strict stubbing argument mismatch. Please check:

Typically, stubbing argument mismatch indicates user mistake when writing tests.
Mockito fails early so that you can debug potential problem easily.
However, there are legit scenarios when this exception generates false negative signal:

• stubbing the same method multiple times using ‘given().will()’ or ‘when().then()’ API
  Please use ‘will().given()’ or ‘doReturn().when()’ API for stubbing.
• stubbed method is intentionally invoked with different arguments by code under test
  Please use default or ‘silent’ JUnit Rule (equivalent of Strictness.LENIENT).
  For more information see javadoc for PotentialStubbingProblem class.

11.2 异常信息
org.mockito.exceptions.misusing.PotentialStubbingProblem: 
Strict stubbing argument mismatch. Please check:
 - this invocation of 'getWithCache' method:
    serviceFacade.getWithCache(
    "code"
);
    -> at com.xxx.lambda$getService$3(xxx.java:132)
 - has following stubbing(s) with different arguments:
    1. serviceFacade.getWithCache(
     "code"
);
      -> at com.xxxTest.should_xxx_successfully(xxxTest.java:89)
    2. serviceFacade.getWithCache(
     "code"
);
      -> at com.xxxTest.should_xxx_successfully(xxxTest.java:94)
Typically, stubbing argument mismatch indicates user mistake when writing tests.
Mockito fails early so that you can debug potential problem easily.
However, there are legit scenarios when this exception generates false negative signal:
  - stubbing the same method multiple times using 'given().will()' or 'when().then()' API
    Please use 'will().given()' or 'doReturn().when()' API for stubbing.
  - stubbed method is intentionally invoked with different arguments by code under test
    Please use default or 'silent' JUnit Rule (equivalent of Strictness.LENIENT).
For more information see javadoc for PotentialStubbingProblem class.

• when(mock.someMethod(any())).thenReturn(“output1”);
• when(mock.someMethod(eq(“input2”))).thenReturn(“output2”);