You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
A lot of stacktraces are shown in the log for the test run, even though the test launches and operates normally. I'm not sure why. The log page if I'm not mistaken may just be collecting some "noise" from other logging events. Here's a snippet of the stacktrace I'm seeing:
java.lang.NoSuchMethodException: getSlotId [int]
at java.lang.Class.getMethod(Class.java: 2068)
at java.lang.Class.getDeclaredMethod(Class.java: 2047)
at com.google.android.apps.a.a.a.c.i.b(SourceFile: 51)
at com.google.android.apps.a.a.a.c.i.d(SourceFile: 73)
at com.google.android.ims.k.w.a(SourceFile: 22)
at com.google.android.ims.k.w.a(SourceFile: 21)
at com.google.android.ims.k.x.a(SourceFile: 7)
at com.google.android.ims.k.a.<init>(SourceFile: 7)
at com.google.android.ims.k.k.<init>(SourceFile: 8)
at com.google.android.ims.k.k.a(SourceFile: 7)
at com.google.android.ims.CarrierServicesReleaseApp.onCreate(SourceFile: 61)
at android.app.Instrumentation.callApplicationOnCreate(Instrumentation.java: 1118)
at android.app.ActivityThread.handleBindApplication(ActivityThread.java: 5791)
:
at android.app.ActivityThread$H.handleMessage(ActivityThread.java: 1661)
at android.os.Handler.dispatchMessage(Handler.java: 105)
at android.os.Looper.loop(Looper.java: 164)
at android.app.ActivityThread.main(ActivityThread.java: 6541)
at java.lang.reflect.Method.invoke(Native Method: )
at com.android.internal.os.Zygote$MethodAndArgsCaller.run(Zygote.java: 240)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java: 767)
The text was updated successfully, but these errors were encountered:
Overview
Unfortunately this link is not publicly sharable at this point, but I'm including it for my reference: https://appcenter.ms/orgs/XTCTeam/apps/Swiftnotes-Appium/test/runs/77a1c67e-2cfb-4bbd-a75a-eb2b4fd0a747/0-0-0/7bd64936-8d1e-484c-aff9-063db240bb59/logs
A lot of stacktraces are shown in the log for the test run, even though the test launches and operates normally. I'm not sure why. The log page if I'm not mistaken may just be collecting some "noise" from other logging events. Here's a snippet of the stacktrace I'm seeing:
The text was updated successfully, but these errors were encountered: