Inconsistency in Appium Test Case Execution(Android Platform)

Issues/Bugs
11

Hi Aleksei,
used all types of wait function as suggested by you in above link including implicit wait before the App drawer Click Functrion as below

try {
Thread.sleep(10000);
} catch (InterruptedException e) {
e.printStackTrace();
}

    System.out.println("END :" + driver.currentActivity());

    MobileElement el11 = (MobileElement) driver.findElementByAccessibilityId("Open navigation drawer");
    el11.click();

still faced below Issue

[debug] [BaseDriver] Waiting up to 0 ms for condition
[debug] [WD Proxy] Matched ‘/element’ to command name ‘findElement’
[debug] [WD Proxy] Proxying [POST /element] to [POST http://127.0.0.1:8206/wd/hub/session/65344b1d-13aa-4631-bbe1-e8028927b53e/element] with body: {“strategy”:“xpath”,“selector”:“/hierarchy/android.widget.FrameLayout/android.widget.LinearLayout/android.widget.FrameLayout/android.widget.LinearLayout/android.widget.FrameLayout/androidx.drawerlayout.widget.DrawerLayout/android.widget.FrameLayout/androidx.recyclerview.widget.RecyclerView/androidx.appcompat.widget.LinearLayoutCompat[4]/android.widget.CheckedTextView”,“context”:“”,“multiple”:false}
[WD Proxy] Got response with status 404: {“sessionId”:“65344b1d-13aa-4631-bbe1-e8028927b53e”,“value”:{“error”:“no such element”,“message”:“An element could not be located on the page using the given search parameters”,“stacktrace”:"io.appium.uiautomator2.common.exceptions.ElementNotFoundException: An element could not be located on the page using the given search parameters\n\tat io.appium.uiautomator2.handler.FindElement.findElement(FindElement.java:89)\n\tat io.appium.uiautomator2.handler.FindElement.safeHandle(FindElement.java:66)\n\tat io.appium.uiautomator2.handler.request.SafeRequestHandler.handle(SafeRequestHandler.java:41)\n\tat io.appium.uiautomator2.server.AppiumServlet.handleRequest(AppiumServlet.java:262)\n\tat io.appium.uiautomator2.server.AppiumServlet.handleHttpRequest(AppiumServlet.java:256)\n\tat io.appium.uiautomator2.http.ServerHandler.channelRead(ServerHandler.java:68)\n\tat io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:366)\n\tat io.netty.channel.AbstractChannelHandlerCont…
[debug] [W3C] Matched W3C error code ‘no such element’ to NoSuchElementError
[debug] [W3C (cbe59fa4)] Encountered internal error running command: NoSuchElementError: An element could not be located on the page using the given search parameters.
[debug] [W3C (cbe59fa4)] at AndroidUiautomator2Driver.findElOrEls (C:\Users\nanoPix\AppData\Roaming\npm\node_modules\appium\node_modules\appium-android-driver\lib\commands\find.js:75:11)
[debug] [W3C (cbe59fa4)] at runMicrotasks ()
[debug] [W3C (cbe59fa4)] at processTicksAndRejections (internal/process/task_queues.js:95:5)
[debug] [W3C (cbe59fa4)] at AndroidUiautomator2Driver.findElOrElsWithProcessing (C:\Users\nanoPix\AppData\Roaming\npm\node_modules\appium\node_modules\appium-base-driver\lib\basedriver\commands\find.js:33:12)
[debug] [W3C (cbe59fa4)] at AndroidUiautomator2Driver.findElement (C:\Users\nanoPix\AppData\Roaming\npm\node_modules\appium\node_modules\appium-base-driver\lib\basedriver\commands\find.js:53:10)
[HTTP] ← POST /wd/hub/session/cbe59fa4-0214-4241-8fbe-ae2802650f5c/element 404 166 ms - 920

Looks my issue somewhat similar to the below Issue

thanks and regards
Abhilash