Webview android.content.pm.PackageManager$NameNotFoundException: com.google.android.webview [37048374]

Infeasible

Bug

[AOSP] Version-Opensource

Status Update

No update yet.

Description

ji...@gmail.com

created issue #1

May 29, 2015 09:15PM

A random exception while updating applications.
Android System Webview 42.0.2311.137

Android WebView exception
05-26 21:17:30.031 16093 16154 E AndroidRuntime: FATAL EXCEPTION: YI13NAdIdRetrivalThread--0
05-26 21:17:30.031 16093 16154 E AndroidRuntime: Process: com.yahoo.mobile.client.android.yahoo.att, PID: 16093
05-26 21:17:30.031 16093 16154 E AndroidRuntime: android.util.AndroidRuntimeException: android.content.pm.PackageManager$NameNotFoundException: com.google.android.webview
05-26 21:17:30.031 16093 16154 E AndroidRuntime: at android.webkit.WebViewFactory.getFactoryClass(WebViewFactory.java:174)
05-26 21:17:30.031 16093 16154 E AndroidRuntime: at android.webkit.WebViewFactory.getProvider(WebViewFactory.java:109)
05-26 21:17:30.031 16093 16154 E AndroidRuntime: at android.webkit.CookieManager.getInstance(CookieManager.java:42)
05-26 21:17:30.031 16093 16154 E AndroidRuntime: at com.yahoo.mobile.common.util.f.a(CookieHelper.java:34)
05-26 21:17:30.031 16093 16154 E AndroidRuntime: at com.yahoo.mobile.common.util.f.a(CookieHelper.java:27)
05-26 21:17:30.031 16093 16154 E AndroidRuntime: at com.yahoo.doubleplay.a.a.b(AccountManagerAdapter.java:138)
05-26 21:17:30.031 16093 16154 E AndroidRuntime: at com.yahoo.doubleplay.a.e.a(AccountSdkAccountManagerAdapter.java:205)
05-26 21:17:30.031 16093 16154 E AndroidRuntime: at com.yahoo.mobile.client.android.snoopy.c.a(YIDCookie.java:90)
05-26 21:17:30.031 16093 16154 E AndroidRuntime: at com.yahoo.uda.yi13n.ay.a(YQLProxy.java:910)
05-26 21:17:30.031 16093 16154 E AndroidRuntime: at com.yahoo.uda.yi13n.i.run(GooglePlayWrapper.java:177)
05-26 21:17:30.031 16093 16154 E AndroidRuntime: at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1112)
05-26 21:17:30.031 16093 16154 E AndroidRuntime: at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:587)
05-26 21:17:30.031 16093 16154 E AndroidRuntime: at java.lang.Thread.run(Thread.java:818)
05-26 21:17:30.031 16093 16154 E AndroidRuntime: Caused by: android.content.pm.PackageManager$NameNotFoundException: com.google.android.webview
05-26 21:17:30.031 16093 16154 E AndroidRuntime: at android.app.ApplicationPackageManager.getPackageInfo(ApplicationPackageManager.java:167)
05-26 21:17:30.031 16093 16154 E AndroidRuntime: at android.webkit.WebViewFactory.getFactoryClass(WebViewFactory.java:146)
05-26 21:17:30.031 16093 16154 E AndroidRuntime: ... 12 more

Comments

al...@android.com <al...@android.com> #2May 29, 2015 10:52PM

Status: Won't Fix (Infeasible)

Please report all issues with Chrome and Android WebView (which is based on Chromium) to

http://crbug.com/.

ja...@gtempaccount.com <ja...@gtempaccount.com> #3Jun 12, 2015 02:55PM

Was this ever filed in the chromium issue tracker? We're experiencing the same issue and are interested in more information. I searched, but couldn't find anything that looked relevant...

ji...@gmail.com <ji...@gmail.com> #4Jun 12, 2015 05:04PM

It looks like it happens because webview can now be updated through Google play. If your app tries to access webview while it is uninstalling/reinstalling, the package doesn't exist for that short amount of time and can cause your app to crash. I put a try/catcj block around all code that uses webview.

ja...@gtempaccount.com <ja...@gtempaccount.com> #5Jun 17, 2015 10:16PM

I've been able to recreate it the same way (updating Android System Webview in the background while running our app in the foreground) on a Galaxy Note 3. Unfortunately, it's not feasible (or, at least, not straightforward, by any means) for us to add guard clauses around anything using android.webkit (our crash actually occurs on accessing CookieManager). I'll go ahead and file this issue on

crbug.com.

ja...@gmail.com <ja...@gmail.com> #6Jun 28, 2015 05:09PM

I am seeing this as well

lb...@gmail.com <lb...@gmail.com> #7Jun 28, 2015 08:51PM

@1 I don't even use a webView in my app and I saw this issue recently. I think it's something with Admob.

ja...@gmail.com <ja...@gmail.com> #8Jun 28, 2015 08:57PM

Yes I am also using Admob as well. There are always problems with Admob with every update.

lb...@gmail.com <lb...@gmail.com> #9Jun 28, 2015 09:00PM

@7 I don't get how could it be. It's usually just static image banners... Why even use a Webview for such a simple ad?

ja...@gmail.com <ja...@gmail.com> #10Jun 28, 2015 09:02PM

@8 I dont know? I am jus agreeing with your previous comment. I also use Interstitial(full page) ads as well.

lb...@gmail.com <lb...@gmail.com> #11Jun 28, 2015 09:14PM

@9 Do the "Interstitial" ads also just use an image and that's it?
Or is it an animation of some sort?

ja...@gmail.com <ja...@gmail.com> #12Jun 28, 2015 09:17PM

They can have either.

lb...@gmail.com <lb...@gmail.com> #13Jun 28, 2015 09:26PM

@11 I see. Thanks. Anyway, Google, please fix this issue.

ja...@gtempaccount.com <ja...@gtempaccount.com> #14Jul 2, 2015 09:25PM

FYI for those following this issue I've reopened it in the chrome issue tracker per AL's request:

https://code.google.com/p/chromium/issues/detail?id=506369

me...@gmail.com <me...@gmail.com> #15Jul 7, 2015 05:15AM

we are facing this issue as well.

od...@gmail.com <od...@gmail.com> #16Aug 30, 2015 07:21AM

We have the same issue, is there any workaround this? Also, there is a good chance it happens many times after webview update, and not just for a "short amount of time".

od...@gmail.com <od...@gmail.com> #17Aug 30, 2015 07:23AM

lb...@gmail.com <lb...@gmail.com> #18Aug 30, 2015 07:43AM

@15 I think a possible workaround is to have the AdView instance via code. That's what I do, at least.
I've even put it in a fragment's onCreatView function, and added it to one of its ViewGroups.
Try it. Maybe it will help.

ga...@gmail.com <ga...@gmail.com> #19Nov 4, 2015 03:45PM

This is the relevant chromium issue, marked as WontFix:

https://code.google.com/p/chromium/issues/detail?id=506369

lb...@gmail.com <lb...@gmail.com> #20Nov 4, 2015 03:48PM

@18 Why is it marked as wontFix, if it's clearly a bug that causes the app to crash, and that we can't fix it ourselves (it's inside of AdView...) ?

ta...@gmail.com <ta...@gmail.com> #21Mar 19, 2018 05:38AM

Facing this issue with support lib 27 as well.

dp...@gmail.com <dp...@gmail.com> #22Mar 26, 2018 06:54PM

Given that this issue is surprising but also known & intended behavior, could we get CookieManager.getInstance()'s signature modified in Android Pocky or Peanut Butter or whatever to include throws AndroidRuntimeException?

al...@gmail.com <al...@gmail.com> #23May 11, 2018 10:00AM

I had a bug report about this issue in my app which does not use Webviews. I don't have the stacktrace showing it (not deep enough) but it seems there is an undocumented dependency from textView on Webview when using autolink:

https://bitbucket.org/bitbeaker-dev-team/bitbeaker/issues/239/namenotfoundexception
I am now disabling autolink during layout inflation on views visible just after startup and setting it later by code wrapped in a try catch. I don't have many instances of the crash so I won't be able to confirm this workaround really works. I would appreciate your comments.