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
adb shell am start -n 'com.google.android.webview.canary'# https://stackoverflow.com/revisions/4567928/2#:~:text=adb%20shell%20am%20start%20%2Dn%20com.package.name/com.package.name.ActivityName
...causing the undermentioned crash:
Exception occurred while executing 'start':
java.lang.IllegalArgumentException: Bad component name: com.google.android.webview.canary
at android.content.Intent.parseCommandArgs(Intent.java:8458)
at com.android.server.am.ActivityManagerShellCommand.makeIntent(ActivityManagerShellCommand.java:477)
at com.android.server.am.ActivityManagerShellCommand.runStartActivity(ActivityManagerShellCommand.java:601)
at com.android.server.am.ActivityManagerShellCommand.onCommand(ActivityManagerShellCommand.java:233)
at com.android.modules.utils.BasicShellCommandHandler.exec(BasicShellCommandHandler.java:97)
at android.os.ShellCommand.exec(ShellCommand.java:38)
at com.android.server.am.ActivityManagerService.onShellCommand(ActivityManagerService.java:9798)
at android.os.Binder.shellCommand(Binder.java:1068)
at android.os.Binder.onTransact(Binder.java:888)
at android.app.IActivityManager$Stub.onTransact(IActivityManager.java:5267)
at com.android.server.am.ActivityManagerService.onTransact(ActivityManagerService.java:2743)
at android.os.Binder.execTransactInternal(Binder.java:1344)
at android.os.Binder.execTransact(Binder.java:1275)
versionCode=119016358 minSdk=21 targetSdk=34
versionName=8.9.76.426
signatures=PackageSignatures{4a035f4 version:4, signatures:[e47393c5], past signatures:[]}
Verification
I've confirmed that Scoop remains able to record (other) crashes, because I can reproducibly cause the undermentioned:
FATAL EXCEPTION: main
Process: com.twitter.android, PID: 31316
java.lang.UnsupportedOperationException: Editing b is not supported
at d5k.invoke(Twttr:78)
at wc5.d(Twttr:21)
at androidx.recyclerview.widget.e0$a.d(Twttr:56)
at oi$a.onInitializeAccessibilityNodeInfo(Twttr:254)
at android.view.View.onInitializeAccessibilityNodeInfo(View.java:8907)
at android.view.View.createAccessibilityNodeInfoInternal(View.java:8868)
at android.view.View$AccessibilityDelegate.createAccessibilityNodeInfo(View.java:31666)
at android.view.View.createAccessibilityNodeInfo(View.java:8851)
at android.view.AccessibilityInteractionController$AccessibilityNodePrefetcher.prefetchDescendantsOfRealNode(AccessibilityInteractionController.java:1526)
at android.view.AccessibilityInteractionController$AccessibilityNodePrefetcher.prefetchAccessibilityNodeInfos(AccessibilityInteractionController.java:1315)
at android.view.AccessibilityInteractionController.findAccessibilityNodeInfoByAccessibilityIdUiThread(AccessibilityInteractionController.java:405)
at android.view.AccessibilityInteractionController.-$$Nest$mfindAccessibilityNodeInfoByAccessibilityIdUiThread(Unknown Source:0)
at android.view.AccessibilityInteractionController$PrivateHandler.handleMessage(AccessibilityInteractionController.java:1719)
at android.os.Handler.dispatchMessage(Handler.java:106)
at android.os.Looper.loopOnce(Looper.java:205)
at android.os.Looper.loop(Looper.java:294)
at android.app.ActivityThread.main(ActivityThread.java:8223)
at java.lang.reflect.Method.invoke(Native Method)
at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:552)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:977)
Turns out that that was because I didn't enter an activity, so I don't know whether it should have recorded it. I'll file a new bug that actually makes use of a crash log.
Error
Despite the undermentioned command:
...causing the undermentioned crash:
...Scoop doesn't record it:
Environment
As undermentioned, in the URI:
Verification
I've confirmed that Scoop remains able to record (other) crashes, because I can reproducibly cause the undermentioned:
...in https://www.apkmirror.com/apk/x-corp/twitter/twitter-10-58-0-release-0-release/x-previously-twitter-10-58-0-release-0-android-apk-download/#file.
Importance
This was problematic for me because it made diagnosing https://issues.chromium.org/issues/366123452#comment1 significantly more difficult.
The text was updated successfully, but these errors were encountered: