Issue metadata
Sign in to add a comment
|
Yahoo! Sports crash in "Account key" menu item |
||||||||||||||||||||||||
Issue description- Package name: com.yahoo.mobile.client.android.sportacular - Android build (Home > Settings > About phone > Build number): marlin-OPR1.170308.002 - Carrier: verizon =====STEPS TO REPRODUCE===== [Be as specific as possible; rather than "browse around a few web pages", say "go to this URL, then click on this specific link".] 1. hamburger menu 2. account key (may need to be signed in) EXPECTED RESULTS: unknown, don't what that is supposed to take me to OBSERVED RESULTS: crash, see log below NUMBER OF TIMES YOU WERE ABLE TO REPRODUCE (e.g. 3/10): 3/3 DEVICES TESTED: marlin 03-10 17:30:41.096 15305 15305 E AndroidRuntime: FATAL EXCEPTION: main 03-10 17:30:41.096 15305 15305 E AndroidRuntime: Process: , PID: 15305 03-10 17:30:41.096 15305 15305 E AndroidRuntime: java.lang.IllegalStateException: Cannot execute task: the task has already been executed (a task can be executed only once) 03-10 17:30:41.096 15305 15305 E AndroidRuntime: at android.os.AsyncTask.executeOnExecutor(AsyncTask.java:612) 03-10 17:30:41.096 15305 15305 E AndroidRuntime: at android.os.AsyncTask.execute(AsyncTask.java:567) 03-10 17:30:41.096 15305 15305 E AndroidRuntime: at com.yahoo.mobile.client.share.activity.BaseWebViewActivity$AccountWebViewClient.shouldOverrideUrlLoading(Yahoo:1019) 03-10 17:30:41.096 15305 15305 E AndroidRuntime: at android.webkit.WebViewClient.shouldOverrideUrlLoading(WebViewClient.java:73) 03-10 17:30:41.096 15305 15305 E AndroidRuntime: at com.android.webview.chromium.WebViewContentsClientAdapter.shouldOverrideUrlLoading(WebViewContentsClientAdapter.java:354) 03-10 17:30:41.096 15305 15305 E AndroidRuntime: at org.chromium.android_webview.AwContentsClient.shouldIgnoreNavigation(AwContentsClient.java:168) 03-10 17:30:41.096 15305 15305 E AndroidRuntime: at org.chromium.android_webview.AwContentsClientBridge.shouldOverrideUrlLoading(AwContentsClientBridge.java:352) 03-10 17:30:41.096 15305 15305 E AndroidRuntime: at org.chromium.base.SystemMessageHandler.nativeDoRunLoopOnce(Native Method) 03-10 17:30:41.096 15305 15305 E AndroidRuntime: at org.chromium.base.SystemMessageHandler.handleMessage(SystemMessageHandler.java:41) 03-10 17:30:41.096 15305 15305 E AndroidRuntime: at android.os.Handler.dispatchMessage(Handler.java:102) 03-10 17:30:41.096 15305 15305 E AndroidRuntime: at android.os.Looper.loop(Looper.java:156) 03-10 17:30:41.096 15305 15305 E AndroidRuntime: at android.app.ActivityThread.main(ActivityThread.java:6408) 03-10 17:30:41.096 15305 15305 E AndroidRuntime: at java.lang.reflect.Method.invoke(Native Method) 03-10 17:30:41.096 15305 15305 E AndroidRuntime: at com.android.internal.os.Zygote$MethodAndArgsCaller.run(Zygote.java:232) 03-10 17:30:41.096 15305 15305 E AndroidRuntime: at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:751) =====HELPFUL DETAILS=====
,
Mar 16 2017
,
Mar 16 2017
can someone from london investigate tomorrow.
,
Mar 17 2017
Friendly ping here... who will finalize investigation?
,
Mar 17 2017
I will look, it seems :)
,
Mar 21 2017
This is broken by https://codereview.chromium.org/2633663003, strict secure cookies.
,
Mar 22 2017
,
Mar 22 2017
Mike/Joel: I guess the action is connecting Yahoo in this case. Do we expect such breakages to be rare? Alex: FYI, for M58 potential WebView breakages.
,
Mar 22 2017
Joel has left the company, so he's unlikely to take a look at this. :) The patch mentioned in comment 7 implements behavior we want, so I'd like to make sure we keep it in in some form. That said, it's not at all clear to me how it affects the codepath we're discussing here. Could you help me understand the error? If we can implement the change in a way less likely to break WebView apps, we certainly will.
,
Mar 24 2017
I think in this particular case, it is Yahoo to blame. after adding some logs I see that Yahoo is using WebView's setCookie API to set a secure cookie for url "yahoo.com" SSL=v=1&s=W1oCYMzCdd20UIGyyWjQdE...(some other stuff)...&kv=0; path=/; domain=.yahoo.com; secure; httponly With the strict secure cookies, this will not be set anymore. There is probably some other part of the code that relies on this cookie, and not work. I will close the bug as won't fix, and will ping Yahoo about it.
,
Mar 24 2017
,
Apr 14 2017
|
|||||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||||
Comment 1 by sgu...@chromium.org
, Mar 16 2017